From: Mike Hibler <mike@fast.cs.utah.edu>
To: Matthew.Wilcox@genedata.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Mach sources?
Date: Mon, 5 Jul 1999 22:09:09 -0600 (MDT) [thread overview]
Message-ID: <199907060409.WAA22770@fast.cs.utah.edu> (raw)
> Date: Mon, 5 Jul 1999 13:40:02 +0200
> From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
> To: parisc-linux@thepuffingroup.com
> Subject: [parisc-linux] Mach sources?
>
> It's quite a pain to actually find the sources from the reference on
> the puffin group website. There's a morass of broken links and the
> OSF no longer seem to distribute the source. So for everyone's
> convenience, the URL for the latest set of Mach/PARISC sources is:
>
> ftp://flux.cs.utah.edu/flux/mach/ALPHA/
>
> Jeff, does 9th Jan 1996 sound like the most recent version to you?
>
I'll give you the authoritative answer...
For the Utah code (Mach3 + 4.4BSD server), that was the last release,
in particular:
ftp://flux.cs.utah.edu/flux/mach/ALPHA/pa-snapshot2.tar.gz
For the OSF code (OSF Mach + Linux server), I believe someone else posted
a URL for a copy of that.
The OSF code supported a few more machines (e.g., J series) and devices
(e.g., EISA stuff) than we did, though we might have had a few bug fixes
they didn't. Of most interest in the Utah code is the HP-UX compatibility
code (mostly in the Lites server/emulator) which was good enough to run the
X11 server and Netscape.
next reply other threads:[~1999-07-06 4:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-06 4:09 Mike Hibler [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-07-05 11:40 [parisc-linux] Mach sources? Matthew Wilcox
1999-07-05 12:31 ` Helge Deller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199907060409.WAA22770@fast.cs.utah.edu \
--to=mike@fast.cs.utah.edu \
--cc=Matthew.Wilcox@genedata.com \
--cc=parisc-linux@thepuffingroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.