08:27 <cruxbot> [core.git/3.7]: libcap: update to 2.68

08:27 <cruxbot> [opt.git/3.7]: ruby-sqlite3: update to 1.6.2

08:27 <cruxbot> [opt.git/3.7]: iwd: update to 2.4

08:27 <cruxbot> [opt.git/3.7]: ghostscript: update to 10.01.1

22:37 <mike_of_earth> I haven't spotted it in my browsing of the crux site... what init does CRUX use?

22:37 <jaeger> sysvinit

22:47 <Menelkir> hi, does crux have a root tar to be used in a chroot env?

22:49 <jaeger> Hi. If you mean statically linked, no, not by default

22:50 <Menelkir> No, I mean a tar that I can just untar and chroot into it, for test purposes instead of using a full fledged VM

22:51 <jaeger> Oh, I see. I'm dumb. :)

22:51 <jaeger> Again not by default but that's trivial to make from the ISO

22:54 <jaeger> I can give you an example if you like

22:54 <Menelkir> yes but using a ISO I would have to boot the entire machine and choose the directory, right?

22:54 <jaeger> no

22:55 <jaeger> You can mount the ISO via loopback, then install the packages from it into a directory that will be your base

22:56 <jaeger> There's a copy of pkgutils built on the ISO you can use, even from another distro, or you can simply untar the packages into the right place (though they're not tracked by the package database this way)

22:57 <Menelkir> I'm looking to the iso contents now, it seems there's a rootfs.tar.xz there, isn't possible to use it as an initial image or it's incomplete?

22:57 <jaeger> That one's designed specifically for the installation environment, it's not the same as an installed system

22:58 <Menelkir> yeah i thought that was something like it, to fill a ramdisk and start the install or something like this

22:58 <jaeger> yeah, exactly

22:59 <cruxbot> [opt.git/3.7]: [notify] nvidia-fb: updated to version 530.41.03, use pkgadd -u -f to update library symlink ownership

22:59 <cruxbot> [compat-32.git/3.7]: [notify] nvidia-fb-32: updated to version 530.41.03, use pkgadd -u -f to update library symlink ownership

23:01 <jaeger> Something like this, without pkgutils installed: mkdir target; mount -o loop,ro <ISO> /mnt; for P in /mnt/crux/core/*.pkg.tar.*; do tar -C target -Jxvf ${P}; done

23:02 <Menelkir> but those packages will registered with the package manager after that? I mean, can I register then later to not be orphans?

23:03 <jaeger> You could, but if you're willing to install pkgutils first, it's even easier

23:03 <jaeger> Something like: mkdir -p target/var/lib/pkg; touch target/var/lib/pkg/db; mount -o loop,ro <ISO> /mnt; for P in /mnt/crux/core/*.pkg.tar.*; do pkgadd -r target ${P}; done

23:03 <Menelkir> I was thinking about something like this: untar the pkgutils into the lets say /mnt/crux, and then a for with ./pkgadd -r <chroot path> -c <chroot path>/etc/pkgadd.conf $for_var

23:04 <jaeger> Sure, should be able to do that

23:04 <jaeger> pkgadd.conf won't existr in <chroot path> until you copy it yourself or install pkgutils, but you could also use any other path where it already exists

23:05 <jaeger> (like the pkgutils source)

23:05 <jaeger> Incidentally this is pretty much how I make a clean docker image for crux work