From: Digby Tarvin digbyt@acm.org
Subject: porting linux programs and drivers to plan9
Date: Fri, 18 Apr 1997 09:04:57 +0100 [thread overview]
Message-ID: <19970418080457.dm8CeNd5DlcZh6VqwenpJPSlu0BhhVwBduandss_fKo@z> (raw)
>
>For others who don't have endless computers kicking around, if the
>pcdist had a free pppclient, a large documentation library, and a
>commonly recognized editor (can we agree on microemacs?) plan 9 would
>not be as much of a shock to new users.
My vote is for Microemacs. It may not be as good as what Plan9
has to offer, but until versions of a Plan9 editor is available for Unix,
OS-9000, OS-9/68K, DOS (just for editting plan9.ini of course..),
VMS, etc.... and every other system I have to use, Microemacs seems the
best candidate for a 'Universal' editor. Vi would be an alternative I could
live with, but having to use 'ed' when using Plan9 for the first time
was a bit tiresome.
My other requirement for making Plan9 a viable replacement for my
'workhorse' system is the ability to run X clients (so I can use
Plan9 from the X-Terminal on my desk..I don't like having to sit next
to a whirring disk drive in order to get graphics) and an X server
so my Plan9 laptop can be used as for remote access of foreign
systems.
I have seen reference to a '9x' which sounds like it would fulfill my
first desire, but have not been able to locate it. Any pointers?
I have also seen an X server demonstrated on Plan9 in one of
Rob Pike's presentations some years ago. However I have not
seen any mention of this in the FAQ or archives. Anyone
know anything about this?
As far as the floppy distribution goes, I think manuals would
be a bit of an extravagence for a 'minimal' system.
Regards,
DigbyT
--
Digby R. S. Tarvin digbyt@acm.org
http://www.users.dircon.co.uk/~cthulhu/
next reply other threads:[~1997-04-18 8:04 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-18 8:04 Digby [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 9:50 Andrew
1997-04-18 8:10 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=19970418080457.dm8CeNd5DlcZh6VqwenpJPSlu0BhhVwBduandss_fKo@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).