On 11/27/05, Jakub Jirku <[EMAIL PROTECTED]> wrote:
> > As for /home, that's the mount point onto which the
> > AutoMounter mounts users' home directories.
> >
> > You see, in any environment where you have more than
> > one PC-bucket, you'll probably want to implement a
> > central file server, usually with some sort of a big
> > RAID, that, among other things, will serve up your
> > users' home directories. Sun, as the inventor of NFS,
> > has defined /export/ and /export/home/ as the points
> > from which resources are shared (exported). So
> > instead of trying to figure out which server to mount
> > to and where, with the AutoMounter it's a uniform
> > location, namely /home.  This in turn makes it
> > consistent across multiple systems and your files are
> > always remotely mounted on the same mount point
> > (/home).  It was designed this way to abstract the
> > physical location.
> > Point in case: if you set up the AutoMounter on the
> > very system that your home directory is on, the
> > AutoMounter will simply NFS loopback-mount
> > /export/home under /home (in a somewhat complex way,
> > but this is abstracted from you as the user).
>
> I understand that. What I don't understand is why have loopback-mounted 
> directories when you login directly to computer and when you're using shared 
> /home, why not export /home directly.

what happens when you someone logs in from a different computer...  it
doesn't actually mount /export/home .. it loopback/nfs mounts
/export/home/username so you can have 100's of users from 100's of
servers.

another case where automounter makes sense these days is when you are
using zones. you can share your home directory to non-global zones. 
and they only see one user.. not all users home directory.. and only
when the user is logged in.. so its a security protection.

James Dickens
uadmin.blogspot.com

>
> Anyway, let's say it's a tradition. There is no need to argue about it.
>
> > Did you happen to read my previous post with a
> > recount of the /proc classic?
>
> I'll take a look.
> This message posted from opensolaris.org
> _______________________________________________
> opensolaris-discuss mailing list
> [email protected]
>
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to