In the interests of full disclosure, here's the glossy press
release (with html as well ! :-).
Jeremy.
---------------------------------------------------------------------
Samba 2.2.0 - Powering the next generation of Network Attached
--------------------------------------------------------------
Storage.
--------
17 April 2001.
The Samba Team is proud to announce a new major release of Samba,
version 2.2.0. This release includes significant feature enhancements
for Samba, and sets the standard for UNIX? and Microsoft Windows?
integration.
Enhancements include :
o Integration of server terminated leases (Windows "oplocks") with
UNIX NFS sharing (Linux 2.4 kernel and IRIX only). Complete data
and locking integrity when sharing files between UNIX and Windows.
o Ability to act as an authentication source for Windows 2000? and
Windows NT? clients, allowing savings on the purchase of Microsoft?
Client Access Licenses.
o Full support for the automatic downloading of Windows 2000 and
Windows NT printer drivers, providing the first full implementation
of the Windows NT point-and-print functionality independent of
Microsoft code.
o Unification of Windows 2000 and Windows NT Access control lists
(ACLs) with UNIX Access control lists. Allow Windows clients to
directly manipulate UNIX Access control entries as though they were
Windows ACLs.
o Single sign-on integration using the winbind server (available
separately). Allow UNIX servers to use Windows 2000 and Windows NT
Domain controllers as a user and group account server. Manage all
user and group accounts from a single source.
o Microsoft Distributed File System? (DFS) support. Samba 2.2.0 can
act as a DFS server in a Microsoft network.
o Share level security setting. Allow security on Samba shares to be
set by Microsoft client tools.
o Many other feature enhancements and bug fixes.
About Samba
-----------
Samba is an Open Source/Free Software implementation of the Microsoft
CIFS/SMB protocols for UNIX systems. In development for ten years,
Samba is considered to be the reference implementation of the CIFS/SMB
protocol for UNIX systems. Samba test tools are used by all the
CIFS/SMB vendors to test and fix their protocol implementations.
Samba is currently used in Network attached storage (NAS) and other
products from the following vendors (Note: this does not imply
endorsement by these vendors, please contact the vendor marketing
departments separately for comments).
IBM?, SGI? (Samba for IRIX), Sun Microsystems ?(Cobalt Qube), Hewlett
Packard? (CIFS/9000), VERITAS?, VA Linux Systems?, REALM Information
Technologies ?, Network Concierge?, Procom ? and many others.
In addition, Samba is shipped as a standard part of Linux? offerings
from Linux vendors such as Red Hat?, Caldera?, SuSE?, Mandrake?,
TurboLinux ? and others.
Samba is being used worldwide to solve the problem of integrating
hetrogeneous networks by corporations such as Agilent Technologies ?,
CISCO Systems ?, and many others in addition to educational
establishments and individuals
Best of all Samba is an Open Source/Free software project, available
under the GNU GPL license meaning that source code for Samba is freely
available for anyone to modify and customize.
Code from the Samba Team and individuals around the world has been
integrated and tested to create Samba. In addition the following
corporations have made significant donations of code, effort, testing
facilities and support to make this release possible :
Linuxcare (now TurboLinux), VA Linux Systems, Caldera, SGI, Hewlett
Packard, VERITAS, IBM.
This new release may be downloaded from our Web site at :
http://www.samba.org
For press enquiries about this release please contact either Jeremy
Allison (jra@samba.org), Andrew Tridgell (tridge@samba.org) or John
Terpstra (jht@samba.org).
Samba - the SOURCE for Windows Networking !
--
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------
-------------- next part --------------
HTML attachment scrubbed and removed
OK. Having read the press release on 2.20 sounds great. BUT my questions are as follows: 1) I have 2.07 installed, and it is NOT completely shaken out. (remaining problems are: can't reliably log in and get read/write access unless user is on admin users = line in smb.conf) and printers aren't done (but not a high priority right now.) 2) I still have a 2.2 based kernel (mandrake) and WONT upgrade it until samba is STABLE... (doesn;t that sound like a good plan ?(;--> ) Therefore, can someone assist me in figuring out a) if I will gain anything right now by upgrading to 2.20 and trying to get that pain in the 2.2 kernel? Or is just trying to shake out my bugs in 2.07 more realistic? b) Next: below I will include my smb.conf file, and explain my problem in detail (again...) Please make sure to also address a copy of any replies to me, so I can ABSOLUTELY make sure I read it CAREFULLY! ---------my smb file follows: # Samba config file created using SWAT # from 192.168.10.184 (192.168.10.184) # Date: 2001/04/08 15:29:41 # Global parameters [global] workgroup = @HOME server string = It's time to SAMBA dih dah dah dah! encrypt passwords = Yes update encrypted = Yes map to guest = Bad Password smb passwd file = /home/smbscripts/private/smbpasswd unix password sync = Yes log level = 3 log file = /var/log/samba/%m.log max log size = 50 debug pid = Yes debug uid = Yes nt smb support = No nt pipe support = No nt acl support = No name resolve order = lmhost, host, wins, bcast time server = Yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 logon script = samba.bat logon path = /home/smbscripts/netlogon/scripts domain logons = Yes os level = 0 preferred master = Yes domain master = Yes wins support = Yes guest account = guest valid users = +family admin users = mlb, clb, moo hosts allow = 192.168.10.0 hosts deny = 24.0.0.0 [homes] comment = Choose YOUR directory path = /home guest account = nobody browseable = No [printers] comment = All Printers path = /var/spool/samba print ok = Yes browseable = No [netlogon] comment = Home Login Directory path = /home/smbscripts/netlogon/scripts admin users = mlb, clb, moo, zeb write list = mlb guest ok = Yes max connections = 6 mangled names = No [moo] comment = Jess home directory path = /home/moo/dosroot invalid users = family valid users = moo admin users = moo write list = moo read only = No create mask = 0700 max connections = 3 [mlb] comment = Mitch's home directory path = /home/mlb/dosroot invalid users = family valid users = mlb write list = mlb read only = No create mask = 0700 max connections = 3 [tmp] path = /tmp [clb] comment = Cheryl's Space path = /home/clb/dosroot valid users = clb admin users = clb write list = clb read only = No create mask = 0700 max connections = 3 [zeb] comment = Zack's directory path = /home/zeb/dosroot valid users = zeb admin users = zeb write list = zeb read only = No create mask = 0700 max connections = 2 [mbsw] comment = MB SW for CDROM path = /var/sw username = mlb valid users = mlb read only = No create mask = 0700 max connections = 2 [mail] comment = MB/CB Mail files path = /var/mail invalid users = zeb valid users = mlb, clb, moo write list = mlb, clb, moo read only = No max connections = 3 [newtest] comment = test path = /home/mlb/dosroot invalid users = family valid users = @family write list = mlb read only = No create mask = 0700 max connections = 3 copy = mlb [software] comment = BigFileSystem-/SW path = /software/dosroot admin users = mlb, zeb, moo, clb, @family write list = family read only = No guest ok = Yes [testshare] comment = test sw dir share path = /software/testshare read only = No guest ok = Yes max connections = 5 ** if you're still reading this I have an interesting comment. My son (zeb) doesn't use his share for anything except games, and apparently WILL work without being an administrator. Writing seems to be the problem.
Dear samba team, I had great success with samba 2.2.0 I used the configure settings I used with samba 2.0.7, compiled and installed and everything worked great! My system is a Debian 2.2 version with a RedHat 2.2.16-4.lfs kernel (needed for Raid5 support) GCC version 2.95.2 Thanx, Ries van Twisk
Samba 2.2.0 - Powering the next generation of Network Attached StorageGreetings go to all Samba users and developers ... I seem to have pick up a very strange problem with Samba 2.0.7 on a RedHat 7.0 installation ... All was working fine for quite a few months seeing that I upgraded to RH 7.0 pf late ( The last three months, I think ) The last few days, I have found that users are having problems logon to the network. I have been wondering if I should upgrade to Samba 2.2, but I am a little worried that this will not help ... thinking this is an oplock problem ... pobbile that there are not enough oplocks or something like that ... Could somebody help me with this ... Thanks ... Getting errors like this in the machine log ... [2001/04/20 09:05:34, 1] smbd/service.c:make_connection(550) melanie-lewis (10.1.1.62) connect to service software as user melaniel (uid=51 3, gid=100) (pid 4718) [2001/04/20 09:05:52, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 3957 on port 1100 for dev = 301, inode = 3664695 for dev = 301, inode = 3664695, tv_sec = 3adfd51f, tv_usec = 7f11f [2001/04/20 09:05:52, 1] smbd/service.c:close_cnum(583) melanie-lewis (10.1.1.62) closed connection to service netlogon And messages like this in the log.nmb ... [2001/04/20 08:19:06, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.1.1.251: code = 0x7 [2001/04/20 08:19:50, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.1.1.66: code = 0x0 [2001/04/20 08:19:57, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.1.1.66: code = 0x0 [2001/04/20 08:20:16, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.1.1.66: code = 0x7 [2001/04/20 08:21:31, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.1.1.252: code = 0x7 [2001/04/20 08:24:07, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.1.1.66: code = 0x0 [2001/04/20 08:24:49, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.1.1.96: code = 0x0 -------------- next part -------------- HTML attachment scrubbed and removed
Samba 2.2.0 - Powering the next generation of Network Attached StorageSorry to bother again so soon ... The option "utmp consolidate" is still in SWAT, but I can't find any information in the SWAT help files or in the smb.conf man file ... does this option still exist ... Thanks again. Mailed C.Lee Taylor -------------- next part -------------- HTML attachment scrubbed and removed