sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: "James A. Robinson" <Jim.Robinson@Stanford.Edu>
To: "Chaotrope" <>
Subject: Re: 9term under Linux?
Date: Mon, 1 Feb 1999 21:01:28 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: Message from "Chaotrope" <>  of "Mon, 01 Feb 1999 16:25:45 PST."References: <>  <>

> 'editors' and  a 'TeX' directory. So I'm leaning toward BSD rather
> than Linux just because that indicates to me that these people are
> "thinking" along those lines.
> So my question is, e.g., Jim, what are you using? Is there a general
> consensus on ease of installation, whatever, getting this p9 'look and
> feel grafted on top of what version of Unix? Are there known problems
> with (obviously) RedHat vs. whatever?


I'm using a heavily modified, stripped down, and generally munged
version of RedHat 5.0 here at work. At home I'm running a customized
Slackware 3.0 setup.

I've got a /usr/local/src/plan9 tree on the home machine which has
the source for 9menu 1.4, 9wm 1.2, es 0.90beta1, sam 4.3, 9term 1.6.6,
rc 1.5b2, and wily 0.13.41.  I've fiddled with the various make files
and source so that they all compile without any problem on my box. As
I recall, 9term is the hardest to compile. 9wm, 9menu, the editors,
and the shells compiled without any trouble. 9term now compiles, but it
does tend to give off quite a few "seems to be harmless" errors.

Oh yeah, all the little tools that wily comes with were a pain in the
ass to compile.  But I got win, and tools/shell/* to compile. So, if
people want to download entire 1.0 meg binaries and 2.9 meg source tree,
grab it from

The only thing missing from the tars are the Xg unicode fonts. It doesn't
have a clear distribution-rights copyright statement, so I can't bundle
it in the archive.  I'm not even sure where I got them from originally,
so you'll have to hunt them up. =(

If you unarchive both from your root, they will go into

	/opt/plan9/^(bin doc lib man)

for the binaries, and

	/usr/local/src/plan9/^(9menu-1.4 9term-1.6.6 9wm-1.2 es-0.90beta1 rc-1.5b2 sam-4.3 wily-0.13.41)
for the source.


  reply	other threads:[~1999-02-02 20:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-02  0:25 Chaotrope
1999-02-02  2:01 ` James A. Robinson [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-02-03  7:19 Bengt Kleberg
1999-02-02 20:41 Chris Siebenmann
1999-02-02  6:49 Aharon Robbins
1999-01-28 12:28 Bengt Kleberg
1999-02-02 19:11 ` Mark H. Wilkinson
1999-01-28 11:33 Aharon Robbins
1999-01-28  7:45 Bengt Kleberg
1999-01-26 15:35 Aharon Robbins
1999-01-27 22:24 ` James A. Robinson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).