-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Heads up everyone.
The 3.0alpha21 snapshot has been placed on samba.org for download
and will be available on mirrors shortly. RedHat RPMS will be
uploaded within the hour I think.
Just a remember that this release is provided for testing
purposes only. And testing with no feedback does us no
good. :-)
The full WHATSNEW file is available at
http://www.samba.org/samba/ftp/alpha/WHATSNEW.txt
The source release tarballs and GPG signatures are
available in that same directory.
Here's the relevant portion of the release notes....
WHATS NEW IN Samba 3.0 alpha21
26th November 2002
==============================
This is a pre-release of Samba 3.0. This is NOT a stable release.
Use at your own risk.
The purpose of this alpha release is to get wider testing of the major
new pieces of code in the current Samba 3.0 development tree. We have
officially ceased development on the 2.2.x release of Samba and are
concentrating on Samba 3.0. To reduce the time before the final Samba 3.0
release we need as many people as possible to start testing these alpha
releases, and hopefully giving us some high quality feedback on what needs
fixing.
Note that Samba 3.0 is not feature complete yet. There is a more
coding we have planned, but unless we get what we have done already more
widely tested we will have a hard time doing a stable release in a
reasonable time frame.
Reporting bugs & Development Discussion
- ---------------------------------------
Please discuss this release on the samba-technical mailing list or by
joining the #samba-technical IRC channel on irc.openprojects.net
Note that general use or administration question should still be directed
to the samba@samba.org mailing list.
If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored.
Removed Parameters
- ------------------
* postscript
* printer driver
* printer driver location
* printer driver file
Added Parameters
- ---------------
* ldap trust ids
* acl compatibility
* mangle prefix
Modified Parameters
- -------------------
* restrict anonymous
* password server
Changes in alpha21:
See cvs log for SAMBA_3_0 for complete details. There are many
smaller numerous changes that would clutter the release notes.
1) Numerous documentation updates including new Samba FAQ
2) Fixed logic error in checking wins server lists
3) Added more Solaris sendfile checks
4) Added --with-ldapsam for compatibility with 2.2.x Samba/LDAP setups
5) Add new client side support the Win2k LSARPC UUID in rpcbinds
Detect a native mode Win2k DC when in "security = domain"
6) Include Domain Local Groups in listing when a member of a native
mode Win2k domain
7) Fix ACL inheritance problem
8) Register <0x1c> name on unicast subnet
9) Removed stat() call in lp_add_home()
10) Change default of max_xmit to match W2K. Ensure NT negprot uses it
11) Merge the new ACL mapping code from Andreas Gruenbacher
12) Removed make_printerdef tool from build
13) Fix fd leak on printer queue tdb's
14) Better error/status logging in both the pam_winbind client and
winbindd_pam
15) Fix fd leak with kernel change notify
16) Fix slowdown because of enumerating all print queues on every smbd
startup
17) Fix --set-auth-user command to delete entries from the secrets file
when an empty username/password is passed on the command line
18) Added --get-auth-user to wbinfo for displaying account information
used to enumerate users and groups
19) Numerous updates for 'net rpc vampire' to migrate from an NT 4.0
Domain
20) Merge of scalable printing code from APP_HEAD
21) Numerous changes the passdb layer
22) More work on printer publishing in Active Directory
23) Enable "make modules" to build VFS libraries
24) Enable print notify messages on printer attributes from smbcontrol
25) Enable auto lookup of domain controllers when adding '*' to
"password server" parameter. Allows to have preferred list
of DC's, but not authoritative (e.g. password server = DC1 DC2 *)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/
iD8DBQE95Dw/IR7qMdg1EfYRAm4PAJ0fbPPlk8RW+9a5mUAjEUCWpE9lZACgxOSU
O6E0NNoqOxSRxNMjEbCgQyY=qIyz
-----END PGP SIGNATURE-----
I remember hearing that samba 3 alpha can be installed without affecting
the 2.x installation... is this true for the (S)RPM's? Is a 2.2.7 conf
likely to be workable for 3.0 alpha21 (winbind, using NT PDC for auth),
or is it a whole new ballgame requiring LDAP or something else?
Thanks,
Daniel
-----Original Message-----
From: Gerald (Jerry) Carter [mailto:jerry@samba.org]
Sent: Tuesday, November 26, 2002 10:30 PM
To: samba@samba.org
Subject: [Samba] Samba 3.0 alpha21 released
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Heads up everyone.
The 3.0alpha21 snapshot has been placed on samba.org for download
and will be available on mirrors shortly. RedHat RPMS will be
uploaded within the hour I think.
Just a remember that this release is provided for testing
purposes only. And testing with no feedback does us no
good. :-)
The full WHATSNEW file is available at
http://www.samba.org/samba/ftp/alpha/WHATSNEW.txt
The source release tarballs and GPG signatures are
available in that same directory.
Here's the relevant portion of the release notes....
WHATS NEW IN Samba 3.0 alpha21
26th November 2002
==============================
This is a pre-release of Samba 3.0. This is NOT a stable release.
Use at your own risk.
The purpose of this alpha release is to get wider testing of the major
new pieces of code in the current Samba 3.0 development tree. We have
officially ceased development on the 2.2.x release of Samba and are
concentrating on Samba 3.0. To reduce the time before the final Samba
3.0
release we need as many people as possible to start testing these alpha
releases, and hopefully giving us some high quality feedback on what
needs
fixing.
Note that Samba 3.0 is not feature complete yet. There is a more
coding we have planned, but unless we get what we have done already more
widely tested we will have a hard time doing a stable release in a
reasonable time frame.
Reporting bugs & Development Discussion
- ---------------------------------------
Please discuss this release on the samba-technical mailing list or by
joining the #samba-technical IRC channel on irc.openprojects.net
Note that general use or administration question should still be
directed
to the samba@samba.org mailing list.
If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored.
Removed Parameters
- ------------------
* postscript
* printer driver
* printer driver location
* printer driver file
Added Parameters
- ---------------
* ldap trust ids
* acl compatibility
* mangle prefix
Modified Parameters
- -------------------
* restrict anonymous
* password server
Changes in alpha21:
See cvs log for SAMBA_3_0 for complete details. There are many
smaller numerous changes that would clutter the release notes.
1) Numerous documentation updates including new Samba FAQ
2) Fixed logic error in checking wins server lists
3) Added more Solaris sendfile checks
4) Added --with-ldapsam for compatibility with 2.2.x Samba/LDAP setups
5) Add new client side support the Win2k LSARPC UUID in rpcbinds
Detect a native mode Win2k DC when in "security = domain"
6) Include Domain Local Groups in listing when a member of a native
mode Win2k domain
7) Fix ACL inheritance problem
8) Register <0x1c> name on unicast subnet
9) Removed stat() call in lp_add_home()
10) Change default of max_xmit to match W2K. Ensure NT negprot uses it
11) Merge the new ACL mapping code from Andreas Gruenbacher
12) Removed make_printerdef tool from build
13) Fix fd leak on printer queue tdb's
14) Better error/status logging in both the pam_winbind client and
winbindd_pam
15) Fix fd leak with kernel change notify
16) Fix slowdown because of enumerating all print queues on every smbd
startup
17) Fix --set-auth-user command to delete entries from the secrets file
when an empty username/password is passed on the command line
18) Added --get-auth-user to wbinfo for displaying account information
used to enumerate users and groups
19) Numerous updates for 'net rpc vampire' to migrate from an NT 4.0
Domain
20) Merge of scalable printing code from APP_HEAD
21) Numerous changes the passdb layer
22) More work on printer publishing in Active Directory
23) Enable "make modules" to build VFS libraries
24) Enable print notify messages on printer attributes from smbcontrol
25) Enable auto lookup of domain controllers when adding '*' to
"password server" parameter. Allows to have preferred list
of DC's, but not authoritative (e.g. password server = DC1 DC2 *)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/
iD8DBQE95Dw/IR7qMdg1EfYRAm4PAJ0fbPPlk8RW+9a5mUAjEUCWpE9lZACgxOSU
O6E0NNoqOxSRxNMjEbCgQyY=qIyz
-----END PGP SIGNATURE-----
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
-----------------------------------------------------------------------
This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.
And what about side-by-side installations? Having both versions installed... so I can run 3.x for a bit, stop it, and turn 2.x smbd back on if needed? I heard this was the case in tarball installation, but is this supported by the RPM? ~ Daniel On Wed, 27 Nov 2002 daniel.jarboe@custserv.com wrote:> I remember hearing that samba 3 alpha can be installed withoutaffecting> the 2.x installation... is this true for the (S)RPM's? Is a 2.2.7conf> likely to be workable for 3.0 alpha21 (winbind, using NT PDC forauth),> or is it a whole new ballgame requiring LDAP or something else?The official position is that a 2.2.x config file should work out of the box with Samba 3.0. The main exception to this is thatr "encrypt password + yes" is now the default. If you require plain text authentication, you will need to set this accordingly in the config file. Feedback on this is much appreciated. ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
K, thanks for the clarification Jerry! ~ Daniel On Wed, 27 Nov 2002 daniel.jarboe@custserv.com wrote:> And what about side-by-side installations? Having both versions > installed... so I can run 3.x for a bit, stop it, and turn 2.x smbdback> on if needed? I heard this was the case in tarball installation, butis> this supported by the RPM?The 3.0alphaX RPMs will overwrite a 2.2.x RPM. Downgrading is not supported as some TDB's will be upgraded to a newer format that would be unrecognized by 2.2.x. ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.