Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-unix!quintus!sun!pitstop!sundc!seismo!uunet!hi-csc!giebelhaus From: giebelhaus@hi-csc.UUCP Newsgroups: comp.unix.wizards Subject: Re: //host vs "mount point" Message-ID: <38d18d4f.4580@hi-csc.UUCP> Date: Wed, 2-Dec-87 01:05:00 EST Article-I.D.: hi-csc.38d18d4f.4580 Posted: Wed Dec 2 01:05:00 1987 Date-Received: Sun, 6-Dec-87 13:35:22 EST References: <648@tut.cis.ohio-state.edu> <1668@tut.cis.ohio-state.edu> <35000@sun.uucp> Organization: Honeywell CSDD, Golden Valley, MN Lines: 50 Summary: But // is just another directory too. In article <35000@sun.uucp>, brent%terra@Sun.COM (Brent Callaghan) writes: > Another good reason for "just another directory" is that it leaves > open the possibility of having nodes other than host names under > the directory. Consider the following: > > /host/- file systems on other hosts > /home/ - users home directories > /src/ - other source trees > > There's not always a need to know the host on which a file > resides. There are good reasons for hiding this information > e.g. because you don't know the disk partition a file is in > the administrator can relocate disk partitions freely. > Similarly a /home directory allows a user to move to another host > and have his/her home directory mounted automatically. But the // directory is just another directory. It is simply a directory above the / directory. The only things special about it is I cannot reference a remote // directory (I can only reference the / directory and below) and the // name its self. I can put links in or anything I want. I'm a bit confused about how the /home directory works. We have about 30 suns and I have been trying to figure out how to arrange the cross mounts and such. We have four servers and each server has at least one partition of user files. I can't figure out how to get the path to the home directory look the same for all people no matter what server they log in on and still make it so I can move them from server to server without them knowing. What I am doing now is making links from a /udd directory. All users have a link in the /udd directory to either //host/user/user-name on the apollo or /n/host-name/user-name. host-name is the name of the host, but it is the directory (partition) on that host with the user files in it. I have some steps so that the loss of the /udd dir is not so bad like putting the /n/host-name/user-name in the /etc/passwd file and keeping replicas of the /udd dir. I'm still not happy with this though. Is there a better way? P.S. About my previous message, I do know the lock protocol is seperate from nfs. I meant to say it was added for use with nfs, not a part of nfs which could not be seperated. I'll put more effort in remaining clear in the future. -- --------------------------------- UUCP: {uunet, ihnp4!umn-cs}!hi-csc!giebelhaus ARPA: hi-csc!giebelhaus@umn-cs.arpa Nobody I know admits to sharing my opinions. I don't even have a pet.