<Guest59>
hey i tried using swaybg but get an error saying that "couldnt recognize image file format." ive installed libjpeg and libpng and don't know what could cause this
<ukky>
Guest59: your image could be in SVG format. Use file command to check image format.
<Guest59>
its a png file
<Guest59>
wait what's the command to check image format
<ukky>
file file-name
<Guest59>
i checked and it is a "javascript source"
<ukky>
You can confirm visually via: hexdump -C file-name | less
<Guest59>
i dont think it is a svg
dontmindmee has quit [Ping timeout: 260 seconds]
<ukky>
do you have 'feh' image viewer?
<Guest59>
isn't feh for xorg
<ukky>
oups
<ukky>
can you post header of that file to 0x0? hexdump -C file-name | head -n 100 >/tmp/header.txt
<synima>
Sorry i didnt quite understand what you said
<midfavila>
they're not exactly anything special
<midfavila>
maybe i'll put some stuff about my routines up on my site
<midfavila>
idk
<sewn>
i would like
<sewn>
synima: man acpid
<synima>
Was using the lfs page lol
<sewn>
bruh
<synima>
Thats what im sayin
traidare has joined #kisslinux
midfavila has quit [Quit: Leaving.]
schillingklaus has joined #kisslinux
phinxy has joined #kisslinux
chomwitt has quit [Ping timeout: 260 seconds]
<sewn>
ughh chromium has no vulkan
<sewn>
time to recompil
chomwitt has joined #kisslinux
traidare has quit [Ping timeout: 258 seconds]
schillingklaus has quit [Quit: schillingklaus]
traidare has joined #kisslinux
<ukky>
sewn: compiling chromium is fun
<acsqdotme>
I'm almost done with my install now. Building up my packages from source was cool, and I get how cool and simple the package system is with just listing out the packages and dependencies in plaintext. I just don't have enough experience to know much about the kernel part besides hardware comparability and have no idea how boot works with initramfs.
asimovsh has quit [Ping timeout: 264 seconds]
<acsqdotme>
can someone give a basic explanation of how booting works and how I'm setting that up with the fstab stuff and grub and tinyramfs?
asimovsh has joined #kisslinux
<ukky>
acsqdotme: Booting process on X86 platform after power up starts from executing System BIOS. There are two modes: Legacy and UEFI. System BIOS might execute some extra BIOS code from PCI devices. Then System BIOS passes control to boot loader, which can be Grub/Lilo/etc, also in two modes, legacy or UEFI.
<ukky>
Then, if it is Grub, it loads Kernel/Initramfs according to your Grub config.
<ukky>
And then Kernel might execute your init script from Initramfs. Without initramfs, after kernel initialization, kernel passes control to init system. Usually it is /sbin/init.
<ukky>
Information about hardware Linux kernel takes from memory map and ACPI tables. Those are created by System BIOS.
<ilt>
+ without initramfs extra care must be taken to ensure that all modules(like fs) necessary to boot are built in. otherwise kernel may not be able to boot the host system
<ilt>
iirc this is documented in kiss install guide
<acsqdotme>
yeah, the actual quote was messing with my head though, so I wanted to check in: "Thus (without an initramfs), your kernel must be able to locate and mount the root filesystem without the use of modules. In other words, these drivers should be "baked in" (=y) (not =m)."
<acsqdotme>
so lmk if this is okay to understand: BIOS/UEFI --(boot order)-> grub --(fstab grub files)-> kernel --(initramfs??)-> pid1 /sbin/init that spawns the rest of the os?
<acsqdotme>
how does one thing find the rest in this chain?
traidare has quit [Ping timeout: 258 seconds]
<ukky>
It depends on which component in this boot chain is currently being in control.
<synima>
What repo do yall use for jdk?
<synima>
Or jre
<ukky>
acsqdotme: I.e. whether current component is BIOS, grub, kernel, etc., the next step options depend on it.
<ukky>
acsqdotme: System BIOS has no idea if you are loading Linux, Windows, or baremetal application without any OS
<ukky>
acsqdotme: System BIOS only knows where to find boot loader.
<acsqdotme>
yeah, so each component can only see the next one. I wanna know how bios can find the bootloader or how the bootloader can find the kernel etc. I wanna know how the gaps in the chain are filled in.
<sewn>
ukky: with ccache its fun to watch
<synima>
Look up a build a kernel book
<sewn>
but its not fun when a critical tool doesnt build
<sewn>
and now i have to debug cflags
<synima>
Nerd
<sewn>
your mom
traidare has joined #kisslinux
<ukky>
sewn: how long does it take to build chromium with ccache and without on your system? just curious.
<sewn>
idk cant tell yet cuz a tool to build it is broken
<sewn>
but with ccache it takes like maybe 2 or 3 hours
<sewn>
i mean without
<sewn>
cuz i build it half way through and it took only an hour
<sewn>
schillingklaus: wayland is a protocol, i think youre talking about compositors specifically
<sewn>
i think flatpak is a good thing for kiss because you dont have maintainers who maintain large packages like gimp or krita, or the curse of them breaking
asimovsh has joined #kisslinux
<ilt>
sewn: some points are still actual
<ilt>
like, device=all is still present
<ilt>
which is footgun
<sewn>
yeah thats a fair point
<sewn>
i see this with ungoogled chromium
<sewn>
then atleast we should have proper package maintainers or something on kiss if flatpak isnt all that great as it is
<synima>
I appreciate all of the help yall, but it is all for nothing, as i have reformatted my kiss linux drive
<synima>
Shit, i forgot to save my .config
<sewn>
uh oh
<sewn>
why
<sewn>
atleast use alpine
<synima>
Minecraft 1.12.2 doesnt work on wayland
<synima>
Ill likely revisit when i find a browser that doesnt need x at all and i can run mc via wayland
<sewn>
flatpak
<sewn>
and xwayland
<synima>
Ill reinstall this wednesday then probably
dontmindmee has quit [Ping timeout: 252 seconds]
schillingklaus has quit [Quit: schillingklaus]
farkuhar has joined #kisslinux
<synima>
Ima make a write up for post install and getting into a wayland environment