9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] troff problem
Date: Fri, 21 Nov 2003 14:49:29 +0100	[thread overview]
Message-ID: <f4430c7983bada8599cfd8dddcf3686c@plan9.escet.urjc.es> (raw)
In-Reply-To: <868ym9519a.fsf@gic.mteege.de>

[-- Attachment #1: Type: text/plain, Size: 72 bytes --]

Yep. You'd better edit /sys/lib/bin/lpscratch to avoid mounting other.

[-- Attachment #2: Type: message/rfc822, Size: 2887 bytes --]

From: Matthias Teege <matthias-9fans@mteege.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] troff problem
Date: Fri, 21 Nov 2003 13:55:39 +0100
Message-ID: <868ym9519a.fsf@gic.mteege.de>

Fco.J.Ballesteros <nemo@plan9.escet.urjc.es> writes:

> setup your fileserver environment variable
> so that 9fs $fileserver could mount it.
> lp will try to mount it and it seems that
> 9fs kfs does not work for you (using fossil?)

I use a old style fileserver. I set $fileserver to the name of my
fileserver and try the following:

term% mntgen
term% 9fs $fileserver
term% troff -ms hello.ms | lp -dstdout > hello.ps
mount: mount /n/batidaother: attach -- unknown user or failed authentication
cannot mount /n/batidaother filesystem
term%

Hmm, there must be another problem to.

Thanks
Matthias

--
Matthias Teege -- http://www.mteege.de
make world not war

  parent reply	other threads:[~2003-11-21 13:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21  8:17 Matthias Teege
2003-11-21  9:59 ` Fco.J.Ballesteros
2003-11-21 12:55   ` Matthias Teege
2003-11-21 13:43     ` Axel Belinfante
2003-11-21 14:04       ` Sape Mullender
2003-11-21 15:40         ` mirtchov
2003-11-21 17:34         ` Matthias Teege
2003-11-21 18:25           ` Sape Mullender
2003-11-21 13:49     ` Fco.J.Ballesteros [this message]
2003-11-21  8:23 cej
2003-11-21  8:28 ` Geoff Collyer
2003-11-21  9:44   ` Skip Tavakkolian
2003-11-21  8:48     ` Geoff Collyer
2003-11-21  8:59       ` Charles Forsyth
2003-11-21 12:56     ` Matthias Teege
2003-11-21  8:33 cej
2003-11-21  8:41 ` Geoff Collyer
2003-11-21  9:02 cej

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=f4430c7983bada8599cfd8dddcf3686c@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --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).