From: Roy Marples <uberlord@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Opinions Wanted - Arrays again :)
Date: Fri, 26 Oct 2007 11:42:46 +0100 [thread overview]
Message-ID: <1193395366.4312.14.camel@uberlaptop.marples.name> (raw)
In-Reply-To: <4721BE92.4070200@thefreemanclan.net>
On Fri, 2007-10-26 at 06:16 -0400, Richard Freeman wrote:
> If there is some problem with this suggestion feel free to shoot it full
> of holes, but how about something like:
>
> address_eth0="1.2.3.4"
> netmask_eth0="255.255.255.0"
> broadcast_eth0="1.2.3.255"
> gateway_eth0="1.2.3.1"
> network_eth0="1.2.3.0"
> hostname_eth0="mypc"
> options_eth0="bells and whistles"
How would you construct that if you wanted to add 5 addresses to the
interface?
> Without digging through the original source I'm not sure what everything
> else in that array is, but I think you get the picture. Instead of
> sticking all these parameters into a big array why not break them down
> into what they actually are used for? This should also make the code
> that actually reads back these variables a lot more readable - instead
> of wondering what the 5th field in the array is you would see something
> meaningful like "netmask".
We don't care what the actual options or values are, they are merely
passed to ifconfig. Basically we need the equivalent of doing this
ifconfig eth0 1.2.3.4 netmask 5.6.7.8 broadcast 1.2.3.4
ifconfig eth0 5.6.7.8 netmask 1.2.3.4 broadcast 5.6.7.8
ifconfig eth0 maybe some undocumented command
And we do this with a few other tools as well. Lets take a list of
preferred wireless AP's to connect to. How would you have that? As the
only invalid character in an SSID is a NULL (daft, but I didn't write
the specification)
Thanks
Roy
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-26 10:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 15:40 [gentoo-dev] Opinions Wanted - Arrays again :) Roy Marples
2007-10-25 16:02 ` Marijn Schouten (hkBst)
2007-10-25 16:18 ` Roy Marples
2007-10-25 16:37 ` Ioannis Aslanidis
2007-10-26 11:30 ` Roy Marples
2007-10-25 17:18 ` Josh Saddler
2007-10-25 21:31 ` Donnie Berkholz
2007-10-25 21:49 ` Roy Marples
2007-10-25 22:56 ` Donnie Berkholz
2007-10-26 6:28 ` Roy Marples
2007-10-26 10:16 ` Richard Freeman
2007-10-26 10:42 ` Roy Marples [this message]
2007-10-26 16:36 ` [gentoo-dev] " Duncan
2007-10-26 17:03 ` Roy Marples
2007-10-26 18:57 ` Duncan
2007-10-26 21:17 ` Roy Marples
2007-10-27 3:02 ` Richard Freeman
2007-10-28 6:46 ` [gentoo-dev] " Steve Long
2007-10-29 7:35 ` Natanael Copa
2007-10-30 3:55 ` [gentoo-dev] " Steve Long
2007-10-26 6:13 ` [gentoo-dev] " Alec Warner
2007-10-26 6:32 ` Roy Marples
2007-10-29 9:50 ` Roy Marples
2007-10-30 3:58 ` [gentoo-dev] " Steve Long
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=1193395366.4312.14.camel@uberlaptop.marples.name \
--to=uberlord@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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