Hi all. So, I have several Linux machines I'd like to share the same .bash_profile and an Active Directory server (running Windows 2008) with Microsoft Identity Management for Unix. I'm using LikeWise to join the Linux guests to the AD domain which seems to work fine. I'm wondering if there's a way I can tell the Linux guests to share a common .bash_profile, similar, I suppose, to roaming profiles for Windows guests. Or, if there's another way to get the job done, I don't necessarily have to go through AD at all. Just trying to find a way to have each user have their own .bash_profile files presented to them as soon as they login to the Linux guest.

It's been a while so I'll reply even though I know nothing about "Microsoft Identity Management for Unix" or LikeWise,starting with some clarifying questions ...

What do you want to achieve with the shared .bash_profile?

Do you want one .bash_profile to be used by each user, regardless of which Linux system they log on to? Will each user's be different?

Hi catkin and thanks for the reply. The .bash_profile will be catered to each individual user and will be brought in as the accounts are created. Each user will have their own set of aliases they prefer within these .bash_profile files, along with any other personalizations. I wasn't sure whether the hosts could somehow get these files pulled automatically from the Active Directory server - perhaps upon successful authentication the .bash_profile will be sent across or some other way. It doesn't have to involve Active Directory, but that was just my thought process of possible ways to get the end result accomplished.

Anyone?

How are the accounts being created? If that is when you want to copy the .bash_profile file (any reason for .bash_profile rather than the more conventional .bashrc?) then whatever is being used to create the accounts is what you need to hook into. Assuming some hook is available, where is the master copy of .bash_profile to be copied from?

Whatever you do, if the user changes their .bash_profile on one system it will not be updated on others. You could get around this by keeping a master .bash_profile (or a scrippet it sources) on a networked drive ...

Thanks catkin. The accounts are being created with the newusers script, unless you suggest a better alternative. I'm supposing I'll just end up choosing one of the Linux machines that already has the most pristine rendition of the .bash_profile and user accounts present and then just push out from that machine.

The last part you mentioned - "You could get around this by keeping a master .bash_profile..." - can you please elaborate more on what that might look like?

Thanks for your time.

How about yet another idea. Assuming the network can handle the load, you could just centralize the home directories of each machine. Then you have 1 place to distribute everything to, everyone has their personal files no matter which machine they're sitting at, and you simplify backing up documents.

Have you looked into NFS home dirs?

Sorry for delay -- a cyclone took away our electricity for a while. I was thinking of putting the .bash_profile (or a scrippet sourced from a local .bash_profile) on a networked drive along the lines custangro has suggested.