07:03 <elge> meow. there's no chpasswd binary available?

07:04 <elge> I installed all the .tar.xz packages from the release and there's `passwd` but no `chpasswd`

07:05 <SiFuh> There is a chgpasswd though

07:05 <SiFuh> But I think that is for group

07:12 <SiFuh> elge: if you look in the /usr/ports/core/Pkgfile it has been intentionally removed on line 42

07:14 <SiFuh> I am not sure why it has been removed. That is up to the core development team. If you want it you can remove the chpasswd entry for the command and the man page and rebuild it.

07:22 <elge> sifuh, thanks. I installed using some kind of bootstrapping hence I do not have /usr/ports populated

07:22 <elge> how to I deploy /etc/ports?

07:23 <jaeger> elge: the 'ports' package, generally

07:23 <SiFuh> edit /etc/pkgmk.conf /etc/prt-get.conf and run 'ports -u'

07:23 <jaeger> as well as rsync nad git packages for the drivers

07:24 <jaeger> out of curiosity, how did you 'install' the packages?

07:25 <elge> jaeger, extracting core/*.tar.xz onto a mountpoint then tuning the few book files (e.g. disable hwclock) for running a XEN guest

07:25 <elge> boot* files

07:26 <elge> I just miss opt/iputils and chpasswd)

07:27 <jaeger> Ah. Even in that case I would recommend using pkgutils

07:27 <elge> sifuh, thanks, ports -u just worked out of the box

07:28 <jaeger> Installing the system just by extracting will work but you lose a bit of package management (no initial package database)

07:28 <elge> indeed! that error I just got

07:29 <elge> how to create the initial pkg db?

07:30 <jaeger> Simplest way would be 'mkdir -p /var/lib/pkg; touch /var/lib/pkg/db'

07:31 <jaeger> It's easy to do this at the point that you extracted the packages to the mountpoint, for future reference.

07:32 <elge> sure

07:32 <jaeger> something like 'mkdir -p <target>/var/lib/pkg; touch <target>/var/lib/pkg/db; for P in core/*.pkg.tar.xz; do pkgadd -r <target> ${P}; done'

07:32 <jaeger> That way they populate the package database from the start

07:33 <jaeger> It can be done with a non-crux distribution, even, as pkgadd is statically linked

07:38 <elge> jaeger, it's fine I can otherwise chroot pkgadd $P - thanks

07:39 <jaeger> fair enough

18:23 <js> Hi! Is there any way to verify the download of the ISO? I couldn't find a signature, not even a hash on the webiste. The only thing that I could fine is as .sha256 file -- on the same mirror where I got the .iso from, so completely useless.

18:25 <jaeger> Hi. At the moment, nothing other than the sha256

18:34 <js> cc004425a2529b706795a95cbd59d3a8208d80441faa62703bad2c02a5671afc

18:34 <js> Would that be the one for the current ISO?

18:35 <ppetrov^> are you looking for the updated install iso?

18:38 <js> just the last release

18:38 <js> so that's not it?

18:42 <ppetrov^> https://crux.nu/Main/Download

18:42 <jaeger> will check, I don't recall

18:42 <ppetrov^> http://ftp.spline.inf.fu-berlin.de/pub/crux/crux-3.7/iso/crux-3.7.iso

18:43 <jaeger> that's the correct one for the release ISO, yeah

18:43 <jaeger> You can also find an "updated" ISO at https://crux.ninja/updated-iso/ which is basically the same, just has updated packages since the release and sometimes a newer kernel

18:45 <js> jaeger: Thx, I was looking for the official release ISO 🙂. Thx for verifying!

18:47 <jaeger> No problem

18:47 <jaeger> They're both built with the same process and by the same person (me) for reference

18:53 <jaeger> And while saying that on the internet is of course zero guarantee, just mentioning it as a data point