On Tue, 2009-06-30 at 10:55 -0500, Nicolas Williams wrote: > On Tue, Jun 30, 2009 at 10:13:34AM -0400, Moore, Joe wrote: > > The global zone could be the one running automount. Since it knows > > what host is "local", it'll convert the nfs mounts to lofs > > automagically. > > > > For each zone, add the zone's automount entries to > > global:/etc/auto_master as /zonepath/root/home +auto_home > > vers=3,nosuid (for example) > > > > Haven't tried it. It would muck up NFSv4 identities, and blur the > > lines between the global zone administrator and a local zone admin. > > The problem with this is that it takes something important (sysadmin > independence) away from zones to fix a relatively minor problem and > greatly complicates the automounter and g-z administration in the > process. For example, the automounter would now have multiple distinct > -hosts mounts to implement, and we'd have to augment the mount(2) > syscall so that the zone ID into which the mount should be made can be > passed by the automounter in the g-z (so that we don't "muck up NFSv4 > identities"), and so on.
I'm sorry if I miss the subtleties of the context (or implementation for that matter), but isn't the problem here the fact that mount tables are not really per-zone? They are not really virtualized they are just filtered. Thanks, Roman. _______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
