Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode
Hello,
Johannes Schauer Marin Rodrigues, le ven. 20 déc. 2024 06:53:16 +0100, a ecrit:
> Quoting Samuel Thibault (2024-12-05 18:22:11)
> > > you are creating that image manually right now? How do you do it?
> >
> > Yes, see http://cdimage.debian.org/cdimage/ports/latest/hurd-i386/debian-hurd.img.txt
>
> oh no! :D
:D
> I looked into how that can be automated. I think you can do what you want by
> using unattended installations with debian-installer.
That can probably be done, yes.
> qemu-system-i386 -net user,hostfwd=tcp:127.0.0.1:2222-:22 -net nic,model=e1000 -m 1G \
> -kernel gnumach -append "TERM=mach-gnu-color auto-install/enable=true debconf/priority=critical netcfg/get_hostname=hostname netcfg/get_domain=domain passwd/root-password=r00tme passwd/root-password-again=r00tme passwd/user-fullname=user passwd/username=user passwd/user-password=insecure passwd/user-password-again=insecure pkgsel/run_tasksel=false popularity-contest:popularity-contest/participate=false grub-installer/bootdev=/dev/sda" \
> -initrd 'initrd.gz $(ramdisk-create),./ext2fs.static --multiboot-command-line=${kernel-command-line} --host-priv-port=${host-port} --device-master-port=${device-port} --exec-server-task=${exec-task} -T typed gunzip:device:rd0 $(task-create) $(task-resume),./exec.static $(exec-task=task-create)'
This seems to be missing -drive file=disk.qcow ?
> Apologies for having to post a screenshot of qemu. I haven't yet figured out
> which options I have to pass to hurd to get output on the serial line that
> qemu prints to the terminal with -nographic.
You can append console=com0 to the kernel options.
> The input to the process is netinst.iso. How (and by whom) is that generated?
That's produced by the debian-cd package, from the output of
debian-installer's build_cdrom_grub target.
> > > A benefit of genext2fs is, that it produced bit-by-bit reproducible output
> > > automatically.
> >
> > mke2fs doesn't?
>
> It can if you pass it some extra options which I would not call "automatically"
> anymore. You also need to feed mke2fs a tarball. It is probably a bug that
> mke2fs cannot create reprodicible disk images when given a directory, even with
> the special options, but I have not yet figured out how to fix it, so I work
> with tarballs. The special options are -U and -E hash_seed=... The former gives
> a non-random uuid to the filesystem and the latter a non-random seed for the
> internal hash functions.
Ah, sure, you at least need a non-random uuid indeed :)
Samuel
Reply to: