How to modify the Linux fstab file to cancel the read-only attribute
Experimented with disabling the execution of set bit programs and binary programs through mount options
[root@localhost~]#vi /etc/fstab/
#join in
/dev/sdc1 /var ext3 defaults,noexec 1 2
[root@localhost~]#mount -o remount /var
After the system restarted, it was found that /dev/sdc1 could not be entered and could only enter the character interface.
I want to delete that line, but when saving the file, it prompts read-only attribute
Read-only file system
Experimented
(1)chmod w /etc/fstab
(2):w!
The file is still read-only and cannot be modified
method
#mount -n -o remount,rw /
Then you can save it
Restart the computer system and it will return to normal. The above problem occurs because of my own partition format setting.
Supplementary knowledge
/etc/fstab contains information about how your disk partitions and storage devices are mounted, and where they are mounted
The first column contains the device name,
The second column is its mount point,
The third column is its file system format,
The fourth is the mounting parameters,
The fifth column [a number] is the dump option
The sixth column [another number] is the file system check option.
The last two items in this file
1. default This writable value (rw ro suid [a security mechanism] user [nouser] whether ordinary users can mount exec and whether they can execute binary files sync [async] sync is written to the hard disk in real time, async is not For real-time writing, you can write to the memory first, which will be used in FTP)
2. 0 0 The first one is 0 indicating whether to back up, 1 is backup, and the latter one is indicating whether to check for partition errors.
The above is the detailed content of How to modify the Linux fstab file to cancel the read-only attribute. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

Starting an Nginx server requires different steps according to different operating systems: Linux/Unix system: Install the Nginx package (for example, using apt-get or yum). Use systemctl to start an Nginx service (for example, sudo systemctl start nginx). Windows system: Download and install Windows binary files. Start Nginx using the nginx.exe executable (for example, nginx.exe -c conf\nginx.conf). No matter which operating system you use, you can access the server IP

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

How to fix Nginx 403 Forbidden error? Check file or directory permissions; 2. Check .htaccess file; 3. Check Nginx configuration file; 4. Restart Nginx. Other possible causes include firewall rules, SELinux settings, or application issues.

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

The error log is located in /var/log/nginx (Linux) or /usr/local/var/log/nginx (macOS). Use the command line to clean up the steps: 1. Back up the original log; 2. Create an empty file as a new log; 3. Restart the Nginx service. Automatic cleaning can also be used with third-party tools such as logrotate or configured.
