On Fri, Feb 17, 2006 at 04:02:01PM -0800, Steve Langasek wrote: > On Thu, Feb 09, 2006 at 03:41:04PM +1100, Anand Kumria wrote: > > On Wed, Feb 08, 2006 at 01:15:44AM -0800, Steve Langasek wrote: > > > On Tue, Feb 07, 2006 at 07:02:03PM +1100, Anand Kumria wrote: > > > > > Please include samba.schema (in the examples/LDAP) directory in > > > > samba-common at /etc/ldap/schema as this will make it simpler for > > > > administrators to setup PDC and BDC synchronised with each other and/or > > > > via a third LDAP machine. > > > > > I recommend samba-common as the package is lightwight enough that it can > > > > be installed on an LDAP machine that wouldn't otherwise have anything > > > > samba related on it. > > > > For my part, I would rather see a separate "smb-ldap" package to provide > > > this schema file and other integration bits. I started on one once, but > > > haven't gotten anywhere due to lack of time. > > > What would be the other integration bits that samba could provide? > > Assuming the DC and LDAP server are on the same system (the common case), > autoconfiguration of the passdb backend; auto-loading of the schema file; > autoconfiguration of LDAP credentials.
well, part of that is editing another package's config file; part of that is convincing the other package maintainer to make some debconf variables shared. An 'smb-ldap' might be a good idea but I can't see why (as a start) the samba.schema file isn't included in *some* package. I'd prefer samba-common since the package is fairly lightweight. Cheers, Anand -- `When any government, or any church for that matter, undertakes to say to its subjects, "This you may not read, this you must not see, this you are forbidden to know," the end result is tyranny and oppression no matter how holy the motives' -- Robert A Heinlein, "If this goes on --" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
