On Sun, 2005-01-09 at 14:59, Andrew L. Gould wrote:
> On Sunday 09 January 2005 08:44 am, Andy Ruhl wrote:
> > On Sun, 9 Jan 2005 08:26:52 -0600, Andrew L. Gould 
> <algould@datawok.com> wrote:
> > > A newbie question:
> > >
> > >  I have NetBSD 2.0 Release for x86 running on a PC for
> > > cross-compiling. How do I apply the patch? (Another task I've never
> > > done.)
> >
> > There is a patch command. If you read the security notices from the
> > main www.netbsd.org site, there is info on how to use it. Also man
> > patch
> >
> > If you have your (correct) sources in place, you just run:
> >
> > patch < patch_file
> >
> > But you don't want to patch a 2.0 release system with a patch
> > intended for current. Unless you go into the file in each branch and
> > find out they are the same, and all the dependencies that the patch
> > changes/doesn't change are the same. Generally you want to be on the
> > same source level.

I haven't tried applying this patch to the release tree yet, but from
what Matthew said, the same interrupt code was in 1.6.x, so unless the
code has been altered since, it should still apply.

By all means track the netbsd-2 stable branch though, which should be
safe.

> > I'm thinking about running current on my Mobilepro but I haven't
> > researched it yet.
> 
> Since current is always evolving, how do I know what the correct source 
> level is?

You don't. :-)

>   Does anyone know if the patch has already been committed to 
> current?

Not as far as I know, unless it has in the past couple of days. IMO it
should be committed as it allowed me to get a lot further with my
Workpad.

Matt