[csw-maintainers] New and Improved: Samba

[Laurent Blume]

Hello all,

I've just pushed an experimental Samba 3.6.16 there:
http://buildfarm.opencsw.org/experimental.html#samba

I'm hoping to make it the new default soon.

Here are the changes, not huge ones, but useful:
   - include patch for group sorting:
https://bugzilla.samba.org/show_bug.cgi?id=7588
     Not a Samba bug per se, but a limitation of S10/OI that the patch 
works around;

   - Rename nss modules to the Solaris standard (nss_name.so.1), rather 
than the inadequate libnss_name.so.1 that was used before;

   - Add nss_wins.so.1 (following Solaris Samba there, it probably had 
been overlooked);

   - Since they're not libraries, and the .1 is defined by the system, 
both above are grouped into a more neutral CSWsamba-nss package, 
replacing CSWlibnss-winbind1;

   - Create system symlinks, to make it more usable: the NSS modules 
above are used in nsswitch,conf, which will look in /usr/lib and 
/usr/lib/64 only, also, PAM modules in pam.conf will be looked for in 
/usr/lib/security and /usr/lib/security/64. To avoid the users tinkering 
with those, I made two new special packages containing only symlinks: 
CSWsamba-nss-system-links & CSWsamba-pam-system-links
They create /usr/lib/nss_winbind_csw.so.1, 
/usr/lib/security/pam_winbind_csw.so, and so on. The links are relative, 
so they can be used properly with different rootpaths. They add the _csw 
suffix to the name to avoid conflicting with the Solaris packages there.
To use NSS, they'll be winbind_csw and wins_csw in nsswitch.conf, to use 
PAM, pam_winbind_csw.so and pam_smbpass_csw,so in pam.conf.

Who is using any of those to validate all? I can't test all of it 
myself, I don't have the infrastructure :-)

Cheers,

Laurent