From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Mon 19 Jul 2004 - 16:29:19 BST
On Mon, Jul 19, 2004 at 04:55:54PM +0200, loic d'Anterroches wrote:
> Dear All,
> Do I am wrong or I need to put nothing in the /etc/fstab of a vserver?
> For the moment I have:
> /dev/md0 / ext3 errors=remount-ro 0 1
> proc /proc proc defaults 0 0
> And I get some troubles with the / mount point when shutting down the
> vserver. I put the /proc because at I was enable to run top from within
> the vserver at first.
> Can a vserver be happy with nothing in the fstab? Another thing, I have
> mdadm (software raid if I am not wrong), snmpd (is it only usefull for
> MRTG?) and ntpd running within the vserver. For ntpd and snmpd I am pretty
> sure I can remove them, but mdadm I am not sure.
inside a vserver (guest), there should be no direct
hardware access, and this, to some amount, includes
mounting filesystems like the rootfs ...
for sure, you do not want to run mdadm inside a
vserver, because if you provide enough device nodes
to make mdadm happy, somebody might use it to redesign
you vserver host from inside ...
so to make it short: vserver should not need
an /etc/fstab at all, but they will require an
/etc/mtab to display filesystem info and handle quota ..
> Little note for Linux newbies like me who want to rsync a normal server as
> a vserver on another machine:
> Do not ever sync the /proc mount point. It is created automatically. I you
> do synchronized it, you are ready for a nice crash party as it will be
> mounted automatically and will contain wrong data.
> I put the note here, because I am always going through the archives of the
> mailing list when I have some troubles. So maybe I am not the only one
> doing that.
> Vserver mailing list
Vserver mailing list