Re: misc/60956: ramdisk-cgdroot.fs seems to check for /libdata/firmware/ in the ram disk rather than the mounted cgdroot

["Taylor R Campbell via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR misc/60956; it has been noted by GNATS.

From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
To: Martin Husemann <martin%duskware.de@localhost>
Cc: "David H. Gutteridge" <david%gutteridge.ca@localhost>,
	Ellie <el%horse64.org@localhost>, gnats-bugs%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost
Subject: Re: misc/60956: ramdisk-cgdroot.fs seems to check for /libdata/firmware/ in the ram disk rather than the mounted cgdroot
Date: Tue, 3 Nov 2026 14:35:52 +0000

 > Date: Tue, 3 Nov 2026 15:30:19 +0100
 > From: Martin Husemann <martin%duskware.de@localhost>
 > 
 > On Tue, Nov 03, 2026 at 02:26:54PM +0000, Taylor R Campbell wrote:
 > > It should not be a matter of asking users to manually assemble their
 > > own custom cgdroot.fs from sets or a custom build -- we should have a
 > > systematic way to handle this.
 > 
 > Or do the magic root pivot w/o chrooting ;-)
 
 This doesn't help.  Whether userland does chroot or mounts a pivot
 root or dances the waltz, the kernel doesn't know (a) that instead of
 running config_mountroot hooks as soon as cgdroot.fs is mounted, it
 has to wait for userland to mount the real root; or (b) when userland
 has mounted the real root and it can finally run the config_mountroot
 hooks.