From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id b62ca9a0 for ; Wed, 28 Aug 2019 16:35:34 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id E38F39BCEC; Thu, 29 Aug 2019 02:35:32 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 0D3479BCD5; Thu, 29 Aug 2019 02:35:08 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="B91rvCUy"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 8933A9BCD5; Thu, 29 Aug 2019 02:35:05 +1000 (AEST) Received: from mail-oi1-f174.google.com (mail-oi1-f174.google.com [209.85.167.174]) by minnie.tuhs.org (Postfix) with ESMTPS id 03F379BCD0 for ; Thu, 29 Aug 2019 02:35:05 +1000 (AEST) Received: by mail-oi1-f174.google.com with SMTP id y8so164222oih.10 for ; Wed, 28 Aug 2019 09:35:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ghHQi0Ll2fci2DjKMmc2DUEYN8kkY4eFVE/042Uwm94=; b=B91rvCUyFU7ROT2+xJpJW8jTE2TNv8cG3G3HQ4knm01C+4AhPjWMbFYHO+6jBdvI1b wSbV0ztUEho7qzwQ+rUL2Ri/O8PGSsnuo6Zbxt5tig9Ki6SJaw1P2QgiGI5l6CI0aSXe RwZGwS9+icek4Sy0Ek1gk/2Iy8E/YmgkjaqWCO1TsMmC5/IE4LlWSmXjtwYdVS9LzEGb CMe++u2FBTOMlNFLG4pE2SY+hc4OK3awFJPH9IDO3DFdJn/VUAPafFS3+ehlO2FmrYoW PMclUmSMdwNoum/j5QKy5mcYvDdlbmz8j/N1vqcCXU9DghjP6LZ0+J79GoAMoUkxt8NK J00w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ghHQi0Ll2fci2DjKMmc2DUEYN8kkY4eFVE/042Uwm94=; b=eG2OAafFVbVM5ezfFemsPb96NyLtNzUK4KsLbW8ruRdm8KofFKDz/t0e+nmc0QHA42 Ps90QLKny4JpaiiWSACfmi4uoIoeOCpJu46QHf8PgFgX4qBKm2YWsC7dxdEAapxuHvgR CK7+7zf9D5sxINSpoyXL8It1kOErC/URonjrCJCPQZh5Up3Nl+5fMvZ47YW+awcn3owl UUlcHh0Qo81A9RkejM12TV9oRQwTitmbXvpDwlpEpYZixiXEHwIHCg0W0vEHAxXJaVtN g1MrlTLoEFu1xRMf7hhpx8EMH84dbaVptqVJiJY5S06ym1/EXgsgamN9T0LFAV6+VSjN vv2w== X-Gm-Message-State: APjAAAWM2eu0y24l3HIBFRkSBxE2FXNf3ajcZhfWQOVWbdzg5YE2CFMF t72R/td5WtqBRyMvfWn9TUFxSxHsmSA94BpaZjWb9JCrqyM= X-Google-Smtp-Source: APXvYqysVUIT8oskPhl18Knft0jzbN1RJ1qfiScAdBoLpbQ24W5PFfYdUJsz//ZU+ftF9D3upsYzsOvKPvzkn2rA5c0= X-Received: by 2002:aca:cd12:: with SMTP id d18mr3476506oig.68.1567010103596; Wed, 28 Aug 2019 09:35:03 -0700 (PDT) MIME-Version: 1.0 References: <20190828063045.GE75146@server.rulingia.com> In-Reply-To: From: Henry Bent Date: Wed, 28 Aug 2019 12:34:46 -0400 Message-ID: To: Clem Cole Content-Type: multipart/alternative; boundary="000000000000959d7f05912ff846" Subject: Re: [TUHS] If not Linux, then what? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "tuhs@minnie.tuhs.org" Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000959d7f05912ff846 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 28 Aug 2019 at 10:05, Clem Cole wrote: > If that's the MIPs code base, it is likely to not be there. I could be > forgetting something, but I remember that DECnet was released for the MIP= S > products. It was on Tru64 and Ultrix, but is a 'layered product' so you > needed a license to install it and it needed to be a late enough version > that had switched to exposing a full OSI stack. > > That said, I do not remember/know how well it functioned talking to any > OSI stack other than DECs. > OSF/1 for MIPS wasn't actually a beta but it might as well have been. It was slow, it was buggy, and DEC dropped support for it fairly quickly after it was released. It was never ported to any of the R4k machines. Customers were not happy. Anyway, the official release announcement ( https://groups.google.com/forum/?hl=3Den#!original/bit.listserv.esl-l/BovGe= 3q9yWE/cqlcCYfxmbAJ ) mentions a few layered products, none of which I have ever seen in the wild. No OSI implementation is mentioned. Looking through a list of layered products for Ultrix from mid-1994, I see a few OSI-related things: MIPS: DEC OSI Application 1.1 GZSAA Developer's Toolkit DECnet/OSI for ULTRIX 5.1A YT9AA OSI Application Toolkit 5.1A OSIAP_RISC VAX: DECnet/OSI for ULTRIX 5.1A 716AA OSI Application Toolkit 5.1A OSIAP_VAX If you want more documentation on any of these, contact me off-list. -Henry > On Wed, Aug 28, 2019 at 7:05 AM Jason Stevens < > jsteve@superglobalmegacorp.com> wrote: > >> >> >> I have OSF/1 1.0 running on gxemul =E2=80=A6 >> >> >> >> Any idea on where/ how to configure OSI? >> >> >> >> >> >> OSF/1 Release 1 (OSFMIPS) console >> >> >> >> login: root >> >> Last login: Thu Aug 29 06:03:07 on console >> >> DEC OSF/1 V1.0 (Rev. 166); Sun Jun 07 19:23:34 CDT 1970 >> >> DEC OSF/1 V1.0 Worksystem Software (Rev. 161) >> >> >> >> # find / -name 'osi*' -print >> >> # >> >> >> >> *From: *Peter Jeremy >> *Sent: *Wednesday, August 28, 2019 2:47 PM >> *To: *Wesley Parish >> *Cc: *TUHS main list >> *Subject: *Re: [TUHS] If not Linux, then what? >> >> >> >> On 2019-Aug-28 18:19:21 +1200, Wesley Parish >> >> wrote: >> >> >Speaking of OSI stacks, I know 4.4BSD Lite came with some fragments of >> >> >one. OSI's dead and hardly mourned these days, but did anyone in the >> >> >Unix world ever get beyond the 4.4BSD fragmentary implementation? >> >> >> >> There was ISODE >> >> (https://en.wikipedia.org/wiki/ISO_Development_Environment). >> >> I recall experimenting with it but didn't actually use it in anger. >> >> >> >> I know that DEC/Compaq/HP Tru64 Unix (nee OSF/1) came with a OSI stack - >> >> we had customers who wanted/used FTAM and I was surprised to find it >> >> came with the OS. >> >> >> >> -- >> >> Peter Jeremy >> >> >> > --000000000000959d7f05912ff846 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, 28 Aug 2019 at 10:05, Clem Cole &= lt;clemc@ccc.com> wrote:
<= div class=3D"gmail_quote">
If = that's the MIPs code base, it is likely to not be there.=C2=A0 I could = be forgetting something, but I remember that DECnet was released for the MI= PS products.=C2=A0 =C2=A0It was on Tru64 and Ultrix, but is a 'layered = product' so you needed a license to install it and it needed to be a la= te enough version that had switched to exposing a full OSI stack.

That said, I do not remember/know ho= w well it functioned talking to any OSI stack other than DECs.
<= /blockquote>

OSF/1 for MIPS wasn't actually a beta b= ut it might as well have been.=C2=A0 It was slow, it was buggy, and DEC dro= pped support for it fairly quickly after it was released.=C2=A0 It was neve= r ported to any of the R4k machines.=C2=A0 Customers were not happy.=C2=A0 = Anyway, the official release announcement ( https://groups.google.com/forum/?hl=3Den#!original/bit.listserv.esl-l/BovG= e3q9yWE/cqlcCYfxmbAJ ) mentions a few layered products, none of which I= have ever seen in the wild.=C2=A0 No OSI implementation is mentioned.
<= /div>
=C2=A0
Looking through a list of layered products for U= ltrix from mid-1994, I see a few OSI-related things:

MIPS:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 DEC OSI Application =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1.1 =C2=A0 =C2=A0GZSAA
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 Developer's Toolkit

=C2=A0 =C2=A0 = =C2=A0 =C2=A0 DECnet/OSI for ULTRIX =C2=A0 =C2=A0 =C2=A0 =C2=A0 5.1A =C2=A0= YT9AA

=C2=A0 =C2=A0 =C2=A0 =C2=A0 OSI Application= Toolkit =C2=A0 =C2=A0 =C2=A0 5.1A =C2=A0 OSIAP_RISC

VAX:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 DECnet/OSI for ULTRIX =C2=A0 = =C2=A0 =C2=A0 =C2=A0 5.1A =C2=A0 716AA

=C2=A0 =C2= =A0 =C2=A0 =C2=A0 OSI Application Toolkit =C2=A0 =C2=A0 =C2=A0 5.1A =C2=A0 = OSIAP_VAX

If you want more documentation on any of= these, contact me off-list.

-Henry
<= div>

On Wed, Aug 28, 2= 019 at 7:05 AM Jason Stevens <jsteve@superglobalmegacorp.com> wrote:
=

=C2=A0

I have OSF/1 1.0 running on gxemul =E2=80=A6

<= u>=C2=A0

Any idea on where/ how to con= figure OSI?

=C2=A0

=C2=A0

OSF/1 Release 1 (O= SFMIPS) console

=C2=A0

login: root

Last login: Thu Aug 29= 06:03:07 on console

DEC OSF/1 V1.0 (Rev. 166); S= un Jun 07 19:23:34 CDT 1970

DEC OSF/1 V1.0 Worksy= stem Software (Rev. 161)

=C2=A0

=

# find / -name 'osi*' -print

#

=C2=A0

From: Peter Jeremy
Se= nt: Wednesday, August 28, 2019 2:47 PM
To: Wesley Parish
Cc: TUHS main listSubject: Re: [TUHS] If not Linux, then what?

=C2=A0

On 2019-Aug-28 18= :19:21 +1200, Wesley Parish <wobblygong@gmail.com>

wrote= :

>Speaking of OSI stacks, I know 4.4BSD Lite = came with some fragments of

>one. OSI's de= ad and hardly mourned these days, but did anyone in the

>Unix world ever get beyond the 4.4BSD fragmentary implementation= ?

=C2=A0

= There was ISODE

(https://en.wikipedi= a.org/wiki/ISO_Development_Environment).

I re= call experimenting with it but didn't actually use it in anger.

=C2=A0

I know th= at DEC/Compaq/HP Tru64 Unix (nee OSF/1) came with a OSI stack -

we had customers who wanted/used FTAM and I was surprised to= find it

came with the OS.

=C2=A0

--

Peter Jeremy

=C2=A0

=
--000000000000959d7f05912ff846--