Rworkman: Reverted edits by Esmapebb (talk) to last revision by Erik

2011-12-09T14:11:36Z

Reverted edits by Esmapebb (talk) to last revision by Erik

← Older revision		Revision as of 14:11, 9 December 2011
Line 1:		Line 1:
	==Normal Permissions==		==Normal Permissions==

	On *nix-like systems, traditionally ~~eery~~ file has an owner, an assigned group, and a list of permissions (although POSIX Access Control Lists are getting more popular).		On *nix-like systems, traditionally every file has an owner, an assigned group, and a list of permissions (although POSIX Access Control Lists are getting more popular).

	You can change the owner of a file with the "chown" command:		You can change the owner of a file with the "chown" command:

Merge-delete at 10:19, 9 December 2011

2011-12-09T10:19:48Z

← Older revision		Revision as of 10:19, 9 December 2011
Line 1:		Line 1:
	==Normal Permissions==		==Normal Permissions==

	On *nix-like systems, traditionally ~~every~~ file has an owner, an assigned group, and a list of permissions (although POSIX Access Control Lists are getting more popular).		On *nix-like systems, traditionally eery file has an owner, an assigned group, and a list of permissions (although POSIX Access Control Lists are getting more popular).

	You can change the owner of a file with the "chown" command:		You can change the owner of a file with the "chown" command:

Erik: Manual copy of old data.

2009-05-28T23:56:59Z

Manual copy of old data.

New page

==Normal Permissions==

On *nix-like systems, traditionally every file has an owner, an assigned group, and a list of permissions (although POSIX Access Control Lists are getting more popular).

You can change the owner of a file with the "chown" command:

: <code>fred@linux:~> chown someUser foo</code>

You can change the group of a file with the "chgrp" command:

: <code>fred@linux:~> chgrp someGroup foo</code>

Alternatively, you can do both at once:

: fred@linux:~> <code>chown someUser.someGroup foo</code>

or:

: fred@linux:~> <code>chown someUser:someGroup foo</code>

For every file, you can set the following for the User, Group, and Others: r - can read w - can write x - can execute

These are set with the "chmod" command:

: fred@linux:~> <code>chmod u=rwx,g=rx,o=r foo</code>
: fred@linux:~> <code>ls -l foo</code>
: -rwxr-xr-- 1 fred users 0 2004-10-26 11:38 foo

You don't need to set all the permissions - you can just modify them, for example, to make a file executable:

: fred@linux:~> <code>chmod +x foo</code>

You can also change the permissions just for either the User, Group, or Others:

: fred@linux:~> <code>chmod o-x foo</code>

==Octal Permissions==

You can also specify permissions with a number. To find out which numbers, add up the numbers from this table:

r w x
4 2 1

For example, rwxr-xr-- would be:

U G O
4 4 4
+2 +0 +0
+1 +1 +0
=7 =5 =4

So to give a file rwxr-xr-- permissions:

: fred@linux:~> <code>chmod 754 foo</code>

==Umasks==

umasks define which permissions can not be set (in octal). For example, the default umask on slackware is 0022:

: fred@laptop:~$ <code>umask</code>
: 0022

Ignoring the first digit, this means that the owner can do anything, but group and others are unable to write (2 == w). A more secure umask (possibly more suitable for your ~/) is 0077, meaning that group and others have no access to your files.

==More Umask==

The following is based on [[User:Sandman1|Sandman1]]'s Umask tutorial.

Well first this is a pretty boring topic to write about, So im going to get right to the point. When you set a umask you set what permission NOT to set. So when you create a file it uses the umask to set the file permissions. All of this might not make sense now but it will later. Now type:

: <code>umask</code>

Now on slackware you will get "0022", First ignore the first 0. Now we have 022. The first 0 makes sure the owner has ALL the permissions of a file. You can tell that becuase you have no permissions you want to turn off. Now the next two numbers you have a 2 for. The 2 indicates that you NEVER want to set write permissions.

Now that method above of trying to find a umask is a bit confusing. All you do is set the number what you DON'T want the user to have. Now there is an easier way of finding out a umask. You can subtract the permission from 777. Example:

777 - 750 = 027

That is the umask of the 750 permission. Now you may be asking yourself what is this usefull for. Well you can set the umask by typing "umask 027" in bash and when you create a file/directory it goes by umask 027 instead of the 0022.

Now another reason for setting a umask is becuase you want to access a filesystem such as NTFS,VFAT,Samba,etc as a regular user. You can set the umask and allow regular users to write to the filesytem. It is really easy, in the fstab all you add is "umask=027" and remount the filesystem.
See [[Windows_Partitions]] for more information (and a potentially better option than setting umask options).

[[Category:Tutorials]]

Permissions and Umasks - Revision history

Rworkman: Reverted edits by Esmapebb (talk) to last revision by Erik

Merge-delete at 10:19, 9 December 2011

Erik: Manual copy of old data.