defining the available (network) device hardware types

Jason Schoon floydpink at gmail.com
Mon Apr 10 18:12:01 UTC 2006


On 4/10/06, Rob Landley <rob at landley.net> wrote:
>
> On Monday 10 April 2006 8:48 am, Robert P. J. Day wrote:
> >   sort of related to the ongoing discussion of what should and should
> > not be supported in terms of networking functionality, at the top of
> > networking/interface.c, you see the hardcoding of things like protocol
> > families and device types:
> ...
> >   now, regardless of whether or not you want to support IPX, or X.25,
> > or PPP, or SLIP (oh, barf), shouldn't all of this stuff be selectable
> > options during the configuration?  as an extreme example, you have to
> > scroll down to line 1530 of interface.c to realize that there's a
> > macro which (apparently) relates to token ring support:
> ...
> >   in any event, i imagine a good cleaning would resolve most of these
> > issues.
>
> I lean towards just removing anything that we've never been able to
> select,
> and adding it back (as a config option) if anybody actually _needs_ it.
>
> > rday
>
> Rob
>

I would second that.  To me, configs that we don't currently control are not
much different than an #if 0.  They don't serve much more than a comment at
this point, and probably not even that.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20060410/77259405/attachment-0001.htm 


More information about the busybox mailing list