Ludovic Courtès <[email protected]> writes: > Hello, > > Christopher Baines <[email protected]> skribis: > >> Unfortunately, it's not a proper solution, as it obviously breaks when >> you actually want to strip the mount point off so that grub can find the >> right files. > > Is there a way ‘strip-mount-point’ or some higher-level code could > determine whether we actually need to strip the mount point?
So, this is the file-system value that I'm using currently for the store. The information about subvolume is in the options value. (file-system (device (uuid "84fc6b78-d7ff-45df-8659-bef44b5bf0ea")) (type "btrfs") (title 'uuid) (mount-point "/gnu/store") (needed-for-boot? #t) (options "subvol=/gnu/store")) I guess one approach for dealing with this would be to allow directly configuring the stripping of the mount point somehow. Or maybe having some btrfs-file-system record, which could store the subvol option in a more machine readable way. One thing that still makes me uncertian, is how grub actually is trying to find files on the btrfs filesystem. I tried changing the default subvolume to the one containing the store, but that didn't seem to help. Looks like it might not be aware of subvolumes.
signature.asc
Description: PGP signature
