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

["Ellie via gnats" <gnats-admin%NetBSD.org@localhost>]

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

From: Ellie <el%horse64.org@localhost>
To: gnats-bugs%netbsd.org@localhost, misc-bug-people%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Cc: 
Subject: Re: misc/60956: ramdisk-cgdroot.fs seems to check for
 /libdata/firmware/ in the ram disk rather than the mounted cgdroot
Date: Mon, 2 Nov 2026 20:04:10 +0000

 I think there might be a misunderstanding. On the user side, me, chroot 
 was not used at all:
 
 In fact, if I use my chroot script then it works (since then I can 
 symlink it as needed) - this is why I mentioned it. Sorry for that being 
 confusing! The default setup is just straight up ramdisk-cgdroot.fs 
 multiuser boot, and there it breaks.
 
 Regards,
 
 Ellie
 
 On 11/2/26 19:55, Martin Husemann via gnats wrote:
 > The following reply was made to PR misc/60956; it has been noted by GNATS.
 > 
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: misc/60956: ramdisk-cgdroot.fs seems to check for
 >   /libdata/firmware/ in the ram disk rather than the mounted cgdroot
 > Date: Mon, 2 Nov 2026 20:53:35 +0100
 > 
 >   This is by design and unavoidable as long as a chroot(1) is used
 >   to set the "real" root.
 >   
 >   You have to populate the original mount.
 >   
 >   You can create your custom boot filesystem for that, see
 >   
 >   	https://wiki.netbsd.org/security/custom_cgdroot/
 >   
 >   
 >   Martin
 >