I've had 1.5/vax working since it was fresh, which was shortly
after support for the VAXstation 4000/60 SCSI host adapter was
introduced.  Are there any known reasons to upgrade?

As for Slackware, it's the Linux to choose if you ever need one.  
Although occasionally tricky to install (just as it was the
first time I tried in 1994-5), and relatively outdated[1], surely 
downloading and compiling a few tarballs is easy in comparison
with the work required to strip all the bloat and annoyances from
something like RedHat.  NetBSD is compact and elegant in
comparison with *that*.

-aw
(* it [slack] hasn't even jumped on the PAM bandwagon yet)

On Wed, 8 Mar 2006, Gregg C Levine wrote:

> Hello!
> The keyword, Kevin, everyone, in my little speech down there was
> "around". I "grok" that I am allowed to be wrong. It is a part of
> life. Part of the problem with understanding the strange behavior of
> Linux, or even NetBSD happened to be when I got started with them. For
> Linux it was an old port during the 2.0.3x series, and yes it was a
> Slackware one. I am still with Slackware. I only use that guy's
> software for business. 
> 
> At some point in time I will very definitely have NetBSD running here,
> I last had it working back during the 1.x series. For both Intel, and
> VAX. Say? 
> Can we run SIMH/VAX inside a Xen domain? 
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> And for that discussion I'm going to move the thread contents, not
> subject to NetBSD/Xen. 
> 
> 
> 
> For what we are discussing I will be pleased to admit that some sort
> of networking did exist in the kernel for both serial delivery and
> Ethernet around the first series of kernels, and then the 2.0.xx ones.
> Which is why one of us has reported a very early was indeed doing as I
> have just described.
> 
> Before we discuss more Penguin versus Daemon stories, I suggest we
> return to the wonderful world of NetBSD and the VAX.
> 
> Gregg C Levine hansolofalcon@worldnet.att.net
> ---
> "Remember the Force will be with you. Always." Obi-Wan Kenobi 
> 
> > -----Original Message-----
> > From: port-vax-owner@NetBSD.org [mailto:port-vax-owner@NetBSD.org]
> On
> > Behalf Of Kevin Ogden
> > Sent: Wednesday, March 08, 2006 6:52 PM
> > To: port-vax@NetBSD.org
> > Subject: Re: current port-vax status
> > 
> > 
> > On Mar 8, 2006, at 6:13 PM, Gregg C Levine wrote:
> > 
> > > And I agree regarding Linux and networking and XKernel. I do know
> that
> > > Tux got networking around the 2.xx kernel, but it was decidedly
> > > primitive. Ethernet arrived around the time of the middle kernels,
> but
> > > don't hold me to that.
> > 
> > I'm not trying to be a Linux fanboy but I was running an old version
> of
> > Slackware with kernel version 1.2.11 with full TCP/IP support (with
> a
> > 3COM 3c503 ethernet card) and X-Windows (w/ OpenLook and DOOM even)
> on
> > a 486/33.  Linux has had networking for quite a while though it's
> > wasn't near as robust as BSD at the time.  Shortly after getting
> sick
> > of Linux and PC's in general I installed NetBSD 1.2 on a Mac IIci
> and
> > started playing with BSD (A/UX was too pricey and IMHO not as nice
> of
> > an OS as NetBSD).
> > 
> > --Kevin D. Ogden
> 
>