From: "Russ Cox" <rsc@mit.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] shared memory
Date: Tue, 16 Sep 2003 00:23:00 -0400 [thread overview]
Message-ID: <21ff68b72cbb488c658c940b3300b958@plan9.bell-labs.com> (raw)
In-Reply-To: <500490e850e39f6bcca34fe83e4d221f@granite.cias.osakafu-u.ac.jp>
> Russ, have you revised the ghostscript to newest version?
no. i did update our internal copy to gs 8.00,
but that seemed to break more than it fixed.
they just released 8.11, "the first stable release
since 8.00", whatever that means. all i know
is that i can't view the intel architecture
manuals using 8.00. they're all shifted half
a page up off the screen.
i have not been impressed since peter deutsch
handed over the reins. there used to be a
mailing list for people interested in announcements
about new releases. we'd get a mail a month
saying "this just came out and fixes such-and-such."
there's no equivalent now, so i never know when
something is worth trying or not, and i haven't been
very aggressive in watching for new releases.
the instructions for pulling in new source
are in /sys/src/cmd/gs/mkfile. mk try-8.11
should do most of the work. you may need to
tweak it.
next prev parent reply other threads:[~2003-09-16 4:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 5:32 [9fans] g++ YAMANASHI Takeshi
2003-09-12 7:25 ` okamoto
2003-09-12 9:29 ` northern snowfall
2003-09-12 8:33 ` okamoto
2003-09-12 8:43 ` [9fans] shared memory okamoto
2003-09-12 8:48 ` Geoff Collyer
2003-09-12 8:52 ` okamoto
2003-09-12 9:25 ` Geoff Collyer
2003-09-12 9:30 ` Charles Forsyth
2003-09-12 15:33 ` splite
2003-09-12 16:11 ` boyd, rounin
2003-09-12 12:12 ` David Presotto
2003-09-16 3:07 ` okamoto
2003-09-15 13:30 ` okamoto
2003-09-16 4:23 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-29 11:13 paurea
2002-07-29 13:56 ` Ronald G Minnich
2002-07-29 13:59 ` Ronald G Minnich
2002-07-31 12:52 ` andrey mirtchovski
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=21ff68b72cbb488c658c940b3300b958@plan9.bell-labs.com \
--to=rsc@mit.edu \
--cc=9fans@cse.psu.edu \
/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).