John Plocher wrote:
I think I am missing something here.
No I missed the intent of what you said. I thought you were talking
about reprovisioning from being a local only system to being in a
networked environment. Rather than the mobile case where sometimes you
want /home managed by automount and a network nameservice and sometimes
you don't.
If the system is changed to have a local filesystem mounted as /home,
then the automounter can't also use that point to mount /home/otherpeople,
right?
Yes and no, it depends what kind of map auto_home is.
If so, when I move my client laptop from home to work (where home implies
no NIS/NFS and work implies the opposite), then I'm stuck, right?
If you did only what I suggested yes you wouldn't get /home/user mounts
for /home/darrenm when you were at work.
I'd have to move the filesystem mount from /home to /export/home,
change my auto_home map and update nsswitch.conf.
Right. In that case the addition of 'plocher localhost:/export/home/&'
is the best fix and is EXACTLY what smc(1M) already does if you use that
to create your users!
Contrast that to today, where I mount the local filesystem on /export/home,
set up nsswitch.conf to use "files", add an entry to auto_home for
~plocher,
and, when I drop by the office, I simply change nsswitch.conf, change the
entry to "files NIS", and run ypinit....
You shouldn't need to run ypinit every time just :
svcadm enable -t nis/client
[ note the -t so that when you boot up at home again it will stay
disabled ].
you can even have a single nsswitch.conf entry for automount like this:
automount: files nis [UNAVAIL=return]
that means you don't need to change nsswitch.conf.
--
Darren J Moffat
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
