Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

1.4.1 vaxdiffs.gz file

1 view
Skip to first unread message

Todd Whitesel

unread,
Mar 1, 2000, 3:00:00 AM3/1/00
to port...@netbsd.org
While getting 1.4.2 finalized we discovered

/pub/NetBSD/NetBSD-1.4.1/vax/vaxdiffs.gz

the contents of which don't appear to have ever been committed anywhere,
not on the release branch nor in -current (as of late December anyway;
I don't have a recent checkout handy).

I just got done submitting patches for these directly against the release
branch, since (a) we're literally about to label 1.4.2, and (b) putting
these in current is something that really should be done by someone who's
more familiar with the vax port than me.

Anyone? Anyone?

"Bueller?"

Todd Whitesel
toddpw @ best.com

Peter Joules

unread,
Mar 2, 2000, 3:00:00 AM3/2/00
to port...@netbsd.org
In article <2000030108...@shell17.ba.best.com>, Todd Whitesel
<tod...@best.com> writes
>While getting 1.4.2 finalized

[Snip]

Will 1.4.2 contain the RZ56 patch?

--
Regards
Pete

Todd Whitesel

unread,
Mar 2, 2000, 3:00:00 AM3/2/00
to Peter Joules
> Will 1.4.2 contain the RZ56 patch?

I hope so. The main reason I am annoyed by vaxdiffs.gz is that I should
not have had to submit those diffs during the 11th hour; someone should
have arranged for them to be properly pulled up many many months ago.

I've now taken care of the release branch, and I'm asking for a vax guru
to take care of evaluating them for -current.

One of the patches is a change to arch/vax/vsa/ncr.c which sets a field
called sc_no_disconnect to 0xff. Is that "the RZ56 patch" ?

There are also changes to the boot loader that might affect recognition
of RZ devices, in case that's it.

Todd Whitesel

unread,
Mar 5, 2000, 3:00:00 AM3/5/00
to Brian Chase
> At the very least, it'd be nice if a similar set of patches were available
> under 1.4.2 for people to apply to the distributed 1.4.2 sources.

Not to worry. Havard and I did some last minute shoveling to get them in,
so if you check out -rnetbsd-1-4-PATCH002 you will get those patches.

Only one exception: etc/etc.vax/Makefile.inc. I've got other local patches
to that one which I'll be reimplementing in current once I get off 1.4.2.

We did rename _POSTAGE_STAMP_ and _SMIDGEN_ to POSTAGE_STAMP and SMIDGEN
before putting them in arch/vax/conf. They will appear in binary/kernel
for 1.4.2, unless someone knows a good reason why not.

Brian Chase

unread,
Mar 5, 2000, 3:00:00 AM3/5/00
to Anders Magnusson
On Sat, 4 Mar 2000, Anders Magnusson wrote:
> > While getting 1.4.2 finalized we discovered
> >
> > /pub/NetBSD/NetBSD-1.4.1/vax/vaxdiffs.gz
> >

> Well, I have committed (almost) all of those fixes into -current now.
> Many thanks for this! Great!

Argh.. Brownlee and I worked hard on this during the 1.4.1 release and I
know we asked to have them pulled up into the tree(s) at that time. Well
Brownlee did the coding and generated the diffs. I was his personal QA
dept and tested the changes on my collection of VAXen. I was really
hoping they'd have made their way into 1.4.2 since a lot of the vaxdiffs
were what made the 1.4.1 a relatively easy release to install from
scratch.

At the very least, it'd be nice if a similar set of patches were available
under 1.4.2 for people to apply to the distributed 1.4.2 sources.

-brian.
--- Brian Chase | b...@world.std.com | http://world.std.com/~bdc/ -----
"Never program a computer you can lift." -- Barry Shein


Anders Magnusson

unread,
Mar 5, 2000, 3:00:00 AM3/5/00
to Todd Whitesel
> While getting 1.4.2 finalized we discovered
>
> /pub/NetBSD/NetBSD-1.4.1/vax/vaxdiffs.gz
>
Well, I have committed (almost) all of those fixes into -current now.
Many thanks for this! Great!

-- Ragge


Anders Magnusson

unread,
Mar 5, 2000, 3:00:00 AM3/5/00
to Brian Chase
>
> Argh.. Brownlee and I worked hard on this during the 1.4.1 release and I
> know we asked to have them pulled up into the tree(s) at that time. Well
> Brownlee did the coding and generated the diffs. I was his personal QA
> dept and tested the changes on my collection of VAXen. I was really
> hoping they'd have made their way into 1.4.2 since a lot of the vaxdiffs
> were what made the 1.4.1 a relatively easy release to install from
> scratch.
>
It may be my fault in that case, sorry in that case.
But anyway; the doc/dist changes are in now, so be happy :-)

-- Ragge

0 new messages