Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Hello there, I am a bit tired and just made a horrible mistake.
Instead of doing:
Code:
x:/etc/openvpn# mv * ..
I did:
Code:
x:/etc/# mv * ..
So right now all the contents of "/etc/" is residing in "/". Can someone please help me sort this out? Perhaps someone running Debian 4 could list the contents of their system root? That way I would be able to guessestimate which files and folders should go in /etc/.
The contents can vary a bit from system to system, to be completely sure I think that the best option would be that you paste the output of "ls /" into pastebin.com, and then link it here so we can review it and give a more accurate response.
Things that you can find in / usually are:
Code:
bin boot dev etc home lib lib32 lib64 media mnt opt proc root sbin sys tmp usr var
Some of these might not be there, and there could be more stuff.
Hello there, I am a bit tired and just made a horrible mistake.
Instead of doing:
Code:
x:/etc/openvpn# mv * ..
I did:
Code:
x:/etc/# mv * ..
So right now all the contents of "/etc/" is residing in "/". Can someone please help me sort this out? Perhaps someone running Debian 4 could list the contents of their system root? That way I would be able to guessestimate which files and folders should go in /etc/.
Thanks in advance for helping me.
*holds breath*
Since the contents of / is much more modest than the contents of /etc your best strategy is to take a list of what should be in / and move it to a temporary location. Once safely out of the way, you can then move what's left to /etc and move back the / stuff from the temporary location to / . It may not be perfect but it should be pretty close to what you had before. Here's the contents of my / folder. It's from Squeeze but it shouldn't be that different.root.txt When in doubt (there shouldn't be many cases) save a copy of the doubtful file/folder somewhere else where you can remember it and you can always undo anything bad.
Cheers,
jdk
sensible question. the root of most GNU/Linux filesystems have only few folders with few "links", usually between 17 to 20 of them, the folders ought be memorized by the Linux user, they are:
bin dev home lost+found mnt proc sbin sys usr
boot etc lib media opt root srv tmp var
initrd.img vmlinuz
the last two are not folders but links to impt files somewhere inside one of those folders. Its time to memorize them, the rest of your files you may cp back to your /etc.
I am 99% sure that these don't belong into your /etc, in fact, initrd.img and vmlinuz are symlink, and are probably broken since there shouldn't be a "boot/" directory under /etc/.
In between the rest I see nothing that's obviously wrong, but I haven't used debian for years now. However, nothing critical should be out of place now.
I don't know what /emul is - don't have it in / or /etc on my Fedora machine. Take a look inside it - if it contains config files, it should probably be in /etc/
.pwd.lock should probably be in /. Empty hidden files get put in / from time to time as a flag to do something (usually at boot or shutdown). Don't know what that one does, or if it's actually important.
/etc/vmlinuz needs to be moved back to / - it's a symlink to /boot, but it's a relative rather than an absolute path so it's expecting to be in the same dir as boot (if you have colours switched on in your ls command, you'll see the link is broken atm).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.