breaking DHCP configuration into two parts?

Robert P. J. Day rpjday at mindspring.com
Mon Apr 17 19:36:28 UTC 2006


  i'm just pondering a possibility for restructuring how some
selections might be configured, and i'm quite willing to have this
idea rejected violently.  i'm just thinking out loud, that's all.

  what about breaking "udhcp" configuration into two parts -- client
versus server?  once upon a time, i suggested the idea of perhaps
collecting all of the networking *server* applets into one place, just
for convenience.  a lot of people just mentally find it easier to
concentrate on all of the server-related at one time, rather than have
it scattered throughout the networking config menu.

  as a simple first attempt, it wouldn't be hard to just throw in a
comment line in the networking config menu labelled "Servers", under
which you could collect all of your servers (dnsd, httpd, telnetd,
...).  this would be trivially easy, *except* for udhcp.

  the problem with udhcp is that, because it's "sourced" separately
from Config.in, it's all or nothing:

  source networking/udhcp/Config.in

this, of course, makes it impossible to have the udhcpc (client)
config entry at one location in the menu, and the udhcpd (server)
entry elsewhere, which someone might want.  but this is easy to fix.

  if the entire udhcp software is maintained independently, its
maintainer should take into account that some people might just want
to separate those two parts when sourcing them, and provide *two*
Config.in files -- Config.in.udhcpc and Config.in.udhcpd.  that way,
developers have the freedom to pull in those two files independently,
or even omit one or the other if they feel like it.

  note that this isn't meant to be something you'd do on a regular
basis, but it would seem to make sense for something like udhcp that:

  1) is maintained independently from busybox, and
  2) really has two sizable and fundamentally different functions
	it's providing to the developer.

in special cases like that, it may not be unreasonable to logically
separate it into two independently-selectable parts, just in case.

rday



More information about the busybox mailing list