


Three solutions to the problem that the sudoers folder permissions of the Linux system are 777 and the /etc/profile file cannot enter the system after modification
This article brings you three solutions to the problem of the sudoers folder permissions 777 in the Linux system and the inability to enter the system after the /etc/profile file is modified. It has certain reference value. Friends in need can For reference, I hope it will be helpful to you.
First of all, let’s talk about the method to restore the sudoers folder to 0440:
Method 1 (modify directly in the graphical interface):
①Enter Terminal, switch to administrator status, and enter su.
② Enter chmod 0440 /etc/sudoers. No information is printed, indicating that the modification is successful (try the sudo command to see if it still prompts 777);
If the prompt README is 777, after changing the README path to 0440, you can use the sudo command.
Method 2 (modify in the command interface):
①First press the alt ctrl F1 key on the keyboard to switch to the command interface.
② Switch to administrator status and enter su.
③Enter chmod 0440 /etc/sudoers. No information is printed, indicating that the modification is successful (try the sudo command to see if it still prompts 777);
If the prompt README is 777, after changing the README path to 0440, you can use the sudo command.
④Press alt ctrl F7 on the keyboard to switch back to the graphical interface.
Method three (without administrator identity modification):
pkexec chmod 0440 /etc/sudoers (execute command as administrator).
——————————————————————————————
Let’s talk about the /etc/profile file that cannot be modified after modification. Enter system recovery method:
①First press the alt ctrl F1 key on the keyboard to switch to the command interface.
②Switch to administrator status and enter su.
If you do not successfully switch to the administrator identity, you need to set a login password:
1. Enter the sudo passwd command and set the login password (here you can set it as the password used to log in to the system);
2. Enter su.
③Enter cd /etc to enter the etc folder;
④Use vim to edit profile file:
Enter vi profile, find the information accidentally written (or accidentally deleted) in the profile file, restore it, save and exit;
You can enter the system after restarting the system (Note: The vim file operation method is a bit troublesome, you can search on Baidu for the operation method).
The above is the detailed content of Three solutions to the problem that the sudoers folder permissions of the Linux system are 777 and the /etc/profile file cannot enter the system after modification. 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



The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

CentOS has been discontinued, alternatives include: 1. Rocky Linux (best compatibility); 2. AlmaLinux (compatible with CentOS); 3. Ubuntu Server (configuration required); 4. Red Hat Enterprise Linux (commercial version, paid license); 5. Oracle Linux (compatible with CentOS and RHEL). When migrating, considerations are: compatibility, availability, support, cost, and community support.

CentOS installation steps: Download the ISO image and burn bootable media; boot and select the installation source; select the language and keyboard layout; configure the network; partition the hard disk; set the system clock; create the root user; select the software package; start the installation; restart and boot from the hard disk after the installation is completed.

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)
