LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (http://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   A share that users can see, read and write to....without password (http://www.linuxquestions.org/questions/linux-newbie-8/a-share-that-users-can-see-read-and-write-to-without-password-134511/)

fatboyal 01-13-2004 06:39 PM

A share that users can see, read and write to....without password
 
Is there a simple way to do this? I am new to SuSE 9, new to Linux, not new at all to Win.
I can see the share now from my win machines and I can read from the directories without problems. However, I need to be able for my users to write (ONLY - NO DELETE) to this share, as well. And I'd like it to be without logging in or passwords.
I have read the manuals (does reading the first three pages count as reading the manuals?) and I bought a Linux Admin book, but haven't found the answer.
Is it as simple as editing the section in the smb file for that share to include writeable=yes?
Your help is much appreciated.
Al

g-rod 01-13-2004 06:47 PM

Yes you can do this.
Edit the samba.conf file
int the global section
security=share
create mask=222

under the share
guest ok=yes

fatboyal 01-13-2004 09:24 PM

Ahhhhhh. Now my users can get in and add files - but they can still delete! Is there a config line like DELETE=NO or something simple that will allow them to still read/add files, but not delete them?
This is a music server that the whole house uses and I would hate for 20gb of music to be shredded cause someone put their purse on the keyboard!
Thanks - again - in advance!

objorkum 01-14-2004 04:29 AM

You can set up crontab to execute every 5 minute these commands:

chown root:root /dir/*
chmod 705 /dir/*

g-rod 01-14-2004 06:23 AM

Try changing
create mask=0111
security mask=0111
under the share.
That should do it.

fatboyal 01-14-2004 10:46 AM

That is IT! Thank you very much. I have been reading a bit (ok, a lot now) about masking. Is there a table or a known formula for determining what the mask should be for a particular config?
Thanks everyone for your help!

g-rod 01-14-2004 12:35 PM

filepermision are assigned octet values

User
Group
Other

The octets are made up of
READ=1
WRITE =2
EXECUTE=4

So a file permision of
742
means
USER has 7=READ+WRITE+EXECUTE
GROUP has 4=EXECUTE
OTHER has 2=WRITE

Hope this gets you started.

fatboyal 01-14-2004 02:48 PM

So does WRITE also convey DELETE? Cause now that I have done this, everything works just the way I asked. Of course (and god do I feel like a user right now) I really wanted them to be able to modify files in the share too. (That way, if tags are messed up, they can fix em rather than tell me)

SO.....what I am asking is, can they write to it, read from it, modify, but not delete? (Yes, I get worse)

Thanks!

g-rod 01-14-2004 04:21 PM

I was afraid you were going to ask that. There is no distinction between "delete" and "update" at the filesystem level. Once the file is closed the user can no long write to it. If a user could write to a file he/she could truncate the file, without deleting it by copying a zero byte file on top of it.

fatboyal 01-14-2004 04:59 PM

Good point - but I am not too worried about that. I just want to be able to edit tags. You know, really, this isn't that big a problem and if I was a little less anal about naming conventions, probably wouldn't care at all!
Thanks a lot for your help and putting up with a newbie. (The humbling part of this all is I've been a sysadm/programmer/manager of win systems for 10 years and I can't even figure out sharing in Linux. Must be the manager in me taking over.... or the age.)

:-)

fatboyal 01-16-2004 08:49 PM

OK g-rod, I created a second share. Wanted same perms. Edited smb.conf as suggested and copy/pasted from the first share. Strangely, though in the Samba Gui through YAST2 they show up the same, I can't write to the share. When I check the perms on the directory (using Konquerer), they show up different and the primary difference is (it looks to me) like the group has no write perms.
I could send my smb.conf if you want. If not, could my copy/paste have had something to do with it?
The way I did it was to put both the create mask and the security mask under the share. Under the globals, I have a create mask of 222. That all worked just peachy for the first share, but this one's giving me a bit of the fits.
I love all this, really. I really love Linux, I loved how easy suse installed (even tho it can't see my sound card, which I could not care less about) and I've installed twice to this machine (changed hardware) and twice within VM instances on Winboxes. No issues.
The learning makes it worthwhile. Solutions, however, are even better.
Any ideas?

fatboyal 01-16-2004 08:56 PM

Boy, checking what you say BEFORE you say it has some serious advantages. I didn't provide ANY write access to anyone. Now that I did....it works.
sigh
I still love Linux tho....

Always makes me feel a bit like the conquering hero when I solve little things like that.


All times are GMT -5. The time now is 11:24 PM.