From: "Conor Williams" <connorwilliamsie@aol.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] telnet problem
Date: Thu, 13 Feb 2003 09:07:37 +0000 [thread overview]
Message-ID: <064401c2d33f$5ab5a7d0$4d4a800a@will551> (raw)
In-Reply-To: <2c9e36c062108fc848979b7b781af627@plan9.bell-labs.com>
thanks Russ
got the problem fixed which was easily spotted
after running debug - I was missing a dom=home.net
line so I put it on the same line as the auth and authdom
line at the bottom...
one thing - that url is a link to the binary not the gziped binary!
so a
mv debug.gz debug
did the trick
got my printer setup the other day. a:
bind -a '#'L2 /dev
found the right parallel port configuration
and I changed the devices file to
include a gs!laserjet line and set the spooler
to nospool - that transparent gs incorporation is
very powerful - I can now print postscript with
lp.
l8r
Conor
----- Original Message -----
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: <9fans@cse.psu.edu>
Sent: Tuesday, February 11, 2003 1:03 PM
Subject: Re: [9fans] telnet problem
> Your /lib/ndb/local file looks okay. I'm not sure
> exactly what's wrong. You really need to run
> auth/debug on the auth server.
>
> hget http://pdos.lcs.mit.edu/~rsc/debug.gz |gunzip >/bin/auth/debug
> auth/debug
>
> Russ
>
>
next prev parent reply other threads:[~2003-02-13 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 20:14 [9fans] Booting plan9 OS Nicolas Couture
2003-01-25 19:21 ` Russ Cox
2003-01-25 20:36 ` Nicolas Couture
2003-01-25 19:44 ` Russ Cox
2003-01-25 19:53 ` Russ Cox
2003-01-25 20:56 ` Nicolas Couture
2003-02-10 9:33 ` [9fans] telnet problem Conor Williams
2003-02-10 11:59 ` Russ Cox
2003-02-11 10:15 ` Conor Williams
2003-02-11 13:03 ` Russ Cox
2003-02-13 9:07 ` Conor Williams [this message]
2003-01-25 20:48 ` [9fans] Booting plan9 OS Nicolas Couture
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='064401c2d33f$5ab5a7d0$4d4a800a@will551' \
--to=connorwilliamsie@aol.com \
--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).