Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was unable to determine partition for / and /boot using 'mount | column -t' on one of the server. Shouldn't all servers should have / and /boot?


proc        on  /proc                 type  proc        (rw,noexec,nosuid,nodev)
/sys        on  /sys                  type  sysfs       (rw,noexec,nosuid,nodev)
varrun      on  /var/run              type  tmpfs       (rw,noexec,nosuid,nodev,mode=0755)
varlock     on  /var/lock             type  tmpfs       (rw,noexec,nosuid,nodev,mode=1777)
udev        on  /dev                  type  tmpfs       (rw,mode=0755)
devshm      on  /dev/shm              type  tmpfs       (rw)
devpts      on  /dev/pts              type  devpts      (rw,gid=5,mode=620)
securityfs  on  /sys/kernel/security  type  securityfs  (rw)
/home       on  /var/www              type  none        (rw,bind)

# cat /proc/mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
/dev/disk/by-uuid/91033a67-4da0-41a7-a594-ebb80cd4eb98 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/disk/by-uuid/91033a67-4da0-41a7-a594-ebb80cd4eb98 /dev/.static/dev ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /dev/shm tmpfs rw,relatime 0 0
devpts /dev/pts devpts rw,relatime 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
securityfs /sys/kernel/security securityfs rw,relatime 0 0
/dev/disk/by-uuid/91033a67-4da0-41a7-a594-ebb80cd4eb98 /var/www ext3 rw,relatime,errors=remount-ro,data=ordered 0 0

#df -h /
Filesystem            Size  Used Avail Use% Mounted on
/home                 4.7G  3.0G  1.6G  67% /var/www

Any insight is greatly appreciated, thank you.

share|improve this question
It's possible not to have a mount for "/boot", but that's not typical anymore. Not having a "/" mount, though, is just plain odd. What do you see from a "cat /proc/mounts"? – Evan Anderson Aug 18 '09 at 14:27
Like Evan says, no /boot is nothing speical - that's often just a folder on the / mount these days, but no / is down-right bizarre! – Bart B Aug 18 '09 at 14:33
What about the output of df ? – radius Aug 18 '09 at 14:43
It looks like he is in some hosted, virtualized and jailed environment. The output of df / would be useful. – chris Aug 18 '09 at 15:00
I have root access to virtual server, and it shouldn't be a jailed environment, not too sure why its build this way. "cat /proc/mounts" shows "rootfs / rootfs rw 0 0", I'm not too sure what it means. Thanks guys, you are awesome in your quick response! – Imagineer Aug 19 '09 at 0:54
up vote 7 down vote accepted

The /boot partition is just a linux specific convention that isn't strictly necessary. It's used by grub or lilo or whatever to store the kernels, but in the past it was just as common to put the kernel images into / and the boot loader configurations into /etc (typically /etc/lilo.conf).

The main issue is that the boot loader needs to know where to find the kernel. The kernel itself can be anywhere, but /boot is a convenient place to put it.

/ on the other hand, is necessary. Without that there is nowhere to mount everything else. That's an issue that's a core part of unix -- there is one unified filesystem.

In your specific case, it looks like you're using some usermode linux or something inside a jail or some similar chrooted environment.

The command you're specifically looking for to figure out what is going on with / is

df -h /

that will tell you about what's going on with the root directory (where it's mounted and so on).

share|improve this answer
this is the output for df -h / Filesystem Size Used Avail Use% Mounted on /home 4.7G 3.0G 1.6G 67% /var/www So what does this says about the root directory? – Imagineer Aug 19 '09 at 0:43
I'd say that you are in some sort of paravirtualized / usermode linux environment. I haven't played with any of them in the past couple years beside openvz (which this doesn't look like). I'd guess that whatever is the host has your environment mounted on /home. – chris Aug 19 '09 at 13:36


this is a remnant from old days when a kernel couldn't be booted from disk area beyond 1024th cylinder or so, so you needed to create a partition that would make sure you don't put a kernel where it couldn't be booted.

It is still sometimes a good practice to have it if your setup is more complicated so you don't shoot yourself in the foot that easily, i.e. root partition in software raid, odd hardware etc.

share|improve this answer
I had forgotten about the 1023th cylinder issue. I guess because I never was bitten by that -- I must have had tiny disks or disks that remapped their geometry to not have that many cylinders. Thank's for knocking some of the dust off of those old neurons... – chris Aug 18 '09 at 14:59

NO! (ok just need to fill 115 chars)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.