this branch is support for the Active Directory logon protocols used
by Windows 2000 and above.
-While we welcome your interest in Samba 4, we don't want you to run your network with it quite yet. Please note the WARNINGS below, and the STATUS file,
-which aims to document what should and should not work.
+While we welcome your interest in Samba 4, we don't want you to run your
+network with it quite yet. Please note the WARNINGS below, and the
+STATUS file, which aims to document what should and should not work.
With 4 years of development under our belt since Tridge first proposed
a new Virtual File System (VFS) layer for Samba3 (a project which
-eventually lead to our Active Directory efforts), we was felt that we
+eventually lead to our Active Directory efforts), we felt that we
should create something we could 'show off' to our users. This is a
Technology Preview (TP), aimed at allowing you, our users, managers and
developers to see how we have progressed, and to invite your feedback and
WARNINGS
========
-Samba4 TP is currently a pre-alpha technology. That is more a
-reference to Samba4's lack of the features we expect you will need
-than a statement of code quality, but clearly it hasn't seen a broad
-deployment yet. If you were to upgrade Samba3 (or indeed Windows) to
-Samba4, you would find many things work, but that other key features
-you may have relied on simply are not there yet.
+Samba4 is currently at alpha stage. That is more a reference to
+Samba4's lack of the features we expect you will need than a statement
+of code quality, but clearly it hasn't seen a broad deployment yet. If
+you were to upgrade Samba3 (or indeed Windows) to Samba4, you would find
+many things work, but that other key features you may have relied on
+simply are not there yet.
For example, while Samba 3.0 is an excellent member of a Active
Directory domain, Samba4 is happier as a domain controller: (This is
none on the registry at this stage. We also do not currently have
ACLs on the SWAT web-based management tool. This means that Samba 4
Technology Preview is not secure, and should not be exposed to
-untrusted networks..
+untrusted networks.
Within the above proviso, file system access should occur as the
logged in user, much as Samba3 does.
Those familiar with Samba 3 can find a list of user-visible changes
since that release series in the NEWS file.
- - An optional password is no longer supported as the second argument to
+ - An optional password is no longer supported as the second argument to
smbclient.
- - The default location of smb.conf in non-FHS builds has changed from the
+ - The default location of smb.conf in non-FHS builds has changed from the
PREFIX/lib directory to the PREFIX/etc directory.
KNOWN ISSUES
- Standalone server and domain member roles are not currently
supported. While we have much of the infrastructure required, we
- have not collected these pieces together.
+ have not collected these pieces together.
- There is no printing support in the current release.