From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] wavelan bug?
Date: Wed, 29 May 2002 17:34:59 +0200 [thread overview]
Message-ID: <6c48a61597c3ea4d70e37b67fc63c051@plan9.escet.urjc.es> (raw)
Hi,
I found that option processing in etherwavelan.c makes it
necessary to scape white space twice when setting network and station
names through plan9.ini. For example:
ether0=wave essid='''net name with spaces'''
I think this is a bug since an equivalent write in the ctl file would be
just "essid 'net name with spaces'\0". I mean, AFAIK, I think
ether0=wave essid='net name with spaces'
is the way to scape white space in plan9.ini options.
I think the fix would be to avoid the call to tokenize when processing already
processed isa config options, but I don't have the time right now to do this.
I send this mail mainly to document the bug and to remember me that this is
pending work.
hth
reply other threads:[~2002-05-29 15:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6c48a61597c3ea4d70e37b67fc63c051@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).