04:32 <brian|lfs> will try another machine but I'm getting a kernel panic with the crux-3.8-rc3 iso.

04:37 <brian|lfs> interesting boots fine on virtualbox

04:56 <brian|lfs> trying again writing with dd from Linux this time also verified the md5sum.

05:27 <SiFuh_> brian|lfs: What did you use before trying dd?

05:27 <brian|lfs> rufus in windows

05:28 <SiFuh_> And di it work with dd?

05:28 <brian|lfs> not sure yet drive still wiping lol

05:29 <SiFuh_> I will give it a go too. But using dd.

05:33 <brian|lfs> dd if=crux-3.8-rc3.iso of=/dev/sda bs=1M status=progress

05:33 <brian|lfs> I see no progress lol

05:36 <SiFuh_> Booted fine on and old machine. Surprised to discover the old box had 4GB of ram ;-)

05:38 <brian|lfs> same here booted fine maybe I had a bad download first try

05:39 <brian|lfs> even has my nic driver the kernel now fairly popular card to not be included

05:39 <SiFuh_> brian|lfs: by the way, UEFI or BIOS?

05:39 <brian|lfs> the atlantic driver

05:40 <brian|lfs> UEFI here

05:42 <SiFuh_> I did Legacy BIOS. So all good here

05:43 <brian|lfs> I'll reply to my email an state all seems good must of had a bad download or something

05:46 <SiFuh_> jaeger: Just a thought. That "Welcome to the CRUX 3.8 installation media!" screen for legacy BIOS boot mode, since CRUX copying the rootfs for installation has surpassed 1GB of RAM. Maybe adding a warning line informing the installer might be an idea.

05:50 <brian|lfs> that must be my issue 128 gb of RAM lol.

05:58 <r0ni> crux 3.8 iso is mbr only, can't boot on my uefi system, i can see the partition but something appears wrong with it

05:59 <r0ni> have to bake me a new iso see if I can't get it to show up

06:32 <cruxbot> [compat-32/3.7]: gst-plugins-base-32: 1.24.10 -> 1.24.11

06:32 <cruxbot> [contrib/3.7]: gst-plugins-bad: 1.24.10 -> 1.24.11

06:32 <cruxbot> [compat-32/3.7]: gstreamer-32: 1.24.10 -> 1.24.11

06:32 <cruxbot> [opt/3.7]: gst-plugins-base: 1.24.10 -> 1.24.11

06:32 <cruxbot> [contrib/3.7]: gst-plugins-good: 1.24.10 -> 1.24.11

06:32 <cruxbot> [opt/3.7]: gstreamer: 1.24.10 -> 1.24.11

06:32 <cruxbot> [contrib/3.7]: gst-plugins-ugly: 1.24.10 -> 1.24.11

06:32 <cruxbot> [opt/3.7]: gst-libav: 1.24.10 -> 1.24.11

06:32 <cruxbot> [contrib/3.7]: gst-python3: 1.24.10 -> 1.24.11

06:32 <cruxbot> [contrib/3.7]: easyeffects: 7.2.1 -> 7.2.3

06:44 <cruxbot> [contrib/3.7]: redis: 7.4.1 -> 7.4.2

06:44 <cruxbot> [contrib/3.7]: qownnotes: 25.1.2 -> 25.1.3

06:44 <cruxbot> [contrib/3.7]: iniparser: 4.2.4 -> 4.2.5

07:16 <jaeger> There's a note about requirements in the handbook... but with that said, if you try to boot on a system with too little RAM I don't think you'll get to the welcome message, most likely

07:17 <jaeger> r0ni: it's definitely not bios-only, I test as much UEFI hardware as I can...

07:19 <SiFuh_> jaeger: Nah, I mean the welcome message for SYSLINUX. As for the entry requirement in the handbook it is so short it is easily overlooked :-P

07:20 <SiFuh_> jaeger: So did brian|lfs. He just did it on UEFI

07:23 <SiFuh_> jaeger: Oh and by-the-way. Even if the rootfs has not fully copied over and errors out, you can actually still get a cmdline prompt.

07:23 <SiFuh_> Anyway, it isn't anything important, just an idea only.

07:27 <jaeger> Something to consider, sure. For now, going to sleep :)

07:28 <SiFuh_> Damn, must be like 03:30 am there or something.

08:39 <uwumeowmeownyaa> Why is LLVM installed on my system?

08:40 <cruxbridge> <tim> prt-get dependent llvm

08:41 <SiFuh_> In Soviet Russia your system installed LLVM

08:41 <SiFuh_> Actually that should be LLVM installed your system :-P

08:49 <uwumeowmeownyaa> tim: Thank you! I did not expect ``prt-get'' to have this functionality.

09:07 <uwumeowmeownyaa> There are more than 700 packages installed on my 'puter powered by the "Gentoo Linux" GNU/Linux distribution, while only 350 on the one powered by the "CRUX" GNU/Linux distribution.

09:09 <uwumeowmeownyaa> How many packages do you have installed? I used this command for counting: ``prt-get listinst | ln -b a''.

09:12 <cruxbot> [xorg/3.7]: xorg-xf86-input-synaptics: updated to version 1.10.0

09:12 <cruxbot> [xorg/3.7]: xorg-xinit: updated to version 1.4.3

09:12 <cruxbot> [xorg/3.7]: libinput: updated to version 1.27.1

09:14 <cruxbot> [opt/3.7]: firefox-bin: updated to version 134.0

09:14 <cruxbot> [opt/3.7]: xterm: updated to version 397

09:16 <cruxbot> [core/3.7]: bc: updated to version 1.08.1

10:46 <SiFuh_> uwumeowmeownyaa: 148

10:47 <SiFuh_> uwumeowmeownyaa: And why ''ln -b a'' Shouldn't it be 'wc -l'

12:42 <uwumeowmeownyaa> SiFuh_: How do you have so few packages installed?

12:47 <SiFuh_> uwumeowmeownyaa: Most of what I don't need isn't installed. So certain unnecessary core ports are removed, certain dependencies that not even required are gone. And other so called 'junk' that shouldn't even exist has been removed.

12:48 <SiFuh_> uwumeowmeownyaa: As to what you want removed, that is entirely up to you. You need to go through everything and see what is needed and what is not.

12:49 <uwumeowmeownyaa> Indeed, ``wc -l'' is a better solution. I made a typo: the command was supposed to be ``nl -b a'', outputting lines with their numbers prepended.

12:50 <uwumeowmeownyaa> SiFuh_: Is reading through the list of installed ports the only way to clean up a system?

12:51 <SiFuh_> uwumeowmeownyaa: Pretty much. If you don't do it yourself then you are relying on maintainers to do it and most of them don't follow the original CRUX way

12:53 <uwumeowmeownyaa> Thank you for the information.

13:05 <farkuhar> uwumeowmeownyaa: For cleaning up the system, there's also the pkg-clean script that Romster wrote for us many years ago. But SiFuh might disagree with its naive approach (trusting that all the ports in the core repo are actually necessary).

13:11 <SiFuh_> farkuhar: Wasn't pkg-clean actually designed for another purpose? Wasn't it created by Romster so that you can have a core CRUX system, build your new or updated ports and their dependencies and when successful, upload the new port or ports. Then use pkg-clean to return your system back to core?

13:17 <farkuhar> SiFuh_: Yes, iirc Romster wrote pkg-clean in the era before containers and virtual machines. Nowadays it's more common to use the latter approach to ensure a clean footprint.

13:37 <SiFuh_> farkuhar: Would be a nice option for "prt-get remove" to have a flag like OpenBSD's "pkg_delete -a" and remove auto installed dependencies not required when you remove a port you no longer wish to use.

13:44 <farkuhar> SiFuh_: You'd have to change the format of the pkgdb to record the reason why each port was installed (explicitly requested by the user, or pulled in by the dependency resolver). Or you could keep the current pkgdb format (to avoid confusing pkgadd and pkgrm and pkginfo), and populate another database with this information.

13:45 <SiFuh_> farkuhar: Or populate a folder like OpenBSD does. :-P But that wouldn't be the CRUX way

13:47 <groovy2shoes> a populated folder is technically a database ;)

13:49 <SiFuh_> groovy2shoes: :-P

18:41 <jaeger> one of my desired features for a pkgutils rework has been explicit vs. implicit installations, still would like to implement that at some point in the future

18:43 <SiFuh_> Good morning jaeger :-P

19:00 <frinnst> so I was never able to rebuild perl. However, removing it and building without having perl installed works.

19:00 <frinnst> asdf perl

19:01 <frinnst> nevermind

19:01 <frinnst> i had trouble with ruby, not perl. these damn gems and stones

19:02 <frinnst> still, I was never able to rebuild RUBY. but removing the installed/broken package and rebuilding works

20:52 <frinnst> jaeger: 2 things with the ISO:

20:52 <frinnst> curl is broken; missing libnghttp2.so.14

20:53 <frinnst> no driver for my nic - mellanox connectx-3

20:53 <frinnst> the curl thing was actually already in 3.7 - i noticed that yesterday when i broke everything

20:56 <frinnst> nic driver would be nice but I guess it's sort of a rarer nic for crux installs

21:14 <jaeger> OK, will take a look. What's the module name for that NIC?

21:25 <cruxbot> [contrib/3.7]: shaderc: updated to version 2024.4