NFS mount issue

[Darryl Moore]

Hmmm, I'm beginning to agree with you. It really becomes an issue with
suspend and then waking up to a new home directory. It could cause a bit
of havic with open gnome, firefox, and OOo files in the home directory.
And other too. Doing a quick lsof shows a lot of .* files open in the
home directory.  For that reason I don't think even what you suggest
below will work either.

I guess what I should do is simply mount the NFS home directory in
/media so it shows up in nautilus,  run rsync periodically & during
suspend/log off, but still use autofs so that I can shed the NFS mount
easily when the network context has changed.

mcr at simtone.net wrote:
>
>   So, basically, their laptop has a local /home/user which is read-only
> to the user.  That /home/user gets it's .* files copied from the network
> /home/user/.* on a regular basis, with perhaps a final rsync during
> shutdown/suspend.   When on the road, the user can not change their
> settings, but they can edit any documents in "local documents"
>
>   To make the /home/user read-only to the user, I suggest that you have
> /real/home as writable, and then use a bind mount with -ro to mount
> it. I think you can do this with the latest kernels.
>
>     >> It will confuse users and piss them off because they won't be
>     >> able to find things.
>
>     Darryl> That is an interesting comment, because part of the goal was
>     Darryl> to make things easier to find.
>
>   Disconnected nomadic computing is hard, because users want things to work, and
> get pissed off if you prevent them from getting their work done.
>   There are some really neat things in NFSv4 that help: but I don't know
> if they are implemented in linux yet.
>
>