zxm927 at 163.com
Thu Sep 11 07:26:59 PDT 2008
On Thursday 11 September 2008 10:05:43 pm Mark Ryden wrote:
> In fact, after looking more closely, I see that before that message
> appears: Error: unmouting old /sys
> ERROR unmounting old /sys: Invalid argument.
> forcing unmount of /sys
My experience is you'd better to find a sysfs patch, since the sysfs
filesystem is required by ramdisk and some system utilities, e.g., system
network configuration scripts.
Patch for mm-tree can be found here:
This is what I used:
I merged these 11 patches on Linux-188.8.131.52 though I don't understand these
patches, luckily enough it worked for me.
> Any ideas?
> On Thu, Sep 11, 2008 at 5:01 PM, Mark Ryden <markryde at gmail.com> wrote:
> > Hello,
> > I am trying to follow the
> > Linux Containers - Network Namespace configuration instructions from
> > http://lxc.sourceforge.net/network/configuration.php
> > I had built a kernel with CONFIG_SYS=n and CONFIG_NET_NS=y
> > and CONFIG_VETH=y , etc, according to the instructions.
> > Now, the CONFIG_SYSFS help text says:
> > sysfs is currently used by the block subsystem to mount the root
> > partition. If sysfs is disabled you must specify the boot device on
> > the kernel boot command line via its major and minor numbers. For
> > example, "root=03:01" for /dev/hda1.
> > So I added root=08,02 to my kernel boot parameter line and booted.
> > it starts booting, but then gets:
> > switchroot: mount failed: No such file or directory.
> > Booting has failed.
> > 8 is the majoror number and 2 is the minor number of /dev/sda2, where I
> > have my root partition.
> > Googling for this found the following, which not helped much:
> > http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-11/msg05032.html
> > Any ideas?
> > Regards,
> > Mark
> Containers mailing list
> Containers at lists.linux-foundation.org
More information about the Containers