Messages in this thread | | | Date | Wed, 14 Mar 2001 13:11:05 -0500 (EST) | From | Alexander Viro <> | Subject | Re: (struct dentry *)->vfsmnt; |
| |
On Wed, 14 Mar 2001, Andreas Dilger wrote:
> The AIX vgimport will not corrupt /etc/fstab with duplicate mounts, nor for > that matter with duplicate LV names (AIX has a single namespace for all LVs). > If a conflict is found with an LV name, a new name like "lv01" is used (the > LV names are not that important anyways). I'm not sure what would > happen with a duplicate mount point (whether it would pick a new name, or > simply leave it out of /etc/fstab), but it isn't too hard to think of > easy ways to fix this (e.g. /home01 or /mnt/vgname/home or whatever).
[snip the rest of description]
Excuse me, but doesn't it scream "userland"? IOW, is there any reason to do that in the kernel? If you want to spread /etc/fstab all over the place storing bits in relevant filesystems - fine, you even don't need to bother with superblocks. Just teach mount(8) to put the mountpoint into /.last.mounted and be done with that...
It's a policy question - if somebody wants to play with such schemes he can do it in the place where policy stuff belongs. I.e. in userland. 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...
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/
| |