Bash

File System and File permission

File System and File permission

The Filesystem is a type of arrangement established with the assortment of documents or directories. It establishes management over information, i.e., how information is to be saved and reclaimed?

Linux Filesystem is a tree-like arrangement included of lots of directories. These directories are just the files containing the list of other files. Linux makes no difference between the files and directories. All the files in Linux filesystem are known as directories, and these files are categorized as follows:

Ordinary files that contain data, text, images, program instructions.

Special files that give access to hardware devices.

Directories that contain both the ordinary and special files.

Let's have a look on Linux filesystem.

List all the files and directories by using ls -l command.

Filesystem and File Permissions

There are seven columns in the given image, which are defined as follows:

The first column represents the file type and file permissions. Every file row begins with the file type and then specifies the access permissions associated with the files. These are the following types of files with their specific characters:

Regular file (-)

Directory (d)

Link (l)

Special File (c)

Socket (s)

Named pipe (p)

Block device (b)

The second column describes the number of memory blocks.

The third column denotes the owner of the data or the superuser, who has the administrating authority.

The fourth column describes the group of owners/superusers.

The Trojan horse describes the file size.

The sixth column describes the date and time at which the data was generated or modified.

The last column describes the title of the file or the repository.

File Permissions

Instead of arranging the easiest security standards, a Linux-based OS wants file authorization to ensure its data security in the filesystem, as there are file approval based problems that transpire while a user specifies improper authorization to the data and repository. These concerns could create spiteful or inadvertent modification with the filesystem that can damage the OS. So Linux secures its filesystem with two-factor permission properties as given:

1. Permissions

There are three sorts of permissions related to the files as follows:

Read (r) permission by which you'll view the content of the file.

Write (w) permission by which you'll modify the file content.

Execute (x) authorization utilizing that one can run the programming document or the script.

Note: Dash (-) is supplied just in case of authorization get cited.

2. Ownership

There are three sorts of Linux users as follows:

The owner is that the superuser who creates the file. He can access all the permissions related to a file that has reading, modifying, and running the file.

Group is understood as a group of users or multi-users. The superuser creates it. Every member during a group has an equivalent access permissions related to a file.

Other users, i.e., the third-party users are often anybody else who doesn't belong to the Superuser/Group members. They use the permissions related to any file or directory which are created or owned by the Superuser/Group members.

Let's understand this idea by the given an example.

Filesystem and File Permissions

See the primary column of the darkened row. it's ten slots.

The first slot (-) represents a file named by aa.sh

The next three slots (rw-) specify the permissions employed by the assigned owner. These permissions include read and write. Here, execute permission is denied.

The next three slots (rw-) specify the permissions employed by the group members who own the directory. These permissions include read and write, but don't include execute permission.

The next three slots (r--) specify the permissions employed by the third=party users. These permissions include read permission only. Here, read and write both the permissions are denied.

Changing Permissions

You can alter the file permissions for every class (user/group/others) by using the chmod command. the essential form to get rid of or add any permission for any class is:

chmod [class][operator][permission] file_name  

chmod [ugoa][][rwx] file_name 

class is represented by the indications - u, g, o, and a such u for the user, g for the group, o for the opposite, and for all the classes.

operator ( + or - ) is employed to feature or remove the permission.

permission is represented by the indications r, w, x to permit access for reading, modifying, or running the script respectively.

Let us modify the authorizations of the aa.sh file given below:

Filesystem and File Permissions

1. Attach the rejected authorizations for all classes.

2. Remove the write and run authorization for different class.

And so, we can modify any authorization for any class if we require to