From: "Tiit Lankots" <t.lankots@aprote.ee>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] cs & sysname
Date: Tue, 25 Nov 2003 15:31:15 +0200 [thread overview]
Message-ID: <81132473206F3A46A72BD6116E1A06AE479CB4@black.aprote.com> (raw)
> Also, you could have avoided the problem by setting up a real ip
> address before running cs since it preferentially chose such an
> address.
Yes, but then it chose that ip as my sysname, becasuse it looked
either by ip or alternatively by ether, if ip didn't produce anything.
Case 1).
Tiit
next reply other threads:[~2003-11-25 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 13:31 Tiit Lankots [this message]
2003-11-25 13:42 ` David Presotto
-- strict thread matches above, loose matches on Subject: below --
2003-11-25 13:45 Tiit Lankots
2003-11-25 12:37 Tiit Lankots
2003-11-25 13:08 ` David Presotto
2003-11-25 13:26 ` David Presotto
2003-11-25 16:21 ` Rob Pike
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=81132473206F3A46A72BD6116E1A06AE479CB4@black.aprote.com \
--to=t.lankots@aprote.ee \
--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).