From: Jeff Sickel <jas@spamisham.corpus-callosum.com>
To: 9fans@cse.psu.edu
Subject: [9fans] 802.11b oddities
Date: Tue, 10 Feb 2004 09:36:43 +0000 [thread overview]
Message-ID: <102h10mso8o2a6c@corp.supernews.com> (raw)
I've been using Plan 9 on my laptop for quite some time now (never even
booted the XP that came with it... unfortunately, neither IBM nor M$ will
reimburse me for the XP license I wouldn't sign or use). From the very
first boot, I'd set up the plan9.ini file to have multiple configs to help
choose which network I would be using.
Everything was fine until someone nearby added another 802.11b network.
Now, even though my plan9.ini sets essid=string to my network name, the
other network now takes precidence and ends up messing up my net settings.
Luckily an echo 'essid string' > /net/ether0/0/ctl fixes the problem.
Is there a way to properly force the 802.11b network choice outside of
explicitely setting it in termrc?
jas
---
remove spamisham.
next reply other threads:[~2004-02-10 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 9:36 Jeff Sickel [this message]
2004-02-10 13:58 ` andrey mirtchovski
2004-02-10 15:25 ` David Presotto
2004-02-12 10:01 ` Jeff Sickel
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=102h10mso8o2a6c@corp.supernews.com \
--to=jas@spamisham.corpus-callosum.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).