similar to: Samba 3.0.12 Available for Download

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Manny] "They think I'm a cop! I'm not a cop! I've just had too much coffee!" ==================== Release Announcement ==================== This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. Please read the following important changes in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a preview release of the Samba 3.0.12 code base and is provided for testing only. This release is *not* intended for production servers. However, there have been several bug fixes and new features added since 3.0.11 that we feel are important to make available to the Samba community for wider testing. Common bugs fixed in 3.0.12pre1

I''m trying to do what I think would be relatively simple but can''t seem to make it work. Essentially I want to create several domU''s running CentOS each with it''s own LVM partition for increased performance over image files. Initially I did a test with image files and everything went fine, I booted the supplied initrd and vmlinuz images installed CentOS from

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a preview release of the Samba 3.0.12 code base and is provided for testing only. This release is *not* intended for production servers. However, there have been several bug fixes and new features added since 3.0.11 that we feel are important to make available to the Samba community for wider testing. Common bugs fixed in 3.0.12pre1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Quoting from the "Little Book of Calm": This is a release candidate of the Samba 3.0.12 code base and is provided for testing only. While close to the final stable release, this snapshot is *not* intended for production servers. If all goes well, this this version (or something very similar) will become the final 3.0.12 stable release.

Linux Samba 3.0.12 + acl (ext3) =============================== When upgrading from 3.0.11 to 3.0.12 ACL's do not seem get used anymore. We are using the inherit acls options for both maps and files. After the upgrade users are unable to create new files in directories where they used to have privileges for. The error returned is: "The file already exists. Do you want to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcement ==================== Samba 3.0.14a is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. Please read the following important changes in this release. Common bugs fixed in 3.0.14a include: ~ o Compatibility issues between Winbind and Windows 2003

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== I am a leaf on the wind. Watch me soar. -- Wash (Serenity 2005) =============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is the version

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== You can't change the world, but you can make a dent. -- Smoochy the Rhino =============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is the

Hi all I am running a Suse-9.1 distribution on a server and have been runnig samba from 3.0.4 up to 3.0.11 succesfully on the beast. I have got openldap 2.2.11 running and the server works as a PDC using the LDAP repository I always downloaded the sources compiled the stuff and off it went without any problems. Yesterday I compiled the 3.0.12 on the machine and when I fired it up I realized

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== He's not the first psycho to hire us nor the last. You think that's a commentary on us? -- Capt. Malcolm Reynolds (Firefly 2002) =============================================================== Release Announcements =====================

We are running with a little over 100GB of office data, and about 200GB misc other data shared to approximately 50 users using samba across two servers acting as PDC and BDC to Windows 2000 & XP Pro clients. Also using roaming profiles and ldap backend inclusive of nss_ldap and pam_ldap for the unix side - works well except for the more recent and horribly crippling MS Office bug. Tried

hi, i'm trying to migrate my samba 2.2.8a pdc to 3.0.12 pdc. I'm using ldap and i have already migrated all the data. Also i have executed convertSambaAccount for the new schema. My problem is that I cannot set the old SID (samba 2.2.8) to the new samba 3.0.12 for that the clients can authentificate to pdc server. samba2.2.8> smbpasswd -S LDAP Successfully set domain SID to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== If two heads are better than one, why do my shoulders hurt so much? -- Michael Samuel Finn ============================================================== Release Announcements ===================== The Samba Team

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== It may just be a storm in a teacup, but to the ant in the teacup it certainly feels like a typhoon. -- anonymous ===============================================================

Server: - AIX5.3 with JFS2 file systems - IBM pSeries 520 (1.9GHz p5+ CPU) - Samba 3.0.22 (and the same problem exists in 3.0.21a) - I tested Samba compiled from sources with GCC 4.0.2 and 3.4.3 same result for both. I also downloaded the AIX binary from http://us4.samba.org/samba/ftp/Binary_Packages/AIX/ and it has the same problem as well. Client: MS Windows XP SP2 We have an application that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== Blanking someone is an incredibly powerful thing to do in civilized society. -- Bernard Black ============================================================== Release Announcement ==================== This is the latest

Hello there, I recently replaced a server running Samba 2.x with a brand new one running Samba 3.0.12. I had a couple DOS machines running the Microsoft Client which worked fine on the old server. On the new one, they can log in fine, and do a "dir" on the remote drive, but when I try to copy a file to or from the server, the DOS machine hangs, and on the server I get a

Hi, I just recently purchased a new server and took this opportunity to upgrade to the latest version of samba (3.0.12). Unfortunatly, I have some weird occurances. I have a user called "joe" who is my admin user. In /etc/passwd I have this: joe:x:500:500:Joe:/home/joe:/bin/bash In /etc/group I have this: admin:x:500:joe id returns correctly: uid=500(joe) gid=500(admin)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Quoting from the "Little Book of Calm": This is a release candidate of the Samba 3.0.12 code base and is provided for testing only. While close to the final stable release, this snapshot is *not* intended for production servers. If all goes well, this this version (or something very similar) will become the final 3.0.12 stable release.