I did a frugal install of DSL 4.0 yesterday, and installed the samba.dsl mydsl extension.
Some comments:
1)from an end user perspective (newbie here), I'd say that the new smb.conf file is less user friendly than the one included with DSL 3.4. Is there a reason for the change?
2)testparm doesn't work anymore; was it removed from DSL?
And now I also have another problems:
a)my /dev/hda3 automatically mounts somewhere, while previously with 3.4 I had to mount it manually in /opt/bootlocal.sh What's the reason for that change?
b)the samba share is readable from my other network PC, but not writeable; while it worked with DSL 3.4 previously. I'm fairly sure it's not a smb.conf problem, but a rights problem. Could it come from problem a) above? Who should be the owner of the shared folder?
Thanks for your help!
Quote
2)testparm doesn't work anymore; was it removed from DSL?
- it will be in /usr/bin if it is still there (I'm writing this from a dsl-3.4.x machine).
Quote
b)the samba share is readable from my other network PC, but not writeable
- smb.conf should have something like this:
Code Sample
[share] path = /mnt/sdb4/dslshare read only = no browseable = yes guest ok = yes
- my share is dsl.staff but I'm not sure a windows machine would know this?Thanks Juanito. I'm not in front of my DSL box right now, but I'm quite sure I don't have the guest ok = yes line, so I will add that.
I was trying to write from another linux PC, but in the end it will be also be used from a windows PC.OK: testparm is still there; wonder why I didn't see it before; thanks!
But the write access problem still persisted. I also had owner dsl.staff for my share.
Seeing that my other share /tmp still worked in write mode, I looked at the owner of that one, and guess what, it was root.root. So I changed my other share to root.root and now I can write on it!
I have a feeling there's a problem related to the fact that the /mnt/hda3 is automatically mounted at startup by the new version of DSL, while I had to manually do it from /opt/bootlocal.sh