From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ghostscript not finding LucidaSans
Date: Sun, 27 Jun 2010 21:56:08 -0400 [thread overview]
Message-ID: <7df666a5444b21740cc03ee17da0bfd4@kw.quanstro.net> (raw)
In-Reply-To: <731ED516-1A13-4296-BE0C-2C18D7D62532@mac.com>
> Ghostscript Error:
> postnote 404: sys: write on closed pipe pc=0x0001f8fc
> Fontmap entry for LucidaSans ends prematurely! Giving up.
>
> I don't understand what's going on here but as far as I can tell /sys/
> lib/postscript/fonts/LucidaSans has never existed in the Plan 9
> directory tree (checking sourcesdump) and my old VM works fine without
> it. Anyone know what's going on here? Thanks.
no, it never did.
; find /sys/lib|grep 'LucidaSans$'
/sys/lib/postscript/troff/LucidaSans
/sys/lib/troff/font/devutf/LucidaSans
i can't reproduce your results:
ladd; bind -b /n/sources/plan9/386/bin /bin
ladd; bind -b /n/sources/plan9/rc/bin /bin
ladd; bind /n/sources/plan9/lib /lib
ladd; bind /n/sources/plan9/sys /sys
ladd; ramfs
ladd; mkdir /tmp/x
ladd; bind /tmp/x /sys/lib/lp/log
ladd; touch /tmp/x/stdout; chmod +a /tmp/x/stdout
ladd; echo hello | troff | page
- erik
next prev parent reply other threads:[~2010-06-28 1:56 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 [this message]
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 ` [9fans] " Ethan Grammatikidis
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=7df666a5444b21740cc03ee17da0bfd4@kw.quanstro.net \
--to=quanstro@quanstro.net \
--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).