[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-kernel
Subject:    Re: [PATCH 2.6.24] chroot= as a new kernel parameter
From:       Måns_Rullgård <mans () mansr ! com>
Date:       2008-03-07 9:27:57
Message-ID: yw1xod9qhoiq.fsf () thrashbarg ! mansr ! com
[Download RAW message or body]

Pavel Machek <pavel@ucw.cz> writes:

> On Thu 2008-03-06 07:17:42, H. Peter Anvin wrote:
> > Ingo Molnar wrote:
> > > * H. Peter Anvin <hpa@zytor.com> wrote:
> > > 
> > > > Pawel Plociennik wrote:
> > > > > Hi Andrew and other *real* hackers,
> > > > > 
> > > > > I have sent a *last* version of a patch which it has added a new kernel \
> > > > > parameter chroot= It were discusioned a *long time* on a lkml so I hope \
> > > > > that it will has been applied.
> > > > It has been discussed and *rejected* a large number of times.
> > > > 
> > > > This is completely useless bloat.
> > > 
> > > why is it useless? Would it be more acceptable were it made dependent on a 
> > > .config option?
> > > 
> > 
> > It's useless because it's exactly and trivially replaceable with:
> > 
> > 	init=/path/to/any/sbin/chroot /newroot /sbin/init
> 
> No, that will not work, if you don't have libraries at /. This should
> be exact replacement:
> 
> init=/working_distro/lib/ld-linux.so.2 --library-path /working_distro/lib \
> /working_distro/usr/sbin/chroot /working_distro/ /sbin/init 
> ...assuming your chroot uses ld-linux.so.2. I believe above is ugly
> enough to warrant merge of chroot= option.

I fail to see how a chroot= option would solve the problem of locating
libraries.  If standard library paths won't work, linking chroot
statically seems the cleaner solution.

-- 
Måns Rullgård
mans@mansr.com

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[prev in list] [next in list] [prev in thread] [next in thread]