/home/groups/z/zs/zsnes-docs/htdocs/docs/wip/images/.svn is owned by xamenus no group permissions and not group write. It has to be emptied before it can be deleted.
Once that's done, only Jipcy can delete images/.svn and images for the same reason.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________ Insane Coding
Okay, xamenus let me into his account, we're having some issues here, somehow xamenus is no longer in the zsnes-docs group, so he can't even access some directories, Jipcy, I need you to make all the directories you own leading to the problematic path to be marked executable to everyone.
Edit:
n/m, with some fancy tricks switching users in the middle of directory paths, I managed to delete the whole problematic wip/ set of directories. Thanks xamenus.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________ Insane Coding
- Export the following folders to a folder outside your local copy of the repository:
- chm
- html
- text
- web
THIS IS VERY IMPORTANT SO THAT YOU DON'T ACCIDENTALLY UPLOAD A BUNCH OF .svn FOLDERS!!
Not sure what you mean by export. But be very careful when making the copy. Furthermore any file/directory prefixed with a '.' becomes hidden under unix, so it may be hard to see the .svn directory.
Also in regards to all this, I'm a bit disturbed that xamenus isn't in our group. It is paramount that prior to setting the permissions to group readable that zsnes-docs is the groups, otherwise we could be giving write permission to our webpage to other people who have an account on the server.
In addition to all this, chmod 775 and 644 is very important too as if they're not set that way, people will have issues viewing the webpage. Meaning directories need o+rx and files need o+r.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________ Insane Coding
TortoiseSVN has an "export" function which basically copies your working copy to another folder, without all the .svn folders.
Also in regards to all this, I'm a bit disturbed that xamenus isn't in our group. It is paramount that prior to setting the permissions to group readable that zsnes-docs is the groups, otherwise we could be giving write permission to our webpage to other people who have an account on the server.
Any thoughts on how to resolve these issues? I don't have a clue. How does one check to see what group they're in?
EDIT: I changed some permissions for the various zsnes-docs members. I gave xamenus and RichardC permission to access the shell server (according to the Members page). Maybe xamenus will be in our group now.
In addition to all this, chmod 775 and 644 is very important too as if they're not set that way, people will have issues viewing the webpage. Meaning directories need o+rx and files need o+r.
Ok, well do the directions make that clear enough?
Last edited by Jipcy on Wed Dec 27, 2006 9:43 am, edited 1 time in total.
Also in regards to all this, I'm a bit disturbed that xamenus isn't in our group. It is paramount that prior to setting the permissions to group readable that zsnes-docs is the groups, otherwise we could be giving write permission to our webpage to other people who have an account on the server.
Any thoughts on how to resolve these issues? I don't have a clue. How does one check to see what group they're in?
You can see what groups a person is a member of by doing the following in the SSH terminal:
groups username
Example:
/home/nach> groups nach grinvader jdratlif zones
nach : nach dialout cdrom floppy audio video plugdev nsrt nsrtother
grinvader : grinvader nsrt nsrtother
jdratlif : jdratlif nsrtother
zones : zones nsrt nsrtother
/home/nach>
For some reason though, it's taking forever to run on SF's server. Hopefully we'll all be able to move over to BS soon.
Jipcy wrote:
In addition to all this, chmod 775 and 644 is very important too as if they're not set that way, people will have issues viewing the webpage. Meaning directories need o+rx and files need o+r.
Ok, well do the directions make that clear enough?
Well, they're clear for me. I just worry that they may not be clear enough to someone who lacks understanding on unix permissions, and how they relate to group projects and webpages.
The page has minor typos and I think can be written a bit better, but if you're clueless this should provide you with all the basic must know info.
Just remember unless the file is owned by the webserver's user/group (which could be apache or www or http or something along those lines), you need to think of the 'other' permissions for stuff to be accessed by the web server.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________ Insane Coding
I just wanted to give an update to what I'm doing. I haven't been around much.
A new semester is starting for me. I'll be taking 15 credit hours (5 classes), which is three credit hours (1 class) more than I usually do. In addition, I plan on holding a job (the kind that pays money).
So, my time will be rather limited.
I am more than happy to offer all the help I can in regards to the HTML and CSS of the ZSNES Docs. In addition, I can continue to do any required maintenance on the NSRT Guide. However, I will not have the time or energy to work on much changes to the content of the ZSNES Docs.
xamenus, I greatly thank you for working on the docs lately.
Please let me know if there's anything else I can do to help, within the constraints I layed out above.