SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've just accidentally:
# rm -Rv /dev
(I meant to ./dev but hadn't spotted I missed the full stop until after I hit return).
Anyhow, I've run a simulation of doing the same action on a VM and the system appeared to rebuild the /dev directory upon restart. However I just wanted to make sure that this would fix everything or if there will be other outstanding issues?
The /dev directory entries on most Linux systems are handled by udev these days, which dynamically builds the device tree from detected hardware. In fact on many distros, the /dev directory itself is now hosted on a ram-based virtual filesystem.
What weibullguy posted above could be an exception; I'm no expert there. But if so, I imagine the default init scripts or initramfs probably handle such things usually.
mknod -m 600 /dev/console c 5 1
mknod -m 666 /dev/null c 1 3
These are required by the kernel at boot time and not dynamically created during boot.
The test I performed in a VM booted fine without those commands (I tested it before you had replied). So -on SLES at least- /dev/console and /dev/null are not required to boot.
I will however check to see if they have been recreated. So I definitely appreciate the input.
The /dev directory entries on most Linux systems are handled by udev these days, which dynamically builds the device tree from detected hardware. In fact on many distros, the /dev directory itself is now hosted on a ram-based virtual filesystem.
This is what I suspected (or at least secretly hoped).
I'll keep testing (and reading these forums in case others have any input / advice) for now, just to be safe.
Thank you
Quote:
Originally Posted by David the H.
What weibullguy posted above could be an exception; I'm no expert there. But if so, I imagine the default init scripts or initramfs probably handle such things usually.
I see. That might explain why the VM rebooted without a problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.