From: presotto@plan9.att.com presotto@plan9.att.com
Subject: name resolution
Date: Fri, 29 Sep 1995 10:21:22 -0400 [thread overview]
Message-ID: <19950929142122.P8QiAj6nG7dbf_moxgAbcO_zeyVtFEfjp96d8INPELI@z> (raw)
start ndb/dns in /bin/termrc
------ original message follows ------
>From cse.psu.edu!9fans-outgoing-owner Fri Sep 29 07:54:20 EDT 1995
Received: by colossus.cse.psu.edu id <78523>; Fri, 29 Sep 1995 07:41:59 -0400
Received: from lethe.leeds.ac.uk ([129.11.244.5]) by colossus.cse.psu.edu with SMTP id <78522>; Fri, 29 Sep 1995 07:41:43 -0400
Received: (from stephen@localhost) by lethe.leeds.ac.uk (8.6.12/8.6.9) id MAA00943 for 9fans@cse.psu.edu; Fri, 29 Sep 1995 12:41:56 GMT
Date: Fri, 29 Sep 1995 08:41:56 -0400
From: Stephen Gallimore <stephen@psyc.leeds.ac.uk>
Message-Id: <199509291241.MAA00943@lethe.leeds.ac.uk>
To: 9fans@cse.psu.edu
Subject: Re: name resolution
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
Jesse, you posted this last week sometime:
>I have edited and re-edited /lib/ndb/local and I can't figure out how to
>get hostname resolution working. This breaks things like mothra, which
>need to look up hostnames. All the other net stuff works fine, I can telnet
>and use ftpfs, as long as I know the IP address of the machine I want to
>connect to.
>
>Any advice ?
I have exactly the same problem but noticed that nobody responded to the
list. Have you had a personal reply from any of the guys at AT&T ? If
so could you mail me the solution (if there is one).
Thanks in advance,
stephen
next reply other threads:[~1995-09-29 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-29 14:21 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-09-29 17:33 Jesse
1995-09-29 12:41 Stephen
1995-09-26 1:52 Jesse
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=19950929142122.P8QiAj6nG7dbf_moxgAbcO_zeyVtFEfjp96d8INPELI@z \
--to=presotto@plan9.att.com \
/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).