On Sunday 21 August 2005 21:20, Carl Hartung wrote:
This is very good to know. *Not* that I've suddenly decided to run a second set of books or anything... just, if a device inadvertently becomes mounted to a populated directory and the error isn't noticed for a while, it doesn't automatically cause a catastrophe...
Well, any programs using the original directory will of course be terribly confused The most common error in this regard that I've seen is when people have /boot on a separate partition and keep it unmounted while the system is running. Then they run YOU and get an updated kernel, which of course is installed in the /boot directory on the root partition and not on the separate partition, so grub/lilo never sees the new kernel. But like I said, there are far worse things root can do to a system. When you're running as root, you need to be really careful.