<cruxbot>
[opt.git/3.7]: bindutils: update to 9.18.20
<cruxbot>
[opt.git/3.7]: mupdf: update to 1.23.6
<cruxbot>
[opt.git/3.7]: btrfs-progs: update to 6.6.2
<deltahotel>
I'm going to move from openbsd to crux soon. I hope it's gonna be all right...
<jaeger>
I'd suggest trying it for a while in a VM to see what you think
<jaeger>
Or on some extra hardware if you have it
<SiFuh>
deltahotel: For a non BSD distro, CRUX is probably the closest of the Linux to OpenBSD. There isn't much of a relationship at all since they are two entirely different things but there are many similarities in some ways.
<ukky>
deltahotel: what is the motive behing the decision? I'm just curious, switched to CRUX myself recently.
<cruxbot>
[core.git/3.7]: cmake: update to 3.27.8
<deltahotel>
ukky: my hardware is not recognized, no driver for my wifi card and my touchpad. but on the security side obd is great.
<ukky>
deltahotel: okay.
<deltahotel>
SiFuh: can you explain why crux is closest to obsd than other linux distrubutions?
<SiFuh>
BSD-style initscripts
<jaeger>
Also a ports system similar to BSDs
crash_ has quit [Quit: leaving]
groovy2shoes has quit [Ping timeout: 268 seconds]
groovy2shoes has joined #crux
stoffepojken has quit [Quit: ZNC 1.8.2 - https://znc.in]
stoffepojken has joined #crux
stoffepojken has quit [Remote host closed the connection]
<SiFuh>
jaeger: CRUX's fsearch is the coolest feature
<jaeger>
definitely handy
stoffepojken has joined #crux
<SiFuh>
Yeah, shame most distros don't have this feature
<ukky>
fsearch is probably the most often used prt-get command on my side. This is a must for source-based distro.
<deltahotel>
note that I am going to install crux on an HP 15-dw1000nk laptop
lavaball has quit [Remote host closed the connection]
<jaeger>
Yes, you can certainly build in a container if you want
<jaeger>
Same way as you would build outside a container, you'd need to install the required dependencies and then copy or map the built packages out of the container at the end
<Guest9824>
thank you, i find it easier to deal with virtualized machines which also give better isolation than containers.
<Guest9824>
will go with qemu with ssh
<jaeger>
That would also work fine
<Guest9824>
right now building initramfs from scratch, trying to implement dropbear to boot early and provide ssh for disk decryption.
<Guest9824>
neat distribution, thank you
<Guest9824>
managed to get triple cipher serpent(twofish(aes())) + whirlpool to work with cryptsetup and custom initramfs
<SiFuh>
Yeah, I pushed for that
<Guest9824>
but it's kind of slow, even with nvme and 32 cores
<ukky>
Guest9824: you need to benchmark all algo and choose which one performs the best. If you blindly enable all, it will be slow
<Guest9824>
ah. i used veracrypt cli to crypt the partition, and 'cryptsetup open --type tcrypt --veracrypt --debug --veracrypt-query-pim /dev/nvme0n1p2 crypt' for decryption from initramfs
<SiFuh>
Guest9824: we also have dracut, are you using this for your initramfs?
<crash_>
jaeger: is your updated isos working? i have not tried it for awhile
<Guest9824>
SiFuh: im building my own initramfs, manually. statically building busybox and cryptsetup, including dax, dm-mod, dm-crypt kernel modules and writing script that does switch_root further.
<Guest9824>
and decrypts of course
<Guest9824>
i don't like dracut, it's full of everything
<jaeger>
crash_: as far as I know, but haven't hand-tested the latest
<SiFuh>
Point taken
<ukky>
crash_: I think I installed CRUX on one of the systems using the latest that jaeger has. I can tell which one exactly if you need.
<crash_>
jaeger: nice to know :) i'm not sure what the contributed kernel is based on? i mostly use the standard crux kernel .config but i might try this contributed config on this machine this time.
<crash_>
jaeger: nice to know :) i'm not sure what the contributed kernel is based on? i mostly use the standard crux kernel .config but i might try this contributed config on this machine this time.
<jaeger>
It's a contribution from SiFuh so he can give details on that
<crash_>
I see thanks
<jaeger>
Hrmm... I just grabbed the latest ISO to do a quick chroot tests and it has some problems
<jaeger>
duplicate packages
<jaeger>
I wonder how that happened
<jaeger>
So maybe don't use that one yet until I figure out what went wrong
<ukky>
jaeger: do you mean DB is corrupted?
<jaeger>
No, just that it has more than one copy of for example linux-firmware in the packages directory
<jaeger>
which means the automated process that cleans out old packages before building the new ones failed
<ukky>
Then you probably reused the same build directory, perhaps?
<SiFuh>
crash_: It's just a fully modular kernel for x86/amd64 so that pretty much everything standard (Some non-standard things) exists.
<ukky>
jaeger: It is unofficial ISO. So, having older package versions besides the latest is not an issue. The kernel options is what is important.
<SiFuh>
ukky: Thought it was named unofficial because it is not an officially public release
<ukky>
SiFuh: Yes. And only a few people know where it can be found :-)
<SiFuh>
Including google ;-)
<crash_>
SiFuh: Thanks for the info, so most of the drivers and things should work with yout kernel then :)
<ukky>
But google doesn't know there are older versions of packages in the latest ISO...
<crash_>
jaeger:Oh do you have older working isos as well or just the current built one?
<SiFuh>
crash_: Yep. I use it as is on laptops. But on a PC I use it as the foundation for creating a custom kernel.
<jaeger>
Generally just the latest, it gets replaced automatically
<jaeger>
ukky: part of the automation cleans old build artifacts... and usually that works fine
<crash_>
jaeger: maybe it's better to use the standard crux 3.7 iso until you have fixed the duplicated packages
<ukky>
jaeger: cannot argue. When I was building CRUX ISO I modified Makefile heavily to build it as restricted user, and only as root in chrooted environment. Original Makefile, if used as root, can destroy the root file system when build is interrupted, and then re-run as root again.