Linux Operation not permitted [closed] - linux

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
After I accidentally used the command chown /var/www/moodle, I couldn’t change the root directory to be /var/www/moodle, so that I can't install phpmyadmin.
I have looked some suggestions but not very useful, I guess the permission has now changed, the other problem is I don't remember in which root directory I have used the above command.
What I get right now:
chroot: cannot change root directory to /var/www/moodle: Operation not permitted
I am using linux for the first time.

Your first command, the chown /var/www/moddle, was syntactically bad. You had to run some other, if you didn't get back an error message.
First, try a
chown root:root /var/www/moodle
...although a chroot command should be able to be called. Probably there is also another problem, what gets you if you call a
chroot /var/www/moodle
?

Related

Unable to remove file on Linux [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I'm currently connected to a remote computer running on Linux and I have a random directory that arose after running one of my C programs. The directory name is of this form: 'H$'204'blahblah''u$'[]'$'234', very strange.
When I try to remove it via rm dir_name the terminal spits out Illegal variable name. The same behavior arises even when I use the -f flag. Then I attempted to remove it by clicking on the directory in the explorer (on vscode) and I get an error saying Error: ENOENT: no such file or directory.
I'm running this on csh shell if that helps.
Update: Running: rm ./H<tab> worked. Thanks to Jamie Guinan!
The magic word is ls -b. It will display non printable characters in an escaped way, so that you will be able to enter them back.

Where do we have to put a linux command? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I just coded a script in bash on Ubuntu but I don't know where I should put it...
I read I had to put it in /usr/bin in a tutorial but maybe it's better directly in /bin ?
This is the difference between both directories:
/bin
It contains commands that can be used by both the system administrator and the users, but which are necessary when other file systems are not mounted (for example, in single user mode). It can also contain commands that scripts use indirectly
/usr/bin/
This is the main directory of executable commands in the system.
Therefore, it will work on both, but you must establish what responsibility your script has.

what is the meaning of the lost+found directory on linux [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
Most likely a rather obvious question but nevertheless I am doubtful about it. For development purpose our team got an linux VM tot work on. Once in a while I met a lost+found directory. Most of the time it is not accessible (permission denied). What is the meaning of this directory. Has it been implemented by Linux or has it been manually by one of the administrators?
I do agree with #Arcturus-B and I put some effort in it to get some extra informatie. I found info at https://unix.stackexchange.com/questions/18154/what-is-the-purpose-of-the-lostfound-folder-in-linux-and-unix and http://www.linuxnix.com/2012/12/lostfound-directory-linuxunix.html I guess I was a little bit cautious and did expect to find so much detailed information about this.
Files that are being open when an unexpected shutdown occurs may be damaged. On the following power up, the fsck tool is run to try to recover them. If any file is to be recovered, it is placed in the lost+found directory of the partition the original was stored in.

More differences between 'read' permission and 'execute' permission (examples) [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I apologize in advance in the case my English is not good (it's not my native language).
The only difference I can tell is when opening a directory. I can open only if I have execute permissions to see what's inside of it.
But I guess there might be more differences. Perhaps a file that doesn't have execute permissions can't "pass" through the kernel. I really don't know.
I've been searching for examples about this differences but I couldn't find anything.
For a directory, execute permission controls the ability to access files and subdirectories contained within it.
For a file, execute permission controls whether you can execute the file as a command.

Can't copy file as root in Linux? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am using Cent-OS and I am trying to copy a file. I su to root first, then I execute:
cp test.txt /usr/java/jdk1.7.0_45/jre/lib/management
But I get an input/output error. Why can't I copy this file as root? Is there something that can lock a folder in Linux so root can't change it?
root is a concept to get around the system's permissions.
IO error is a more physical problem that could be of a much more varied nature. Common examples included faulty media, unreadable CDs, lost connection, and so on.

Resources