If one were to standardize on a specific window manager/desktop environment,
one could accomplish much of the same effect as 'windows domain control',
including some control over the desktop environment/settings. Given the
following example for kde:
Typical Linux Desktop:
/home mounted via NFS
- user homedirs exist in NFS share
/home/kde - either simlink'd or configured at compile time to the equivelent
of /usr/local/share/kde, (kde 'default'/'master' settings)
Users, groups, passwords, MTA aliases, etc.. stored in LDAP, accessed using
pam_ldap & nss_ldap combined.
Poof! - You've got yourself a 'linux domain controller', assuming the end-user
never has root access, you could with a little work really tweak what they
can and cannot access using a given window manager/desktop environment by
write-protecting config files, etc.
--
Nathan Vidican
[EMAIL PROTECTED]
Windsor Match Plate & Tool Ltd.
http://www.wmptl.com/
On Monday 29 August 2005 13:46, [EMAIL PROTECTED] wrote:
> ncronization does not equal 1:1 the functionality of roaming
> profiles. Roaming profiles in conjunction with system policies let the
> admin extert a
> great deal of control over the user's experience - this isn't really
> possible
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
