[K12OSN] smbldap - using a separate /home file server

[Rob Owens]

I hadn't thought about redefining $HOME to a local resource for the few
local admins.  I'll give that some thought.

I don't want to SMB mount $HOME.  I want SMB access to $HOME from
Windows.  I'll use NFS if I want to provide $HOME to another Linux server.

Two things I failed to mention in my original post:

1)  There is no need for users to log in directly to authentication
server, so having $HOME files for them there is pointless (even if it is
just over NFS).

2)  I'm trying to package the authentication server as a virtual
machine, to be distributed to a few different companies.  So I want to
reduce its interaction/dependency on other machines.  This is why I'm
hesitant to NFS mount /home -- I'd have to specify an IP address of the
NFS server, which will be different in every installation.  I'm trying
to keep it as simple and modular as possible.

-Rob

David L. Willson wrote:
> Statement:  It seems to me to be easier to redefine $HOME to a local resource for the few local admin users and continue the "normal" NFS mount of /home for the rest, than to network mount $HOME, but over a different protocol, for everyone.
> 
> Question:  Have I misunderstood what you're trying to do?  As I read your message, you want to SMB mount $HOME for everyone, rather than NFS mount /home for the whole system.  Is that right?
> 
> Suggestion:  Or, couldn't you just create home folders for the local admin users in the /home directory on the root partition, and then only use them when the network is down.  They wouldn't affect you when the network is up and /home is NFS mounted.
> 
> I recommend strongly against SMB mounting $HOME.  SMB permissions and *nix file permissions are not identical.  NFS perms and *nix file perms are identical.  Either way, you're network dependent, but SMB buys you an un-needed level of complexity.
> 
> ----- Original Message -----
> From: "Rob Owens" <rob.owens at biochemfluidics.com>
> To: "Support list for open source software in schools." <k12osn at redhat.com>
> Sent: Wednesday, November 19, 2008 9:38:08 AM GMT -07:00 US/Canada Mountain
> Subject: [K12OSN] smbldap - using a separate /home file server
> 
> I'd like to have samba/ldap authentication, but I want my user's home
> directories on a separate server.  I do not want to NFS mount /home on
> the samba/ldap server, because I want to ensure that the local admin
> users have access to a home folder even if the network is down.
> 
> On the samba/ldap server, I'd like to eliminate the [homes] share.  On
> the file server, of course, I would create a [homes] share.
> 
> Can anyone tell me how to accomplish this?
> 
> -Rob
> ********************************************************
> 
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. If you are not the addressee, any disclosure, reproduction,
> copying, distribution, or other dissemination or use of this transmission in
> error please notify the sender immediately and then delete this e-mail.
> E-mail transmission cannot be guaranteed to be secure or error free as
> information could be intercepted, corrupted lost, destroyed, arrive late or
> incomplete, or contain viruses.
> The sender therefore does not accept liability for any errors or omissions
> in the contents of this message which arise as a result of e-mail
> transmission. If verification is required please request a hard copy
> version.
> 
> ********************************************************
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
********************************************************

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. If you are not the addressee, any disclosure, reproduction,
copying, distribution, or other dissemination or use of this transmission in
error please notify the sender immediately and then delete this e-mail.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted lost, destroyed, arrive late or
incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message which arise as a result of e-mail
transmission. If verification is required please request a hard copy
version.

********************************************************