From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ghostscript not finding LucidaSans
Date: Mon, 28 Jun 2010 13:21:14 +0100 [thread overview]
Message-ID: <85132854-E0CF-4218-8B80-2B7A461C34D4@fastmail.fm> (raw)
In-Reply-To: <6BC07976-E754-4857-A276-2ABD1717AB82@mac.com>
On 28 Jun 2010, at 04:18, Pietro Gagliardi wrote:
> I'm not sure if this has to do with 9vx... in fact I'm not sure
> exactly what's causing these things to behave as they are now.
I have the same problem with postscript, and wonder if something went
wrong in getting the files from Plan 9 to make a 9vx tree. I ran a
single Plan 9 instance in Qemu for a few years; no trouble with
postscript then. I copied the tree out from the live running system
using tar and dial[*] on the plan 9 side; tar and netcat on the unix,
and used that tree with no further modification as a root for 9vx.
Postscript now fails with the error Pietro gave.
[*] dial as in p9p / inferno's dial command. I renamed the binary to
dialout to avoid conflict with /bin/dial/
prev parent reply other threads:[~2010-06-28 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 1:07 Pietro Gagliardi
2010-06-28 1:56 ` erik quanstrom
2010-06-28 3:18 ` Pietro Gagliardi
2010-06-28 4:40 ` erik quanstrom
2010-06-28 6:24 ` Pietro Gagliardi
2010-06-28 6:36 ` Pietro Gagliardi
2010-06-28 13:09 ` erik quanstrom
2010-06-28 14:23 ` Pietro Gagliardi
2010-06-28 15:04 ` ron minnich
2010-06-28 18:05 ` [9fans] problems with tracing 9vx on os x (was: " Pietro Gagliardi
2010-06-29 8:03 ` yy
2010-06-29 14:31 ` Pietro Gagliardi
2010-06-28 12:21 ` Ethan Grammatikidis [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=85132854-E0CF-4218-8B80-2B7A461C34D4@fastmail.fm \
--to=eekee57@fastmail.fm \
--cc=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).