xfs
[Top] [All Lists]

Re: Building RH kernel + patches

To: Seth Mos <knuffie@xxxxxxxxx>
Subject: Re: Building RH kernel + patches
From: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Thu, 07 Jun 2001 14:57:56 -0500
Cc: Alan Eldridge <alane@xxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
References: <4.3.2.7.2.20010607210041.033154a0@pop.xs4all.nl>
Sender: owner-linux-xfs@xxxxxxxxxxx
Seth Mos wrote:

> At 14:37 7-6-2001 -0400, Alan Eldridge wrote:
> >I'd like to rebuild RH's current rawhide kernel SRPM, but with the 2.4.5 XFS
> >patches applied ... I'm getting sick of __alloc_pages() failed, and "Out of
> >memory: Killing process nnnn".
> >
> >However, it appears that the XFS patch includes *some* of the RH patches.
> >Is there any clear way to determine which RH patches I want to keep, and
> >which are already applied, *and* where in the sequence I want to apply the
> >XFS patch?

All the RH are applied in the RH7.1 rpms

> >
> >I'm starting to look through the patches manually, but that's going to
> >really suck. Please tell me there's a better way.
>
> Good question, I believe Russel Catalan originally did the 2.4.2-XFS kernel
> that came on the 1.0 installer disk. I think he would be the one to ask.
> There were over 200 patches in the 2.4.2 RH 7.1 kernel so I have no idea
> were to begin.
>
> The 2.4.5 is a vanilla tree with xfs and things like kdb added. There might
> a few things duplicate.
> I can imagine that RH included some of the other SGI patches like High
> availabilty.
> Just guessing here.
>
> My best guess would be to start with a 2.4.5 xfs tree and start applying
> the more harmless patches like added drivers or obvious fixes and see what
> you end up with.

OK so I was going to work on bathroom but hey what the hell.

I have the devel tree and the RH rawhide merged I just have to walk through
the files and resolve the conflicts.

If I can get it done in an hour so I'll send a patch.


>

>
>
> Good luck
>
> --
> Seth
> Every program has two purposes one for which
> it was written and another for which it wasn't
> I use the last kind.

--
Russell Cattelan
cattelan@xxxxxxxxxxx




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