[lkml]   [2002]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.19pre8aa3
On Wed, May 15, 2002 at 11:42:24PM -0300, Rik van Riel wrote:
> On Thu, 16 May 2002, Andrea Arcangeli wrote:
> > I'm not using the full blown initrd of most distros that is aware of the
> Then I guess we found the problem. ;)

disagreement, my initrd is not the problem. the kernel code is really
explicit about what it will do with the real root fs, it will mount it
by itself, I am definitely not required to mount it by myself within
linuxrc, for sure not to workaround a bug in the kernel, and now in
2.4.19pre mounting it in linuxrc is even worse idea because the mount
will likely fail at the first different mount option. linuxrc is allowed
to just run exit(2) and the real root fs must still be mouned correctly,
that is the linuxrc API.

> > > --- snip from linuxrc ----
> > > mount --ro -t $rootfs $rootdev /sysroot
> > > pivot_root /sysroot /sysroot/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).
> Personally I hope the special initrd code gets moved from
> kernelspace into userspace.

I don't care about this part, if it gets changed I will update my
initscripts to act accordingly, however requiring all linux users to
update their init scripts in mid/late 2.4 is probably not a good idea,
if you really want to drop such two lines then do it in 2.5 only (not
recommended, still it's a gratuitous API change IMHO).

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:26    [W:0.102 / U:0.100 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site