Linux Container Development
 help / color / mirror / Atom feed
From: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: "xiaoming.zhang" <zxm927-9Onoh4P/yGk@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	benjamin Thery <benjamin.thery-6ktuUTfB/bM@public.gmane.org>
Subject: Re: sysfs question
Date: Thu, 11 Sep 2008 18:40:42 +0200	[thread overview]
Message-ID: <48C94A0A.8010601@fr.ibm.com> (raw)
In-Reply-To: <200809112353.47144.zxm927-9Onoh4P/yGk@public.gmane.org>

xiaoming.zhang wrote:
> On Thursday 11 September 2008 11:37:33 pm Daniel Lezcano wrote:
>> xiaoming.zhang wrote:
>>> 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
>>>> switchroot...
>>> 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:
>>> 	http://lxc.sourceforge.net/patches/2.6.26/
>>>
>>> This is what I used:
>>> http://lxc.sourceforge.net/patches/2.6.26/2.6.26-rc8-mm1-lxc1/broken-out/
>>> sysfs/
>>>
>>> I merged these 11 patches on Linux-2.6.26.1 though I don't understand
>>> these patches, luckily enough it worked for me.
>> As mentioned Benjamin, it is hard to boot a distro without sysfs. I
>> think it is a good idea to use the lxc patchset.
>>
>> You can use the latest version:
>>
>> http://lxc.sourceforge.net/patches/2.6.27/2.6.27-rc6-lxc1/
>>
> Thank you very much. And is there any patchset for Linux-2.6.26.* (not the 
> mm-tree)?

We worked most of the time sticked with the devel version of the kernel 
tree. The kernel which is the nearest of the version you are describing 
is 2.6.27-rc6-lxc1 which is not based on the -mm but on the 2.6.27 
release candidate. IMO, this is the most stable version of the LXC.

  parent reply	other threads:[~2008-09-11 16:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 14:01 sysfs question Mark Ryden
     [not found] ` <dac45060809110701i49acb8e7m7d8e3ccea7c59ab7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-11 14:05   ` Mark Ryden
     [not found]     ` <dac45060809110705r2474060bi71c657a23588975f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-11 14:26       ` xiaoming.zhang
     [not found]         ` <200809112226.59518.zxm927-9Onoh4P/yGk@public.gmane.org>
2008-09-11 15:37           ` Daniel Lezcano
     [not found]             ` <48C93B3D.3050303-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-09-11 15:53               ` xiaoming.zhang
     [not found]                 ` <200809112353.47144.zxm927-9Onoh4P/yGk@public.gmane.org>
2008-09-11 16:40                   ` Daniel Lezcano [this message]
2008-09-11 14:49   ` Benjamin Thery

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48C94A0A.8010601@fr.ibm.com \
    --to=dlezcano-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
    --cc=benjamin.thery-6ktuUTfB/bM@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=zxm927-9Onoh4P/yGk@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox