From: Kevin McQuiggin mcquiggi@sfu.ca
Subject: [9fans] Thanks, ip almost working!
Date: Wed, 22 Apr 1998 18:07:19 -0700 [thread overview]
Message-ID: <19980423010719.CZO7_3gWc3enPOKuYeslbr9NQI8CDl5uB_UKa5DDssQ@z> (raw)
At 02:08 AM 98/04/22 -0400, you wrote:
>What happened to Plan A? Surely that comes between Plan 9 and Plan B, no?
In hex I suppose you're right. "Plan A" was the atapi CDROM, no luck, so
time for "Plan B".
Reminds me of that big DX-pedition by longtime contester RG8U to the
Coaxial Islands in 1979... (I worked him on the standing wave). :-)
Hmmm, any ham radio types on this list??? (If not I suppose I've just
lobbed a lead balloon...)
>The problem, I think, is that once you set the ip information, you
>can't set it again. Once you tell it your ethernet card is 255.255.255.0
>(probably in termrc?) you're doomed..
I looked through but may have missed this. I'll take another look tonight.
Kevin
---
Kevin McQuiggin VE7ZD
mcquiggi@sfu.ca
next reply other threads:[~1998-04-23 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-23 1:07 Kevin [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-04-25 18:31 Photon
1998-04-25 18:22 Douglas
1998-04-22 6:08 Russ
1998-04-22 2:05 Kevin
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=19980423010719.CZO7_3gWc3enPOKuYeslbr9NQI8CDl5uB_UKa5DDssQ@z \
--to=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).