Two ideas come to mind:
Elegant:
If I am not mistaken the coda filesystem was
intended to make this kind of network transparency
wrt the filesystem possible. However, I imagine
that you would need to have coda on all environments
(well, at least home network and laptop) to make it work
(someone correct me if I am wrong). You may want to
look into this: http://www.coda.cs.cmu.edu/
Kludge:
It *MAY* be possible to write a shell script that
runs fairly early on in the bootup process that asks
you where you are logged on, then takes the necessary
steps such as nfs mount the /home tree if you are at home,
otherwise maybe move (maintaining ownership/permissions),
say /homecopy to /home, then on shutdown will either unmount
/home from nfs or mv /home back to /homecopy (maintaining
ownership/permissions), depending on your location. You
could store your current location in a file or in an
environment variable during bootup to make shutdown
actions noninteractive.
<DISCLAIMER>
The kludge method seems filled with potential disasters, so
I would *only* do the second method if you are *very* comfortable
with shell scripts and the bootup/shutdown process, etc...
But if done correctly it could work.
</DISCLAIMER>
Chris
Theo Brinkman wrote:
>
> I know you can set things up so to mount /home from a remote machine, so
> that no matter what machine on a network you use, your settings stay the
> same, & all your files are the same. Unfortunately, I'm thinking this
> process might cause problems with using my laptop both on my home
> network as well as the one at work.
>
> How might I go about setting it up so that when I'm on my home network,
> I mount the '/home' tree from my server, but still use a local copy of
> '/home' while I'm at work? How about keeping them both up to date?
>
> - Theo
