![]() | |||||||||||||
Messages in this thread |
Followup to: <200201181212.g0ICCGq14563@bliss.uni-koblenz.de> By author: Rainer Krienke <krienke@uni-koblenz.de> In newsgroup: linux.dev.kernel > > Now think of a setup where no user directory mounts are configured but the > whole directory of a NFS server with many users is exported. Of course this > makes things easyer for the NFS-system since only one mount is needed but on > the client you need to create link trees or something similar so the user > still can access his home under /home/<user> and not something like > /home/server1/<user>. Moreover even if you create link trees when you issue > commands like pwd you see the real path (eg /server1/<user>) instead of the > logical (/home/<user>). Such paths are soon written into scripts etc, so that > if the user is moved sometime later things will be broken. > You simply loose a layer of abstraction if you do not mount the users dir > directly. The only other solution I know of would be amd. Amd automatically > places a link. But since we come from the sun world, we simply uses suns > automounter and there were no problems up to now. > This can easily be resolved with vfsbinds. Even Sun has a specific syntax in their automounter to deal with this (server:common_root:tail). If I ever do another autofs v3 release I will probably try to incorporate that via vfsbinds. -hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - 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/ | ||||||||||||
| Last update: 2005-03-22 12:15 [W:0.396 / U:0.570 seconds] ©2003-2008 Jasper Spaans | |||||||||||||