From: bqt@update.uu.se (Johnny Billquist)
Subject: [TUHS] Re: TUHS digest, Vol 1 #71 - 2 msgs
Date: Thu, 29 Aug 2002 12:27:25 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0208291220490.23934-100000@Tempo.Update.UU.SE> (raw)
In-Reply-To: <200208290206.g7T26eD19221@minnie.tuhs.org>
Sokolov wrote:
> Johnny Billquist <bqt at update.uu.se> wrote:
>
> > I'm trying to figure out a way of getting the MSCP driver from Ultrix
> > available for porting to NetBSD.
>
> I don't support NetBSD, but Ultrix' MSCP/SCA code is available to everyone.
I know you don't support it. :-)
> > The problem is that it's (c) by Digital, now HP.
>
> It is a problem only if you choose to honor copyright laws. Since that is your
> personal voluntary choice, it is your problem.
Yes, and it's *that* problem I'm looking for a solution to.
> > Could I be lucky enough that Ultrix actually have been released?
> > And I'm talking Ultrix-32 here, not Ultrix-11.
>
> The International Free Computing Task Force has freed the Ultrix-32 V2.00 and
> V4.20 sources. They can be found on our FTP site in
Freed as in "legally freed", or just "made available".
> ivan.Harhan.ORG:/pub/UNIX/thirdparty/Ultrix-32
harhan.org don't exist from where my dns is looking... :-/
Another machine I have access to managed to resolve ivan.harhan.org to
208.221.139.1, but there is no response at that address.
However, if it is just the sources, and not some legal notes available,
then I don't need to go there.
Johnny
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at update.uu.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
next parent reply other threads:[~2002-08-29 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200208290206.g7T26eD19221@minnie.tuhs.org>
2002-08-29 10:27 ` Johnny Billquist [this message]
2002-09-04 21:06 Michael Sokolov
2002-09-08 3:20 ` Greg 'groggy' Lehey
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=Pine.LNX.4.21.0208291220490.23934-100000@Tempo.Update.UU.SE \
--to=bqt@update.uu.se \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).