xfs
[Top] [All Lists]

Re: [Patch] cramfs initrd will not boot

To: "Karl M. Hegbloom" <karlheg@xxxxxxxxxxxxxx>
Subject: Re: [Patch] cramfs initrd will not boot
From: Steve Lord <lord@xxxxxxx>
Date: 19 Dec 2001 15:15:21 -0600
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <87adwfndad.fsf@juniper.intra.microsharp.com>
References: <87adwfndad.fsf@juniper.intra.microsharp.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Wed, 2001-12-19 at 14:52, Karl M. Hegbloom wrote:
>  
>  This diff is between Debian kernel-source-2.4.16 and a checkout of
>  SGI 2.4.16 that was last freshened yesterday.  (2001-12-18)
> 
>  I have not tested yet, but I believe that it will fix a problem I am
>  experiencing, where an SGI kernel will not load a cramfs from an
>  initrd.  This patch may be part of the Debian kernel and not from
>  Linus' kernel.  I'm not certain...  There may be other patches in the
>  Debian kernel that you might like to have; could be worth having a
>  look.
> 
>  I need this (and perhaps others will as well) since I need to use
>  your kernel for the XFS support.  Right now, it fails to mount the
>  cramfs initrd, saying "wrong magic".  I hope that this patch fixes
>  the problem.

In general, we do not carry patches for other problems in our tree,
since doing this extends the scope of the diff - and makes it appear
that xfs requires changes in places where it does not. Our tree
should be Linus's (or Marcello's now) plus changes for XFS and kdb,
nothing more and nothing less.

If you want something like this to make it into the 2.4 stream
then the best bet is to try and get Marcelo to accept it. So I
would check that it is not already in the 2.4.17-rc2 patch and
if not, wait until Marcelo starts accepting patches for 2.4.18
and send it to him. Once it is in the 2.4 series it will appear
in our patches.

Until then you are pretty much stuch with applying the patch on top
of the xfs tree.

Steve

-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@xxxxxxx


<Prev in Thread] Current Thread [Next in Thread>