-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am currently running Samba 3.0.11 compiled for HP-UX 11i (PA2.0). I am
looking at upgrading to the most current version of Samba, but I see
that HP has finally caught up with the rest of the planet and is now
offering 3.0.22 with select fixes from 3.0.23. This is decent news
because upgrades were often problematic on HP-UX and I will have HP's
theoretical support behind me if I have a major problem.
However, I note that HP does not include pam_smbpass, which I'm
currently using. The question that is relevant to the Samba community is
this: can I easily separately build this module without having any major
problems? From what I could tell, provided that piece was built with the
proper PATH's, you were fine. Would merely adding that module require me
to use a source-compiled dist with that option enabled, or can I safely
just drop in a copy of that SHLIB?
Another slight concern I have is about any major gotchas between 3.0.11
and 3.0.22 -- I've been reading the release notes and the only thing
that seems to concern me is the specification of domain groups
(requiring fully qualified names). Can anyone who has been through such
large jump (or has been continually upgrading) let me know if they think
there is likely anything large to trip over?
Thanks!
- --
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III
|$&| |__| | | |__/ | \| _| |novosirj@umdnj.edu - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFaxaFmb+gadEcsb4RAstLAKDQt1Na3bYTUB/8YIZPZbz7ADGy8gCfUnfD
6e286vsBGraazO+hqA1xvGw=Ovzt
-----END PGP SIGNATURE-----
