From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <85132854-E0CF-4218-8B80-2B7A461C34D4@fastmail.fm>
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-Reply-To: <6BC07976-E754-4857-A276-2ABD1717AB82@mac.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 28 Jun 2010 13:21:14 +0100
References: <731ED516-1A13-4296-BE0C-2C18D7D62532@mac.com>
	<7df666a5444b21740cc03ee17da0bfd4@kw.quanstro.net>
	<6BC07976-E754-4857-A276-2ABD1717AB82@mac.com>
Subject: Re: [9fans] ghostscript not finding LucidaSans
Topicbox-Message-UUID: 37953858-ead6-11e9-9d60-3106f5b1d025


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/