I am so frustrated with all the arcane nonsense wrapped around samba I could scream.
I asked a question recently on this forum for which I never got an answer.
It involved not being able to browse to Linux shares from Windows as named shares and affiliated LONG LONG (VERY LONG) delays encountered by a Windows source control application called Accurev when it tries to host workspaces directly on Linux.
So after a year of searching for a solution, it suddenly occurred to me that maybe I am going at this wrong. So I tried mounting a Windows share on Linux. This way I could use Windows to directly host my source, source control it from there and let Linux access the files on the Windows share.
I spent 2 or 3 hours trying half a dozen recipes for mounting a Windows share through samba until I finally got one to work. YAAY.
I was so excited I almost wet myself :-)
But then I cd'd to my build directory and typed "make clean" to remove all the object files from my gcc project and it failed because, although I can see them all, I cannot modify ANY files on the share.
I did everything Windows would allow me to do to make these files public by changing the sharing attributes.
But from Linux, when I try this:
ls -l B*.c
and get this result:
-rwxrwSrwx 1 rudolph root 15323 Oct 28 13:43 Bop.c
All the permission bits seem to indicate write access is allowed, but what in blazes does 'S' mean??????
Is this preventing me from writing these files, or is there some other ogre hiding in the woods of XP that is thwarting my attempts?
Here is my mount command:
Here is fstab:
[192.168.101.79:LEC-2010P /mnt/Winshare/bmc_v2_9277/bmc/controller]# cat /etc/fstab
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
//BPCLT28/workspaces /mnt/Winshare cifs user,uid=500,rw,noauto,suid,credentials=/etc/sambapasswords 0 0
and the credentials are in this file:
And by the way, all the password references in all these recipes refer to the Windows username and Windows Password, not the Linux password?? Yes?
Our Windows domain is an Exchange Server.