dhcpcd-discuss

On Thu, Apr 29, 2010 at 11:59, Roy Marples <roy@xxxxxxxxxxxx> wrote:
> On 29/04/2010 09:01, Ciprian Dorin, Craciun wrote:
>>      But the problem (actually an annoyance) is that `dhcpcd` has
>> hard-coded paths for most of its files (all except the config file).
>
> You can tailor the paths at compile time.

    Agree, but this doesn't allow the administrator to "customize" the
run-time without re-compiling the package by hand. (See also at the
end more comments about this.)


> I don't want to support any runtime path changes.

    Fair enough. I'll stop here with this proposal.


>>          --duid-file, --lease, --pid, --control
>
> The pid and control files should not be user changeable as programs/scripts
> external to dhcpcd use them as well.

    I proposed to customize only the binary executable, but keeping as
fallbacks the current "hard-coded" values (those configured at compile
time).


> So, that begs the question, why would a user wish to change the duid and
> lease file locations outside of the system default?
>
> Thanks
>
> Roy


    Why I need to change the default paths?

    Well (as I've noted previously) I would like to be able to use the
binary package that comes with the distribution (which is dynamically
linked, but with not too many dependencies), and just put it inside a
chroot with a "relaxed" file system layout. I know I could just copy
the binary and recreate the `/lib`, `/var`, and `/etc` just with the
needed files, but as I only need this for a couple of files, it would
be much more easy for maintenance, to throw all the needed files into
two folders `/bin` and `/data` (inside the chroot), and instruct the
`dhcpd` daemon to use the `/data` folder for everything (configuration
files, lease database, pid, etc.).

    So thanks again for your time,
    Ciprian.