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.
Related
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.
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.
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
Actually I am just trying to build up a cluster(beowulf) in which there is a modification required in /sbin/lilo for reflecting the access to master node by slave node after it goes up . I changed the /etc/lilo.conf.anaconda file for timeout=1200 , but unable to find the /sbin/lilo file to get result of added linux.Please help me that where do i verify that the modificaion is been implemented??....I am working on RHEL 4.
lilo was the boot loader of Linux a long time ago.
As far as I can tell, all distributions have moved to using grub as default instead, as it is much more robust. With lilo, the risk of ending up with a non-booting system were much higher.
It seems you are following an extremely outdated manual?
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.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
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.
This question does not appear to be about programming within the scope defined in the help center.
Improve this question
I recently made the following (i believe important) changes to my system
Actually I was following this tutorial to use something called Linux Containers.
So can you tell me if any of the following stuff is capable enough to crash my system ?
1. Making changes to /etc/fstab or
2. mount /cgroup which will try to mount cgroups automatically or
3 making changes to etc/network/interfaces or
4 making changes to /etc/resolv.conf
A typo in fstab can definitely make a system un-bootable. However, you should be able to boot from CD, mount the HD, and fix it.