/root is missing?
 

I thought root home directory is /root, but it does not exist. Actually I thought I have seen it in previous installations of Fedora core 9.
Am I wrong? Or, there may be something wrong with the installation..?

$ ls /

Do you see 'root' listed?

You have to have /root! Did your Penguin leave you for the snow?

Have you looked in /etc/passwd to see what it is set to?

If you're trying to get there while not logged in as root, SELinux may be preventing the normal user (you) from seeing it.

Now no. But, I am sure it was under /.

Taking a different direction on your post:

What were you doing that caused you to notice that it was missing? Were you logged in as root and moving files in /somethingorother or in /root? If so, chances are you've moved /root somewhere else or perhaps deleted it.

I know. I am newbie but actually have used Linux a lot since early 90s but not for about 10 years. So, I thought /root should exist and it was there until last night.

I log on to the Fedora server as a user but not a root. I frequently use su command. This morning I felt strange when I used it because the prompt was not the same as before. On command line prompt used to show (I believe) current folder name, but all the suddenly it showed just bash-3.2#. Also, I found that cd ~ did not work.
Then, I tried to check the /root, but I could not find!
... I have just reinstalled Fedora core 9 4,5 days before because samba has never worked with the previous installation. Maybe, I am a little confused???

You seem to have deleted or moved the /root directory, obviously unintentionally, maybe during your re-installation. Otherwise Fedora should have the /root directory just below / and this is certainly not something that RedHat and the Fedora people are about to change.

You need to figure what has gone wrong during re-install.

Post your /etc/passwd file.

juz simply creat a new one

and leave the old Penguin out in the cold? I think you should find the old root, where did it go?

I think that was it. I logged on the system as root and could see /root directory. I usually log on to the system as a user and frequently use su to make system level changes.

Thank you for your help. I have spent a few weeks for the samba which has never worked and I was so frustrated. Now that I can go back to work on the samba issue at least... I hope I can make it work this week.

Thank you again!

Thank you very much for the everybody who posted threads here. I have gotten a right answer from Zettabill. I was missing /root because SELinux hid /root directory when a user logged on SELinux system, but I did not know SELinux could hide /root directory.

What happened was that when I used su, the prompt sign changed to basic shell prompt instead of the one with current directory name. I thought the prompt sign did not change when I switched between root and a user. Then, I started searching for the root shell script in /root and could not find the root directory.

I think I probably saw /root when I logged on the system as root and thought it was always there even when I logged on as a user. But, I still do not know why I was not aware of that the prompt sign changed. Maybe it was just my confusion, I guess. I have used earlier version of Linux since 90s but have not used Linux for about 8 years and am not very familiar with SELinux. I probably should learn more SELinux or stop using it if it's not very necessary.

Samoh

SELinux isn't a bad thing especially if you're doing the server work you're hinting to but it does require that next level of knowledge in how it works.

EDIT: When I run my home samba server, I have some subfolders within a share that I only want myself or another to have access to. Others can't access it, but they can unfortunately *see* them. SELinux is very useful for fine-tuning user-level security in such ways (like how your root user is the only user able to see root, which is actually good). I run Slackware so it's not natively installed but it's not such mission-critical information where installing SELinux is necessary for me.

IIRC:instead of just su should set up the environment where you can operate without SELinux interfering. If it doesn't then boy I'm rusty at it, but at least you know you can get to it with a normal root login. ;)

Thank you for the kind words. Glad I could help!