> Obviously, the whole vgimport stuff is going to be in userland. The only
> part that needs to go in the kernel is storing the mountpoint in the
> filesystem superblock. It is _not_ OK to just put it in /.last.mounted.
> Quite often a data/application VG is moved independent of the root filesystem.
> The info needs to stay with the filesystem itself.
Sorry - .last.mounted in the root of filesystem, indeed.
> > Since the reading side contains a bunch of heuristics
> > (obviously depending on the local naming policy for temp. mountpoints,
> > for one thing) you don't need anything special on the writing side...
>
> The writing side can't be done in userland without basically making
> mount(8) know about the superblock layout of each and every filesystem:
That's a wonderful reason to put it _not_ into superblock... OK, what's
wrong with the variant above?
Cheers,
Al
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/