Hi Daniel, Daniel Baumann <dan...@debian.org> (2025-01-14): > Cyril Brulebois <k...@debian.org> wrote: > > anything stored in /dev goes away when (re)starting.
What I meant here is that in general, anything that's manually added to
/dev goes away when rebooting (restarting); but that's also true in our
case, when d-i “just” starts.
> I'm afraid I don't understand - would you mind explaining it to me?
>
> I figured that when haveged-udeb is installed via anna, that postinst is
> then creating the directory. What do you mean with "restarting"?
From an earlier reply:
No, this doesn't work: you cannot ship subdirectories of /dev in a
Debian package and expect it to work, that's a directory managed by
udev.
In this specific context, the directory exists in the tree where d-i
is built, it also exists in the initramfses that are built, but it's
masked at runtime, probably as soon as udev kicks in and the /dev
mountpoint is mounted as devtmpfs.
To expand on this a bit, we start haveged at the very beginning of the
d-i runtime, so it's pulled during the build of the d-i package, not at
runtime. So “the directory exists in the tree where d-i is built” means
e.g. build/tmp/netboot-gtk/tree/dev/ in the src:debian-installer build
tree, for the netboot-gtk target; and even if the contents of the /dev
directory there makes it into the target system, that's getting masked
when d-i starts, once udev kicks in and /dev is mounted as a tmpfs on
top of it.
> > I'd expect having to detect + fix the missing directory at runtime
> > to be the (only?) solution.
>
> done that in 1.9.19-8.
Thanks, I'll check that once I have a little more time.
Cheers,
--
Cyril Brulebois (k...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
