Wouldn't a non-domain client just ignore those settings? I mean, if the machine isn't looking (and can't read) a profile, why hide it further?
Another point is that every piece of perl slows down the mythical "minimum machine" of a 486. Regards Craig Foster (As usual my opinions are mine, and you can't have none!) -----Original Message----- From: Darrell May [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 17 October 2001 9:56 AM To: Greg Zartman; [EMAIL PROTECTED]; e-smith-devinfo Subject: RE: [e-smith-devinfo] samba 2.2.2 development Howto Greg Zartman <[EMAIL PROTECTED]> said: > Is it required by e-smith/SME 5.0 for samba to be broken up like this. Currently, YES. This is the default SME5 implementation that is built into their iso. We need to continue to match their iso implementation to keep a clean upgrade path. > If Samba is to be broken up into four pieces, do we need to be > installing samba-swat-2.2.2-1.i386.rpm? Nope, this is for developers only. I'm sure SWAT will get dropped from the 'supported' blade install. > Following are suggestions to your fragments. Specifically, I've > incorporated perl code into fragments that need only be used in PDC > mode. Yup looks nice. Don't know if we need to get so fancy though. Even if those fragments are in by default they don't effect a non-domain smb.conf installation. I welcome comments on this. Should we implement the perl scripted fragments Greg has provided or go plain? Regards, -- Darrell May <snip>
smime.p7s
Description: application/pkcs7-signature
