Hi Matthias,

first of all, samba is full compatible with WinNT, that means that you can
easy integrate a linux fileserver into a winnt domain, without any changes.
You can make a machine account at the domain controller, so that the
password handling is done by the domain controller.

You do not necessarily need acl.... well, it is maybe be good feature, but
at the moment it is a bit tricky to install. First of all you need a
"special" ext2 filesystem which is able to store the additional access
information. When you have this filesystem running, it may be a problem to
back it up, because most of the backup-tools do not save the additional
access information. At the moment it is only possible to use ext2 and XFS
with ACL....

Without ACL it is of course possible to use ext2 and LVM... it works quite
well.

If you think twice about defining your usergroups/user then it is not
necessary to use ACL, in my point of view.

- Tim -






[EMAIL PROTECTED]@VM.MARIST.EDU> on 29.01.2002 16:20:15

Bitte antworten an Linux on 390 Port <[EMAIL PROTECTED]>

Gesendet von:  Linux on 390 Port <[EMAIL PROTECTED]>


An:   [EMAIL PROTECTED]
Kopie:
Thema:    NT server consolidation with samba


Hello,

currently we are evaluating the use of samba in an nt server consolidation
project.
We need to figure out if the samba server is 100 % compatible with our nt
file servers or what differences exists.
We plan to use samba 2.2 with suse and the samba server should be
integrated
as a member in the existing nt landscape ( domain ).

My question is :

Do we need acl controls to offer the same funtionality with samba ?

If yes, are there any experiences with implementing the acl with a kernel
patch ?
What about backup and recovery concepts of the acl's ? Are they supported
by
the TSM client ?

Is it true that only ext2 is working with acl ? Can I use ext2 with LVM ?

What are your experiences,

thanks a lot
Matthias Wittpoth
----------------------------------------------------------------

Erleben Sie die neue RWE Online-Welt unter http://www.rwe.com

Reply via email to