l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2003 May 12 02:52

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] NFS Mount Points
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] NFS Mount Points

--- Charles Polisher <cpolish@attbi.com> wrote:
> Jim Angstadt wrote:
> > Hi All,
> > 
> > [ this is a re-transmit.  I burped on the
> first
> > one. sorry of any inconvenience. ]
> > 
> > I've been learning nfs on my home network.  
> > 
> > A Red Hat 9.0 box exports /home/ja just fine.
>  RH
> > 8.0 and 7.2 boxes can mount the export.  All
> dirs
> > under /home/ja, and the files within the
> > subordinate dirs looks fine.
> > 
> > But, I'm having problems with the RH 8 and RH
> 7.2
> > desktops under X.  I think the mounting has
> > overlayed all the dot files and produced
> strange
> > results.
> > 
> > I could export each sub-dir and then mount
> each
> > sub-dir so that I don't step on the dot
> files.  I
> > might not need to do that for all sub-dirs,
> so
> > maybe just a few, like /home/ja/bin,
> > /home/ja/temp, /home/ja/etc, and so forth.
> > 
> > Is this the way that most people do it?  Is
> there
> > a better way?
> That's precisely what is happening, and your
> solution is 
> the way to go.
> Mounting a directory 'hides' the directory it
> mounts on.
> Usually, the mount point is an empty directory
> so the hiding
> isn't obvious -- since there are no files.
> Mounting a level below, such as /home/ja/bin
> does an end-run
> around the problem, unless you've already got a
> /home/ja/bin, in
> which case the same problem happens, just one
> level down. Could
> maybe do:  /mnt/nfs/hostname1,
> /mnt/nfs/hostname2, etc., and then
> in your home dir, symbolic links, "ln -s
> /mnt/nfs/hostname1 foo"
> now when you "cd /home/ja/foo" your files are
> all there.

Hi Charles,

I've already consolidated my bin files on the rh
9 box.  Also, have re-written a few to use
arguments that are pertinent to the box I'm on.

> My preference for the 'dot files': I keep _one_
> home dir with my
> custom, jazzed-up .bashrc, .bash_profile,
> Xcolors,
> .Xdefaults,.Xmodmap, & so on and so forth...
> then link my other
> home dirs' dot-files into that 'master' set.

This sounds interesting.  How do you deal with
different version of nautilus, for example, or
other desktop apps.  Is it trial-and-error to see
which ones can share the same dot files?

Or do you have the same apps on each host?

This seems like the way for me to go.


> That way I always have my settings with me. 
> Even though I keep
> several accounts, eg one for building KDE,
> another for building
> GCC, and so on. Makes the .history easier to
> follow when things
> get off-track.
> -- 
> Algol 60 was not only an improvement on its
> predecessors, but
> also on nearly all its successors.          --
> C. A. R. Hoare
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech

Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.