extending nss and examples/nss a bit

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tridge at samba.org wrote:

| In the meantime, having these additional functions in
| our nss library does no harm at all, and puts us on track
| to an eventual situation where SIDs become first class
| citizens in the POSIX world. New standards have
| to start somewhere :-)

If the idea is to push a new standard, then nss_winbindd
is ok.  I though this was the case to start with
but then after talking to Volker I had thought this
was not the case.  Specifically for some of the newer
winbind calls like getting the short form of a domain name.

And after reading Luke H's comments, actually extending
the NSS interface seems reasonable.  My only objection was
exporting functions fro an NSS library that had nothing
to do with the NSS interface and could not be used except
by loading the lib directly.


| I would very much like to avoid having to have a
| header that defines Samba specific structures and expose
| that to 3rd party applications. Having a header that
| provides some prototypes is OK I think

I actually just meant function prototypes and not any
fancy structures.  I agree that this would be a bad idea
and put us back in the same situation we are trying to
avoid.



- --
cheers, jerry
~ ----------------------------------------------------------------------
~ Hewlett-Packard            ------------------------- http://www.hp.com
~ SAMBA Team                 ---------------------- http://www.samba.org
~ GnuPG Key                  ---- http://www.plainjoe.org/gpg_public.asc
~ "If we're adding to the noise, turn off this song" --Switchfoot (2003)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFABUwjIR7qMdg1EfYRAhZIAKDsEeMvq3pFPieVkYcoFesS6P6fnQCfbKc1
8H/rPe0KUhBnPMT6L1gx6gM=
=aluk
-----END PGP SIGNATURE-----