On Tuesday 03 July 2001 09:21 am, Paul Abrahams wrote:
> John Hiemenz wrote:
> > On Monday 02 July 2001 17:03, you wrote:
> > > I'm currently running the 2.4.4 kernel with the Win4Lin
> > > patches. I'm considering upgrading to the 2.4.5 kernel
> > > (from kernel.org, not from a particular vendor). The
> > > easiest way to do that would be to apply the 2.4.4-2.4.5
> > > patch to the kernel source tree and go with it. I've read
> > > that the Win4Lin kernel patches work equally well for 2.4.4
> > > and 2.4.5. Is my simple-minded update likely to work, or
> > > do I need to go the long way round the barn and build a
> > > virgin 2.4.5 kernel and then apply the Win4Lin mods?
> > >
> > > I'd expect it to work if the two sets of patches don't
> > > overlap in any significant way.
> >
> > I've been very successfult with grabbing the kernel 2.4.5 sources
> > from kernel.org, and applying the supplied patch for Win4Lin.
>
> That't not quite what I wanted to do. Your procedure is equivalent
> to:
>
> create 2.4.4 sources
> patch 2.4.4 -> 2.4.5
> patch for Win4Lin
>
> Mine is:
>
> create 2.4.4 sources
> patch for Win4Lin
> patch 2.4.4 -> 2.4.5
>
> I was pretty sure the first one would work. I was questioning
> whether the second one was equivalent and, if not, whether the
> differences mattered.
>
Oops. Sorry. I guess I assumed you would grab new 2.4.5 sources and
go from there. I have bandwidth and grabbing new, complete source
tarballs is just the way I have been doing it.
I am going to make a stab guess and bet that if the 2.4.4 Win4Lin patch
installs without problems onto fresh 2.4.5 kernel source, then the
files it is updating are appearing the same as they did as 2.4.4 kernel
sources, so shouldn't be a problem. I think.
You could always look into the Win4Lin patch file and see what files
are getting patched and check them manually first just to be safe.
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
