Brian wrote:
Im not sure if this is a bug or if Im somehow doing this entirely incorrectly.

Let me describe what I am after, btw I am using snv_118.

I have one user named 'home' which is the user I created when installing OpenSolaris. I created a raidz2 fs called storage, and then a sub directory using zfs create called storage/backup. After that I created a few 'Basic Solaris Users' and gave them passwords in CIFS.
Now all that I want is for any user to be able to read,write,execute,delete 
anything in any folder.  So to accomplish this I tried the basics such as:

chmod -R 777 /storage/backup

If a user creates a folder on their Windows machine, my 'home' account cannot 
write or change any files they created.

So to test this out I created a folder (on the local opensolaris machine using 
'home') in my /storage/backup and merely tried to create a file (which I can 
do) then I tried to write to it (which claims I dont have the correct 
permissions)

So I decided maybe some permissions were getting messed up so I did:
chown -R home /storage/backup to make sure that everything was owned by home.

Still I couldn't write to the file I created.

Ive about gone insane trying to figure out how to just merely have any user 
access anything.


If I right click on a folder and go to permissions, I can change it to 'read/write' but when I click OK, then go back into the permissions screen, it didn't save the read/write part of that.
So is this a bug or do I just have no idea how to assign permissions?


Once I figure this out, I would like the user 'home' to make certain folders read only for the basic users.
Thank you for your time

From what you've said it seems you created the zfs without the sharesmb=on
This link covers most of it: http://wiki.genunix.org/wiki/index.php/Getting_Started_With_the_Solaris_CIFS_Service
HTH
--
Cheers,

Steven Acres
Toronto OpenSolaris User Group <TOROSUG>
Leader http://opensolaris.org/os/project/torosug
_______________________________________________
opensolaris-help mailing list
[email protected]

Reply via email to