Can't you do the following (using /hurd as an example): Without unionfs running on /hurd (which is a directory), you do `ln -s /stow/hurd/hurd/unionfs /hurd/', so /hurd/unionfs is available without unionfs running on /hurd. Once unionfs is running on /hurd, its old (i.e. the content of the directory `/hurd/') isn't visible anymore.
Yes, but this will break horribly if the user for whatever reason considers /stow/hurd a ugly name and changes it to something like /stow/hurd-foo-bar. > One could also store ld.so.1, unionfs, and all other core bits in > /init (or similar), and just use those filenames. You'd also have to frob unionfs's executable then, since it most probably depends on libc.so.0.3, etc., but doesn't have a RPATH for /init/lib/. Compile unionfs as a static executable. _______________________________________________ gnu-system-discuss mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-system-discuss
