On 17/06/2010 14:03, Simon Kelley wrote:
I still bear the scars from an email I once got from someone who had
driven 200 miles to reboot a box which had dropped off the net as a
result of an automatic update to dhcpcd.
I'm not really seeing how that is relevant to the topic at hand as that
scenario could equally apply to any package.
If anyone has the blame, it's the user for allowing a critical piece of
software to be remotely upgraded and not validated locally first.
After careful perusal of the interfaces man page (still can't find the
source for ifup to ensure I'm correct), the only options passed to
dhcpcd are -h $hostname -i $vendor -I $client -l $leasetime
These options still exist and are valid.
Good, but what about<interfacename> which is also passed?
That also works.
I've also solved the init script vs network/interfaces issue by
grepping for iface * inet dhcp and aborting if such a match is found.
Aborting installation, or start-up. The best approach is to have a
dhcpcd5 package which can be installed and configured at leisure (see
above for more details)
It aborts at startup.
So, on a virgin system with dhcpd5 installed, dhcpcd will automatically
start and Do The Right Thing.
On a system already configured for DHCP via /etc/network/interfaces,
dhcpcd will not start (via /etc/init.d/dhcpcd start).
I can understand that the biggest problem with making the set of files
in dhcpcd3 and dhcpcd5 disjoint is the man page: much better to be able
to type "man dhcpcd" rather then "man dhcpcd5". This is achievable by
using Debian's "alternatives" system. It would need a new version of
dhcpcd3, but that's quite possible.
I've uploaded a new package to mentors.debian.net that uses the
alternatives system.
However, I now get these errors from lintian
E: dhcpcd5: init.d-script-missing-dependency-on-remote_fs
/etc/init.d/dhcpcd: required-start
E: dhcpcd5: init.d-script-missing-dependency-on-remote_fs
/etc/init.d/dhcpcd: required-stop
I've tried adding a dhcpcd-5.lintian-overrides file, but it doesn't seem
to work. Any help would be nice here :)
The issue is this - the ntp helper script will restart ntp via
invoke-rc.d and as such /usr is required in $PATH. Now, invoke-rc.d is
*optional* and it's lack of presence won't affect a Debian system with
/usr nfs mounted from working correctly.
Any pointers on fixing this lintian issue are welcome :)
Aside from that, I think I've addressed all issues so the only thing
left is to make dhcpcd-3 alternatives friendly which I assume you will do?
Thanks
Roy
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
