From: Sean Hinchee <henesy.dev@gmail.com>
To: Oleg Finkelshteyn <olegfink@gmail.com>
Cc: bhgv <bhgv.empire@gmail.com>,
inferno-os <inferno-os@googlegroups.com>,
"9fans@9fans.net" <9fans@9fans.net>
Subject: [9fans] Re: [inferno-os] sources of Alef language
Date: Sat, 7 Nov 2020 10:56:35 -0800 [thread overview]
Message-ID: <CADmmOS9UgkmzwCB98djmnGvWCkN31+t6902LyTA6Zc0T8_+LTA@mail.gmail.com> (raw)
In-Reply-To: <acdf3a6f-be3d-4117-b6c5-041050d6b2ad@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
Check the first section for Alef in this post: https://seh.dev/go-legacy/
As mentioned before, my 2e post is probably your best direction at getting
a working Alef chain to play with
A snapshot of BurnZeZ’s work to port forward (from the public grid):
https://github.com/Plan9-Archive/alef
A snapshot of my (poor) attempt to port forward:
https://github.com/henesy/alef2
I believe this is an unmodified Alef source tree:
https://github.com/henesy/alef
If there’s anyone to contact directly about the state of the modern
9front/386 port, it’s BurnZeZ.
Cheers,
Sean
On Saturday, November 7, 2020, Oleg Finkelshteyn <olegfink@gmail.com> wrote:
> > the sources of Alef language?
>
> 9fans is probably a better mailing list for this.
>
> alef was included in the plan9 second edition; that would be a good place
> to start. see https://seh.dev/plan9-2e/ for some pointers and a complete
> iso (including alef sources) in the 'archive'.
>
> you can mount that iso with 9660srv (either in plan9 or with plan9port) to
> recover original filenames.
>
> i remember there was an ongoing effort to update alef to run on modern
> plan9; 9fans will know more about this.
>
> --
> You received this message because you are subscribed to the Google Groups
> "inferno-os" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to inferno-os+unsubscribe@googlegroups.com.
> To view this discussion on the web, visit https://groups.google.com/d/
> msgid/inferno-os/acdf3a6f-be3d-4117-b6c5-041050d6b2ad%40www.fastmail.com.
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T7a4d9d7ff7642ef8-M82787a523820485b8f54cc98
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 3136 bytes --]
prev parent reply other threads:[~2020-11-07 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45626b08-d288-48dd-815b-19e4c258a3e7n@googlegroups.com>
2020-11-07 14:57 ` Oleg Finkelshteyn
2020-11-07 18:56 ` Sean Hinchee [this message]
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=CADmmOS9UgkmzwCB98djmnGvWCkN31+t6902LyTA6Zc0T8_+LTA@mail.gmail.com \
--to=henesy.dev@gmail.com \
--cc=9fans@9fans.net \
--cc=bhgv.empire@gmail.com \
--cc=inferno-os@googlegroups.com \
--cc=olegfink@gmail.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 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).