>however after some deliberation I came to a conclusion
>that dhcpcd client operating through kernel IP layer
>is not the best idea.
>So in this respect Alan Cox was right.
>Dhcpcd must generate ethernet frames itself
And Token-Ring frames, and whatever frametypes you might
imagine using DHCP with ? I'm sorry, but I don't understand
why a DHCP client needs to know about all sorts of underlying
network frames, when there is a perfectly capable network
stack that already has all of the necessary code.
-- Henrik Storner