9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ghostscript not finding LucidaSans
Date: Mon, 28 Jun 2010 09:09:41 -0400	[thread overview]
Message-ID: <74e247fcae1592ffccf14609359ce650@kw.quanstro.net> (raw)
In-Reply-To: <035D301A-3041-45E9-B424-FCA176E4D008@mac.com>

On Mon Jun 28 02:37:21 EDT 2010, pietro10@mac.com wrote:
> Actually, on further investigation it turns out while dircp /n/sources/
> plan9/sys/lib/postscript dir works fine, diff -r dir /n/sources/plan9/
> sys/lib/postscript gives me the same diff log, and diff -r dir olddir
> tells me they're identical. So what's going on here...

the difference that i can think of is #Z.  #Z doesn't do
locks, exclusive access, etc.  why don't you try binding a ramfs
/tmp on lp's temp directory, /sys/lib/lp/tmp.  if that's not
it, the bind/mount list you used to get things working from
sources should give you more directories to investigate.

- erik



  reply	other threads:[~2010-06-28 13:09 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 [this message]
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=74e247fcae1592ffccf14609359ce650@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).