dhcpcd-discuss

    Hello all!

    (Just for the record I'm a very new member of this mailing list,
I've signed up today, so if what I'm asking was already discussed
please forgive me. I've skimmed through the archived emails (only the
subjects) and found nothing relevant about my problem.)

    (Skip this paragraph if in hurry.)
    My interest in using `dhcpcd` is to replace `dhclient` in my
custom made network management scripts:
    * I use the `runit` toolset to run most of my services (including
my network related services like interface (wired and wireless)
management and DNS resolver);
    * I want to statically link dhcpcd, and deploy it inside a chroot
(prepared with static linked busybox for dhcpcd scripts, or hand made
script);

    But the problem (actually an annoyance) is that `dhcpcd` has
hard-coded paths for most of its files (all except the config file).

    So my request for comments is on the following topics:

    * if I would make a patch which enhances the configurability of
the daemon by allowing to specify options either in the config file or
on the command line, would such a patch be welcomed in the "official"
code base? (evidently after thorough review :) ) (I would like to
invest time to make the patch, but I wouldn't want to keep applying it
for every new release... :) )

    * I've skimmed through the source code and the candidates for such
configuration options are found inside the `defs.h` header: CONFIG,
SCRIPT, DUID, LEASEFILE, PIDFILE, CONTROLSOCKET; are there other
hard-coded paths? (I've also found `/dev/urandom`, `/dev/null`, and
some `/proc`, but these are standard and wouldn't need to be changed;)

    * if I were to introduce configuration options for these does
anyone have a good opinion about how these would be named? for
example:
        --duid-file, --lease, --pid, --control (these are not used
according to the man page);

    So any opinions?