From: Phil Kulin <schors@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] building Alef language
Date: Tue, 8 Oct 2019 22:50:30 +0300 [thread overview]
Message-ID: <CAK=u2EVN7rPtMjqX27tqnde6uSLVgajK+ZX_0JCeNky3JYMHFQ@mail.gmail.com> (raw)
In-Reply-To: <CAOFTvP+6hk-YmXT9rj1pQutLYmW3=vtvFO=SXyE_d8jSeBkm5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1975 bytes --]
It's great! Is there a script somewhere that translate 8.3 names to normal
UTF8 through _CONFORM.MAP?
On Tue, Oct 8, 2019 at 6:09 PM Sergey Zhilkin <szhilkin@gmail.com> wrote:
> Do not know anything about licensing, but found Plan 9 archive on
> archive.org :) https://archive.org/details/plan9archive
> This archive include all editions and iso's.
>
> ср, 25 сент. 2019 г. в 20:36, Steve Simon <steve@quintile.net>:
>
>>
>> http://9p.io/sources/contrib/steve/historic/2nd-edition/pcdist/README
>>
>> t
>> 😀
>>
>> that was my stuff, but its only the documentation that was published,
>> not the code. there was a single floppy
>> demo which might be around.
>>
>> I do have a 2nd edition license but i would not release the code without
>> sign-off from lucent, nokia, or whoever owns the code these days.
>>
>> bell-labs payed for the research work that produced plan9 and respect
>> them (and their licensing terms) fir doing so.
>>
>> -Steve
>>
>>
>>
>>
>> On 25 Sep 2019, at 7:40 am, Sergey Zhilkin <szhilkin@gmail.com> wrote:
>>
>> 2nd Ed are still around
>> http://9p.io/sources/contrib/steve/historic/2nd-edition/pcdist/README
>>
>> If it was putted on contrib sources - no one have concerns, i think.
>>
>> вт, 24 сент. 2019 г. в 14:57, Rodrigo G. López <rodrigosloop@gmail.com>:
>>
>>> i think both henesy and BurnZeZ ran 1st and 2nd Ed at some point.
>>> i'm not aware of any license requirement, but do they (Nokia) even care?
>>>
>>> On Tue, Sep 24, 2019, 1:26 PM hiro <23hiro@gmail.com> wrote:
>>>
>>>> who is selling those licenses?
>>>>
>>>>
>>
>> --
>> С наилучшими пожеланиями
>> Жилкин Сергей
>> With best regards
>> Zhilkin Sergey
>>
>>
>
> --
> С наилучшими пожеланиями
> Жилкин Сергей
> With best regards
> Zhilkin Sergey
>
--
Non nobis Domine non nobis sed Nomini Tuo da gloriam
Phil Kulin
[-- Attachment #2: Type: text/html, Size: 4396 bytes --]
next prev parent reply other threads:[~2019-10-08 19:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 20:45 Phil Kulin
2019-09-20 21:05 ` Rodrigo G. López
2019-09-21 2:40 ` Sean Hinchee
2019-09-21 3:14 ` Lucio De Re
2019-09-21 12:33 ` hiro
2019-09-22 7:46 ` Phil Kulin
2019-09-22 9:38 ` Rodrigo G. López
2019-09-22 9:44 ` Ethan Gardener
2019-09-23 1:01 ` Sean Hinchee
2019-09-24 9:53 ` Steve Simon
2019-09-24 11:25 ` hiro
2019-09-24 11:56 ` Rodrigo G. López
2019-09-25 6:40 ` Sergey Zhilkin
2019-09-25 17:35 ` Steve Simon
2019-10-08 15:06 ` Sergey Zhilkin
2019-10-08 19:50 ` Phil Kulin [this message]
2019-10-08 20:24 ` Sergey Zhilkin
2019-10-08 21:54 ` Steve Simon
2019-09-21 14:05 ` Phil Kulin
2019-09-21 17:58 ` Phil Kulin
2019-09-21 20:45 ` Phil Kulin
2019-09-21 23:00 ` Rodrigo G. López
2019-09-22 7:08 ` Phil Kulin
2019-09-22 9:27 ` Ethan Gardener
2019-09-22 9:33 ` Phil Kulin
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='CAK=u2EVN7rPtMjqX27tqnde6uSLVgajK+ZX_0JCeNky3JYMHFQ@mail.gmail.com' \
--to=schors@gmail.com \
--cc=9fans@9fans.net \
/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).