From: Andrea Arcangeli <andrea@suse.de>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre8aa3
Date: Thu, 16 May 2002 14:56:42 +0200 [thread overview]
Message-ID: <20020516125641.GI1025@dualathlon.random> (raw)
In-Reply-To: <20020516020134.GC1025@dualathlon.random> <Pine.LNX.4.44L.0205152303500.32261-100000@imladris.surriel.com> <20020516023238.GE1025@dualathlon.random> <20020516093630.B5540@flint.arm.linux.org.uk>
On Thu, May 16, 2002 at 09:36:30AM +0100, Russell King wrote:
> On Thu, May 16, 2002 at 04:32:38AM +0200, Andrea Arcangeli wrote:
> > On Wed, May 15, 2002 at 11:06:51PM -0300, Rik van Riel wrote:
> > > --- snip from linuxrc ----
> > > mount --ro -t $rootfs $rootdev /sysroot
> > > pivot_root /sysroot /sysroot/initrd
> > > ------
> > >
> > > This way you can specify both the root fs and - if wanted -
> > > special mount options to the root fs. Then you pivot_root(2)
> > > to move the root fs to / and the (old) initrd to /initrd.
> >
> > both lines are completly superflous, very misleading as well. I
> > recommend to drop such two lines from all the full blown bug-aware
> > linuxrc out there (of course after you apply the ordering fix to the
> > kernel).
>
> Have you thought about reading Documentation/initrd.txt and following
> the described method? (last modified December 2000 according to the
> comments and the mtime on the file).
I didn't noticed the API changed in the docs, so my suggestion of
yesterday to remove such two lines is wrong sorry. I was only reading
the kernel code and I was using my own old debugging initrd were I could
reproduce the ext3 problem. Interestingly there's no way to guess the
new API by only reading the kernel code like I was doing.
Andrea
next prev parent reply other threads:[~2002-05-16 12:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 21:27 2.4.19pre8aa3 Andrea Arcangeli
2002-05-15 21:56 ` 2.4.19pre8aa3 Andreas Dilger
2002-05-16 2:18 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-15 22:30 ` 2.4.19pre8aa3 Rik van Riel
2002-05-16 2:01 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 2:06 ` 2.4.19pre8aa3 Rik van Riel
2002-05-16 2:32 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 2:42 ` 2.4.19pre8aa3 Rik van Riel
2002-05-16 2:58 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 8:36 ` 2.4.19pre8aa3 Russell King
2002-05-16 8:59 ` 2.4.19pre8aa3 Russell King
2002-05-16 12:56 ` Andrea Arcangeli [this message]
2002-05-16 9:27 ` 2.4.19pre8aa3 Juan Quintela
2002-05-16 16:07 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 18:37 ` 2.4.19pre8aa3 Rik van Riel
2002-05-16 18:59 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 3:12 ` 2.4.19pre8aa3 Andrew Morton
2002-05-16 3:23 ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 19:26 ` 2.4.19pre8aa3 Christoph Hellwig
2002-05-31 20:34 ` 2.4.19pre8aa3 Andrea Arcangeli
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=20020516125641.GI1025@dualathlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).