Alex, I assure you Samba is far from a hoax. In fact, I think it is the greatest thing since sliced bread. I am an administrator in a mixed environment of over 200 UNIX (Solaris and Linux) and Windows (95 and NT) machines. I use Samba for a variety of purposes, but mostly to mount user home directories and as print servers for the PCs. It works great!!! I first starting using it three years ago and it just keeps getting better. I can download the current release, compile it and install it in under 30 minutes and have it running. I'm not sure why you are having so much difficulty, but I would reread the documentation and the smb.conf man page if I were you. Below is a snippit of smb.conf from one of my Solaris boxes: Maybe it will be useful to you. Also, I noticed your smb.conf file was generated with swat; I have not used this tool so I don't know how reliable it is. You may want to edit smb.conf with vi or some other editor. Lastly, how are you starting smbd? Are you sure it is running and sourcing your smb.conf file properly? Hope something here helps, Leo ======================================================================================== ; Methost smb.conf file ; ; The global setting for a default install ; Copyright(C) John H Terpstra - 1997 ;======================= Global Settings ====================================[global] ; workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4 workgroup = pcnet ; comment is the equivalent of the NT Description field comment = Metrology Samba Server server string = Metrology Samba Server ; printing = BSD or SYSV or AIX, etc. printing = sysv printcap name = /etc/pcprintcap load printers = yes ; Uncomment this if you want a guest account, you must add this to /etc/passwd guest account = pcguest log file = /opt/samba/var/logs/log.%m ; Put a capping on the size of the log files (in Kb) max log size = 50 ; Options for handling file name case sensitivity and / or preservation ; Case Sensitivity breaks many WfW and Win95 apps ; case sensitive = yes short preserve case = yes preserve case = yes ; Security and file integrity related options lock directory = /opt/samba/var/locks locking = yes ; Strict locking is available for paranoid locking situations only ; enabling this severely degrades read / write performance. ; strict locking = yes ; fake oplocks = yes share modes = yes ; Security modes: USER uses Unix username/passwd, SHARE uses WfW type passwords ; SERVER uses an other SMB server (eg: Windows NT Server or Samba) ; to provide authentication services security = user ; OS Level gives Samba the power to win browser elections. Windows NT = 32 ; Any value < 32 means NT wins as Master Browser, > 32 Samba gets it ; default = 0, this ensures that Samba will NOT win the browser election. ; os level = 65 os level = 32 ;============================ Share Definitions =============================[home] comment = Home Directories path = /home/%u browseable = yes writable = yes ; Should be an NIS map (somehow) include = /packages/smb.conf.files/auto_smb.conf [service] comment = Service Database path = /export/disk1/home/servicedb public = yes browseable = yes writable = yes guest account = pcguest locking = yes force user = metguest force group = instr create mask = 0775 ; NOTE: There is NO need to specifically define each individual printer [printers] comment = All Printers path = /usr/spool/samba browseable = yes printable = yes guest ok = yes writable = no create mask = 0700 [tmp] comment = Temporary file space path = /tmp read only = no public = yes **************************************************************** Leo Crombach System / Network Administrator Tropel Corporation Phone: (716) 388-3566 60 O'Connor Road Email: lcrombach@tropel.com Fairport, New York 14450 URL: http://www.tropel.com ****************************************************************
Juan Carlos Castro y Castro <jcastro@pcshop.com.br> wrote:> > So it appears that for SOME reason, the mounted vfat partition is not > > acting the same, permission-wise, under Samba 2.0.0 as 1.9.18p10. I'll > > do some more debugging, and see what I can come up with.... > > No. Permissions are not likely the problem. You know what might be the > problem? Case conversion and name mangling. I wonder how this > VFAT-partition-mounting interprets names. There's another test for you: > > 1) Have both shares working, VFAT and Linux, and map each one under a > letter under Win95. (say, D: and E:) > > 2) Pick some directory (preferably one with both long and short file > names) and, under a DOS box (not DOS mode), do: > > DIR D:\directory > and > DIR E:\directory > > and see if anything funny shows up.Well, I did the above, and guess what? No difference in file attributes or filenames can be seen, looking at the same files on an EXT2 based share, or a VFAT based share. I've tested this with Samba 2.0.1 now, with identical results. What's really funny is that it seems SOME level of file access is going on, because Netscape Communicator appears to write messages that it fetches from my POP3 server (on my in-house Linux PC) to the folders. It just can't READ the folder information when on a shared VFAT volume. I have reported this problem to samba-bugs as well, and will probably start tomorrow morning by running a Level 5 log file of cranking up Netscape Communicator's Email module on this share using Samba 1.9.18p10, and then Samba 2.0.1. Hopefully that will show something.... if not, I'm not sure where to turn. I really thing SOMETHING has changed seriously here, and if it affects Netscape Communicator 4.5, you can be sure it will affect some other application accessing data on a Samba share as well. Maybe it's possible that Samba 2.0.x is using some filesystem functionality that wasn't used by 1.9.18p10? I.e. it is trying to do something that EXT2 supports, but VFAT doesn't, and 1.9.18p10 didn't do whatever it is. Well, until later....>-- /-------------------------------\ | Jim Morris | jim@morris.net | \-------------------------------/