> To get the appropriate hotplug behavior, do I need to get dhcpcd in
> the background somehow, or do I need to change certain values in the
> bootscripts, or do I need a separate program (such as d-bus or HAL or
> something)?
There's a couple of make targets in the udev rules package that aren't
really well known.
make install-network is one of them. I think this is what you're looking
for. It modifies the existing network bootscript to only stop and starts
network devices as udev finds them. ONHOTPLUG=yes needs to be present in
ifconfig.[device]/[service].
Well I've obviously put off fixing this problem for quite a while
considering the last post in this thread. In any case, if I use the
network script from udev-rules, it always exits with an error status
of 1 on boot. And on shutdown, it complains that the interfaces
listedin /sys/class/net/ aren't interfaces. The second problem is
probably partially due to the fact that I gave my network interface a
name other than eth0, but changing it to eth0 doesn't make the first
problem go away, which is the big one (I haven't checked to see
whether the problem on shutdown goes away with my network interface
named eth0).
I tried altering the network script by replacing its stop function
with the one from clfs-bootscripts, but that doesn't fix the boot
problem. Unsurprisingly however, it DOES fix the problem on shutdown.
My guess at the moment is that the network script is being called
with "start" and since start isn't there, it exits with error code 1.
I set ONHOTPLUG="yes" and ONBOOT="no", so I'm not quite sure why start
would be called on the network script on boot. Perhaps if the
ethernet cable were plugged in, hotplug would end up resulting in
start being called, but the failure happens regardless of whether the
cable is plugged in or not. I would have thought that ONBOOT="no"
would have stopped that.
In any case, any ideas as to what I'm missing here would be
appreciated. At the moment, it just seems like the udev-rules network
script doesn't work since it lacks the start function. And if the
lack of start function is what allows it to use hotplug, then there's
a conflict here somewhere.
- Jonathan M Davis
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
