00:39 <CleverTom> Alright, I'm sorry to bug you again (especially considering that I've likely made another stupid mistake this time as well, and I just don't know about it), but I just attempted recompiling my kernel with virtualbox display drivers... everything went smoothly; I followed the same instructions as earlier. For some bizarre reason, though the rest of the boot process goes smoothly, the terminal login prompt

00:39 <CleverTom> does not appear. There's no error message whatsoever. I'm sure I'm booting off the new kernel, as I enabled the linux startup logo on this one, and it showed. I checked dmesg, and there's no sign of an error. I think it's likely hung, as I'm unable to switch virtual terminals when the messages stop. Is this a common error during (likely botched) recompilations?

00:40 <CleverTom> Again, I apologize sincerely, if I'm being much too insistent, or annoying.

00:53 <CleverTom> I suppose I'll do a re-install anyways.

00:53 <CleverTom> Sorry about that.

02:22 <jaeger> Doesn't hurt to ask, just a slow channel, people are AFK a lot and spread over many timezones

11:26 <r0ni> do you have an initrd?

11:27 <r0ni> ahh shit was scrolled up, he's gone anyway

12:36 <ppetrov^> r0ni, how do you create an initrd on CRUX?

12:41 <r0ni> with dracut

12:43 <r0ni> somewhere i have a script from emmitt1 to manually make a initrd as well, but i've basically moved to dracut on everything i use... nice and simple and works

13:34 <ppetrov^> but nothing like Slackware's script?

17:38 <cruxbot> [contrib/3.7]: gitui: 0.25.0 -> 0.25.1

17:38 <cruxbot> [contrib/3.7]: python3-pydantic: 2.6.1 -> 2.6.2

17:38 <cruxbot> [contrib/3.7]: pandoc-bin: 3.1.12 -> 3.1.12.1

17:38 <cruxbot> [contrib/3.7]: botan: 3.2.0 -> 3.3.0

17:38 <cruxbot> [contrib/3.7]: czkawka: 6.1.0 -> 7.0.0

17:38 <cruxbot> [opt/3.7]: c-ares: 1.26.0 -> 1.27.0

17:38 <cruxbot> [opt/3.7]: giflib: 5.2.1 -> 5.2.2; new dependency: imagemagick

17:38 <cruxbot> [opt/3.7]: jasper: 4.2.0 -> 4.2.1

17:38 <cruxbot> [opt/3.7]: libsecret: 0.21.3 -> 0.21.4

17:38 <cruxbot> [opt/3.7]: libunwind: 1.8.0 -> 1.8.1

18:08 <cruxbot> [compat-32/3.7]: libffi-32: 3.4.5 -> 3.4.6

18:08 <cruxbot> [compat-32/3.7]: libnm-32: 1.44.2 -> 1.46.0

18:08 <cruxbot> [compat-32/3.7]: libpcre2-32: 10.42 -> 10.43

18:08 <cruxbot> [compat-32/3.7]: libunwind-32: 1.8.0 -> 1.8.1

18:08 <cruxbot> [compat-32/3.7]: mpg123-32: 1.32.4 -> 1.32.5

18:18 <cruxbot> [contrib/3.7]: zjstatus: 0.12.0 -> 0.13.0

18:38 <deltahotel> hi, I reinstalled my system with crux-3.7-updated.iso and wanted to know how often I need to update the packages?

18:39 <deltahotel> as often as possible?

18:43 <cruxbot> [compat-32/3.7]: libunwind-32: removed libexec dir

18:44 <cruxbot> [opt/3.7]: libunwind: moved libexec dir

18:55 <ukky> deltahotel: there is no strict requirement to do updates often. My last full system update was done on Dec 29, 2023.

18:55 <farkuhar> deltahotel: it's your system, you get to decide how often to update the installed packages. If you subscribe to the crux mailing list, you'll receive notifications about updates that patch a known vulnerability.

20:26 <cruxbot> [contrib/3.7]: ipmitool: fixed IANA PEN registry, added multiple patches

20:57 <cruxbot> [contrib/3.7]: python3-poetry: added missing dependency: python3-fastjsonschema

20:57 <cruxbot> [contrib/3.7]: python3-fastjsonschema: initial commit, version 2.19.1

21:32 <cruxbot> [contrib/3.7]: act-runner: initial commit, version 0.2.6

21:41 <cruxbot> [contrib/3.7]: ibus: #4 depend on libayatana-appindicator instead of libappindicator-gtk3

21:44 <cruxbot> [contrib/3.7]: libido3: closes #4 -> dropped

21:44 <cruxbot> [contrib/3.7]: libindicator-gtk3: #4 -> dropped

21:44 <cruxbot> [contrib/3.7]: libappindicator-gtk3: #4 -> dropped

23:22 <cruxbot> [contrib/3.7]: tea: initial commit, version 0.9.2