Hi, thanks for all this info!
> Buchan Milne wrote: >>[EMAIL PROTECTED], [EMAIL PROTECTED] wrote: >Increasing microsoft use to decrease Novell use may not be the best strategy, but we >will go with that for the moment. NDS is probably better than AD ;-) No increase of M$ use really...that's all there for other uses I can't do anything about. I'm replacing Novell with linux for file sharing, etc. That is a worthy goal :) >The easiest way is to use the winbind from samba-2.2.4, which will allow you linux >system (not only samba) to see all the users and groups from your windows 2000 >system as normal users. All authentication will also be passed off to the domain >controllers. By using the pam_mkhomedir pam module, you can get pam to create the >home directories if they don't exist whenever anyone connects to a pam-configured >service (which can include samba). That is exactly what I needed. Thank you. Google searches never raised this bit of info. >>Does anyone know how well Samba interacts with the quota system, especially >>with the addendum of an external authentication scheme? > >I have only tested with XFS on linux, and it works as expected, with the bonus that >ACLs work (well, mostly, I have some issues). Are those issues big enough to be concerned about? ><plug type=shameless>Mandrake 8.2 ships with support for winbind (probably the >easiest winbind available), as well as support for ACLs and quotas on XFS. Mandrake >RPMs of 2.2.4 are also available on the samba ftp mirrors. 2.2.4 brings the >advantage of the "default domain" parameter to winbind, which means users can >connect as "username" rather than "DOMAIN\username". This may not affect you for >file service via samba, but simplifies life for people running terminal services or >mail with winbind.</plug> I wondered about this...I was concerned that automatically making homedirs when the username was qualified as DOMAIN\username would try to create homedirs with that name, which would cause all sorts of confusion and ugliness. >We use samba as our domain controller and fileserver on a machine sharing 140GB of >RAID disk to about 65 Windows and linux desktops. This Samba box won't be the DC, but the fileserver issue seems to be solved by what you stated above. We'll be sharing Samba drive space to about 170 WinNT, Win2k and Win98 workstations. >Finally, please read throught the documentation (specifically the winbind-related >stuff in the Samba-HOTWO-Collection, available in the source tarball or probably on >the samba pages also). There is also some doc at >http://mandrakeuser.org/connect/csamba5.html#winbind , but it is horribly out of >date and makes it look more difficult than it is (most of the steps are done for you >with the Mandrake RPMs). Excellent, thanks! Greg
