From: Andrew Lynch lynch@ccigate.cci.de
Subject: porting linux programs and drivers to plan9
Date: Fri, 18 Apr 1997 10:50:28 +0100 [thread overview]
Message-ID: <19970418095028.aZyBufm-XXci7dZeqgLE7oiZif2XiOYqPKyU4EvhaHQ@z> (raw)
> > I see many people share your views on unix software. Without digressing
> > into a unix vs. plan9 spam match, if sam is to plan9 as ed is to unix
> > then what would be the emacs of plan9? (I'm sorry Mr. Pike but I can't
> > believe anyone could write code in sam as fast as in emacs.)
>
> If you want something which can sing and dance and ...
> then try 'acme'.
Indeed. Also Plan 9 has an ed, so the original statement ought to
have read:
if ed is to plan9 as ed is to unix then the emacs of plan9 is acme
;-)
Now if only I could run acme on my Sun3/60 and 3/50s... Has anyone
considered an alef "port" for the 68020? I'm thinking it should not
be too difficult looking at eg. the 386 and 68020 C compilers and the
386 alef compiler.
(yeah, I know the easy way out - run acme on a 386 cpu server, but
it's not the same ;-)
Regarding some of the other mails (students etc.):
I graduated at York last July, where I came to like Plan 9. Just
before Easter I bought myself the CD distribution for approx.
DM 600.-. Yes, it hurt, but something like Windows NT Workstation
costs the same here (DM 500-600) and Plan 9 is infinitely more
interesting. It also runs fine on "old" hardware, such as 2nd hand
386 or 486 machines. So you can probably set up a whole Plan9 network
with file server, cpu server etc. for less than a decent Pentium.
Andrew.
next reply other threads:[~1997-04-18 9:50 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-18 9:50 Andrew [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-04-21 20:59 miller
1997-04-21 16:27 Eric
1997-04-21 14:53 Milon
1997-04-21 12:50 miller
1997-04-21 11:29 Nigel
1997-04-21 8:05 Boyd
1997-04-21 7:16 chad
1997-04-21 3:36 presotto
1997-04-21 1:03 David
1997-04-20 16:12 miller
1997-04-19 16:49 Magnus
1997-04-19 10:22 Digby
1997-04-19 4:59 chad
1997-04-19 4:09 ozan
1997-04-19 3:52 Berry
1997-04-19 1:51 David
1997-04-19 0:56 Rich
1997-04-19 0:41 Rich
1997-04-18 21:19 Paul
1997-04-18 21:01 Digby
1997-04-18 20:47 Digby
1997-04-18 16:39 presotto
1997-04-18 16:10 Eric
1997-04-18 16:07 Eric
1997-04-18 15:57 Eric
1997-04-18 15:51 Eric
1997-04-18 15:37 Dean
1997-04-18 15:14 forsyth
1997-04-18 13:54 Brandon
1997-04-18 8:10 Digby
1997-04-18 8:04 Digby
1997-04-18 7:58 Steve_Kilbane
1997-04-18 7:52 Steve_Kilbane
1997-04-18 7:15 Nigel
1997-04-18 5:57 Nickolay
1997-04-18 5:49 Brandon
1997-04-18 4:59 jmk
1997-04-18 3:15 Steve
1997-04-18 0:33 Pete
1997-04-17 23:43 Eric
1997-04-17 23:19 Eric
1997-04-17 21:55 Eric
1997-04-17 21:46 Rich
1997-04-17 21:45 Rich
1997-04-17 18:43 Eric
1997-04-17 18:17 forsyth
1997-04-17 18:13 forsyth
1997-04-17 17:59 Bodet
1997-04-17 17:07 Pete
1997-04-17 16:33 Rich
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=19970418095028.aZyBufm-XXci7dZeqgLE7oiZif2XiOYqPKyU4EvhaHQ@z \
--to=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).