similar to: Samba 3.0.23pre1 Available for Download

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== A revolution without dancing... is a revolution not worth having! -- V ============================================================== Release Announcements ===================== This is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== You are standing in an open field west of a white house, with a board front door. There is a small mailbox here. ============================================================== Release Announcements

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== You are standing in an open field west of a white house, with a board front door. There is a small mailbox here. ============================================================== Release Announcements

I run Samba as a PDC for a small network. I used to use smbpassword and went through the pain of changing up to tdbsam. I have just upgraded from v3.0.14a to v3.0.23a. The immediate effect was that nobody could use their domain log in any more. I was upset. My users wished me to understand their frustration. It was not my fault. I became cross. The dog got my dinner (it's an ill

Now, TOSHARG-ChangeNotes.xml translate to Japanese finished(3.4.0 base). And some typo found. -------------------------------------------------------------------------- Assume that a group named <emphasis>developers</emphasis> exists with a UNIX GID of 782. In this case this user does not exist in Samba's group mapping table. It would be perfectly normal for ----group?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "I hate 'winbind use default domain'" -- attributed to numerous Samba developers ============================================================== Release Announcements ===================== This is the latest stable release of Samba.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== It was during the jra vs. vl code reformatting wars. Somewhere around the time of the 80 column massacre. -- coffeedude ============================================================== Release Announcements ===================== This is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just attempted to build 3.0.23pre1 on HP-UX 11.11 today, preparing for a planned move to a later version of 3.0.x (we're currently down at 3.0.11). Configure ran fine, but make eventually failed here: Compiling lib/sysacls.c cc: warning 422: Unknown option "fPIE" ignored. cc: "lib/sysacls.c", line 1277: warning 611: Type

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== Chef: Bon app?tit! Donkey: Oh, Mexican food! My favorite. -- Shrek 2 =============================================================== Release Announcements =====================

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "I think we just hit thread level Orange." -- anonymous ============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== Happy Birthday, Deryck. =============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is the version that production Samba servers should be running for all

I am trying to acheve pxe booting of a image of barts boot disk (www.nu2.nu). I have managed to get LTSP booting via pxelinux, so I know my dhcp/tftp servers are ok. However when I try to boot memdisk with either a stock suselinux boot image file (taken from SuSE 9.1) or my dos disk (created by dd if=/dev/fd0 of=/imagefile) I get output like MEMDISK 2.08 command line : BOOT_IMAGE=memdisk

Hi, armed with Samba-3 -by example I proceeded to test my 2 linux lan [suselinux pro 9.1 with Samba 3.0.9-2.6-suse]. I followed instructions and made the smb.config as small as possiblw: [global] workgroup = snj server string = Samba Server guest ok = yes [orb] comment = removable 2.2 gb hd path = /orb browsable = yes read only = no However, I was stumped practically immediately as you can

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "Where does he get those wonders toys?" -- The Joker (Batman 1989) ============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is

I have the following five AD domains: RABOTEST.COM AM.RABOTEST.COM OC.RABOTEST.COM AP.RABOTEST.COM EU.RABOTEST.COM There are trusts from the top level to all four regional realms. My winbindd, in ADS mode, is joined to EU.RABOTEST.COM In 3.0.21c, winbindd wbinfo -m gives me RABOTEST RABOTESTAP RABOTESTAM RABOTESTEU RABOTESTOC But in 3.0.23pre1 and rc1, I only get RABOTEST I hope this

Hi, I am having the same problem. Did you figure out how to do this? Any help in how to remove stale WINS entries from Samba would be greatly appreciated. Cheers, -farshad

Since updating app-emulation/libvirt and/or app-emulation/qemu (both were updated at the same time) I have a problem executing "shutdown -r now" in the vm ("shutdown -h now" works fine). When I execute "shutdown -r now" in the vm the shutdown process runs perfect until "Remounting root-filesystem readonly" and than it hangs and I have to "Force Power

Hi list, I''m running xen3 on verious systems and are very happy with the way it works. My set up is based on files as partitions but I have encountered a problem I can only create 4 partitions this way since all are primary partitions. Are there any solution to this problem other than move the domU''s to real partitions ? Thanks in advance Karsten

We are in the process of updating samba on our Solaris servers from (2.0.5) to (3.0.2) I have completed one host and all seems to working ok. However I have noticed that for both versions of samba, as users map shares the smbd process which starts can be either own by root or the users id. This seems to be random. Can anyone shed light as to what controls the owner of this process. This is

Hi, Recently, upgrade samba from 3.0.14a to 3.0.23pre1. And found trusted domain user couldn't logon to Samba share. The command nsquery to query a user from trusted domain failed also. For example: parent.com Win2003 DC |---Child1.parent.com Win2003 DC |---Child2.parent.com Win2003 DC Kinit OK. Net ads join to Child1 OK. Restart the server with winbindd. Wbinfo -m can display trusted