Linux on VAX - Dead ?

[Jan-Benedict Glaw]

Hi!

On Sun, 2023-01-15 01:18:27 +0000, Maciej W. Rozycki <macro at orcam.me.uk> wrote:
> On Sat, 14 Jan 2023, David Brownlee wrote:
> > >  You are welcome.  Bugs in the compiler hindered progress with the
> > > userland.  Chances are this updated GCC would work better.
> > 
> > The VAX gcc work is very much appreciated, and has kept NetBSD/vax
> > from falling into non-viability. Hopefully NetBSD can continue to keep
> > a light on in the back of *nix on VAX until someone has time to bring
> > VAXlinux back up :)
> 
>  In principle I haven't abandoned the VAX/Linux effort, but reality may 
> disagree.  We shall see.  My biggest obstacle has been the distraction 
> coming from PSU failures (electrolytic capacitor leaks caused by improper 
> chemistry) forcing me to focus on hardware repairs rather than software 
> work.

While the Linux port is a sad story as it somewhat came to an end, at
least the system availability may get better. You know, I was long
searching for a room to setup my old system to be 100% operated
remotely. I'm actually negotiating something right now. :) So hope is
there that this may actually become a reality!

  The VAX port, as is, is pretty dead. I wouldn't try pulling in newer
Linux patches into our former tree, but use our arch stuff to add it
to current Linux. And glibc? What were the most "interesting" issues?
ISTR that it was threading and possibly a TLS ABI?

MfG, JBG

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lug-owl.de/pipermail/vax-linux/attachments/20230115/2eaf2055/attachment.sig>