ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.org | post logs or else | "An idiot admires complexity, a genius admires simplicity." -- Terry A. Davis
davidgarland has quit [Quit: Client closed]
<dilyn>
anybody else having a problem installing binaries as setuid with kiss? just had an issue reinstalling opendoas
<dilyn>
oh, curious...??
sammifammish has joined #kisslinux
<noocsharp>
i recently packaged a setuid program and it was fine
<dilyn>
the opendoas package doesn't seem to make itself setuid
<x4n>
But I was talking about the binary packages in kiss-community/bin
pehaef has joined #kisslinux
x4n has quit [Remote host closed the connection]
micro_O has quit [Ping timeout: 260 seconds]
dionys has left #kisslinux [#kisslinux]
micro_O has joined #kisslinux
humky has quit [Quit: Leaving]
micro_O has quit [Ping timeout: 265 seconds]
micro_O has joined #kisslinux
michalsieron has quit [Ping timeout: 252 seconds]
davidgarland has joined #kisslinux
<davidgarland>
made progress since yesterday but now I'm up to a kernel panic-- it says "VFS: Cannot open root device "PARTUUID=..." or unknown-block(0, 0): error -6"; "Please append a correct "root=" boot option; here are the available partitions:" then goes on to list UUIDs I don't recognize from blkid
<davidgarland>
I suspected it might be a missing SATA or AHCI driver based on googling the issue but it seems like I've enabled the relevant settings for an Intel controller (what lspci says I have) so I'm unsure what i could be missing
<soliwilos>
Have you enabled the filesystem you're using in the kernel?
<davidgarland>
let me check
<davidgarland>
ext4 seems to be enabled yeah
<soliwilos>
Did you also try using root=/dev/sdXY instead of uuid?
<davidgarland>
worth a try, ill give that a spin
<pehaef>
one of the UUID things only works if you have an initramfs that handles it with userland stuff, I forget which
<pehaef>
the other I believe the kernel can do on it's own?
<davidgarland>
I am under the impression efistub with no initramfs should be possible-- I've avoided allowing any kernel modules and baked in the microcode and graphics drivers
<pehaef>
ah efistub, that's fun stuff; I am doing the same at work alas I never could get it to do the right thing without an initramfs; which I bake into the kernel for now but have plans to not to once efibootmgr works like it should; sorry I should say that what I am doing is not actually kisslinux related, it's a custom embedded-ish thing
<davidgarland>
I see
<davidgarland>
I've never tried any custom stuff, always got stuck when trying to do LFS lol
<davidgarland>
figures given it's taken me a full day already to get back to this point with KISS
<pehaef>
figuring out how the darn kernel wants to continue booting can be quite confusing, especially when you try EFI; but I figured "hey, no bootloader needed, one less moving part" so I went there as well
<davidgarland>
for me it's more just frustration with the fact that GRUB seems to manage to always erase my windows 10 install that's on a *separate disk* somehow
<davidgarland>
hoping this doesn't have the same issue (though last install also got wiped since i only started trying efistub after another failed grub attempt x_x)
<davidgarland>
boots now :)
<micro_O>
js "I want range(99)" jv "we have range(99) at home" range(99) at home "[...Array(99).keys()]"
<davidgarland>
lmao
<davidgarland>
amazing how everything runs on a language that can't figure out what lexical scope is
illiliti has joined #kisslinux
<davidgarland>
o/
<illiliti>
hi
<testuser[m]>
Hi
<pehaef>
davidgarland: congrats!
<davidgarland>
thanks for the help
<pehaef>
davidgarland: so did PARTUUID work or did the "classic" path for the partition work?
mulc has quit [Ping timeout: 276 seconds]
<davidgarland>
I ended up getting PARTUUID working, but I'm not entirely sure which kernel option specifically was responosible for getting it working
<noocsharp>
that's how it goes
<noocsharp>
one day, go through and randomly delete kernel options until it breaks
<davidgarland>
probably a dumb question but how do I get dhcpcd to stop printing things over the console
<davidgarland>
am using the default busybox init
<davidgarland>
..just edited the run file manually, guess that works
akira01 has joined #kisslinux
<akira01>
hi guys
<akira01>
have any openjdk repo that works?
<davidgarland>
if you're merely concerned with getting one onto your machine, you could use https://adoptium.net/ to grab prebuilt ones-- if that's not what you want, then disregard
humky has joined #kisslinux
<akira01>
will test
<akira01>
why the problem in build?
mulc has joined #kisslinux
micro_O_ has joined #kisslinux
micro_O has quit [Ping timeout: 265 seconds]
<noocsharp>
i think landlock could be a lighter weight way to verify that dependencies are correct than chroot
<noocsharp>
by allowing access only to files owned by particular dependencies, and if a file outside of that is accessed, then you know that it's missing something
akira01 has quit [Ping timeout: 260 seconds]
soliwilos has quit [Remote host closed the connection]
pehaef has joined #kisslinux
pehaef has quit [Client Quit]
micro_O_ has quit [Ping timeout: 265 seconds]
gtms has quit [Remote host closed the connection]
mulc has quit [Ping timeout: 276 seconds]
illiliti has quit [Read error: Connection reset by peer]
aws has joined #kisslinux
<aws>
Hello
<aws>
I'm trying out hexchat
<acheam>
hi
davidgarland has quit [Quit: Client closed]
aws has quit [Quit: Leaving]
aws has joined #kisslinux
aws has quit [Client Quit]
micro_O has joined #kisslinux
jess is now known as j
micro_O has quit [Quit: micro_O]
dilyn has joined #kisslinux
<dilyn>
decided i wanted to play around with dylan's new take on baseinit and also get smdev sorted
<dilyn>
forgot that baseinit by default is fscked with toybox, so had to handle constant exits
<dilyn>
been troubleshooting a 'cannot fork - try again' for a couple hours now
<dilyn>
realized it's because my chromium script is self-referring, not because something during init indefinitely blocks >.<
dilyn has quit [Quit: Connection closed]
<acheam>
uhhh
<acheam>
you launch chromium on boot?
dilyn has joined #kisslinux
<dilyn>
no, it's just one of the first things i launch after wayfire
<acheam>
then why did you think it was an init issue?
<dilyn>
which is why it was so confusing (yet should have been obvious) -- wayfire launched fine
<dilyn>
because I'm a mooran
<acheam>
ah but wayfire launches chromium?
<dilyn>
no it's just muscle memory to hit meta+w at this point
<dilyn>
meta+enter; meta+w, twerktwerktwerk
<dilyn>
interestingly, with toybox mount, baseinit nonfatally errors saying that /dev is not in /proc/mounts when trying to mount devtmpfs...
<dilyn>
but toybox mount is complete, and sufficient in this case. so that's weird