Most modern file systems have methods of administering permissions or access rights to specific users and groups of users. These systems control the ability of the users affected to view or make changes to the contents of the file system.
Welcome to CWAnswers
CWAnswers is your guide to the sprawling world wide web. The directory aims to provide a useful guide made by users. You can share your knowledge as well - simply sign up and edit your first entry. For questions just contact the team at support - at - cwanswers.com.
Weblinks for Permissions
Top 10 for Permissions
Things about Permissions you find nowhere else.
Select content modules
Ramesh Srinivasan's Blog: Reset the entire registry permissions to defaults
Reset the Registry and the File Permissions in Windows XP - The Winhelponline Blog ... Some registry permissions granted to a specific user (me) were reset from full ...winonline.blogspot.com/2005/11/reset-entire-registry-permiss...Permissions - LifeType Wiki
Blog owners do not need any extra permission to access all the areas of a blog. ... Blog permissions control all aspects relative to a specific blog, and include ...wiki.lifetype.net/index.php/PermissionsTim Trent | Marketing by Permission | Blog | Compliance and Privacy ...
... Wong's DP Thinker Blog, featured by Compliance and ... Phillip Hallam-Baker's Blog - The dotFuture Manifesto: Internet Crime, Web ... by Permission" Blog ...complianceandprivacy.com/blogs/Marketing-by-Permission-index...Don't rely on PHP file upload permissions | Tiger Technologies Blog
Behind the scenes at Tiger Technologies. Announcements, technical details, useful tips, thoughts on the Web hosting industry, and more.blog.tigertech.net/posts/php-upload-permissions/Changing File Permissions " WordPress Codex
6.1.4 php5.cgi permissions. 7 See Also ... Permissions will vary. ... have complete control over your blog, including having your database information ...codex.wordpress.org/Changing_File_PermissionsMost modern file systems have methods of administering permissions or access rights to specific users and groups of users. These systems control the ability of the users affected to view or make changes to the contents of the file system.
Differences between operating systems
Unix-like and otherwise POSIX-compliant systems, including Linux-based systems and all Mac OS X versions, have a simple system for managing individual file permissions, which in this article are called "traditional Unix permissions". Most of these systems also support some kind of access control lists, either proprietary (old HP-UX ACLs, for example), or POSIX.1e ACLs, based on early POSIX draft that was abandoned, or NFSv4 ACLs, which are the part of NFSv4 standard.
DOS variants (including the Microsoft products MS-DOS, Windows 95, Windows 98, and Windows Me) do not have permissions. There is a "read-only" attribute that can be set or unset on a file by any user or program.
VMS and OpenVMS as well as Microsoft Windows NT and its derivatives (including Windows 2000 and Windows XP), use access control lists (ACLs) to administer a more complex and varied set of permissions.
Mac OS X versions 10.3 ("Panther") and prior use POSIX-compliant permissions.
Mac OS X, beginning with version 10.4 ("Tiger"), also support the use of NFSv4 ACLs. They still support "traditional Unix permissions" as used in previous versions of Mac OS X, and the Apple Mac OS X Server version 10.4+ File Services Administration Manual recommends using only traditional Unix permissions if possible. It also still supports the Mac OS Classic's "Protected" attribute.
Solaris ACL support depends on the filesystem being used - older UFS filesystem supports POSIX.1e ACLs, while ZFS supports only NFSv4 ACLs.
Linux supports POSIX.1e ACLs. There is experimental support for NFSv4 ACLs for ext3 filesystem.
FreeBSD supports POSIX.1e ACLs. There is experimental support for NFSv4 ACLs for UFS and ZFS filesystems.
Traditional Unix permissions
Permissions on Unix-like systems are managed in three distinct classes. These classes are known as user, group, and others. In effect, Unix permissions are a simplified form of access control lists (ACLs).
When a new file is created on a Unix-like system, its permissions are determined from the umask of the process that created it.
Classes
On Unix file systems, every file and directory is owned by a specific user. The owner of an object comprises its user class. Permissions assigned to the user class only apply to that specific user.
A file or directory is also assigned a group, which comprises its group class. Permissions assigned to the group class only apply to members of that group (other than the owner). It is not necessary that the owner be a member of the file's group. While a particular file can be assigned to only one group, a particular user can be a member of any number of groups, and a group can include any number of users. The "groups" command lists all the groups that include a user; the "members" command lists all the users that are the member of a particular group (Stutz 2004). The system administrator uses "addgroup" to add a user to a group.

























