| 1 |
On 26/5/2005 0:20:02, Mike Frysinger (vapier@g.o) wrote: |
| 2 |
> files - the net scripts have been completely rewritten thanks to UberLord |
| 3 |
|
| 4 |
Ahh; what fun - that was the stuff I'd tweaked the most :/ |
| 5 |
The new network stuff is much better, but I do have one hiccough. |
| 6 |
|
| 7 |
I'm trying it on a laptop that connects to various different networks depending on the weather. I figured this would be a useful test as it's a less common configuration. It connects mostly via different docking stations. I use udev to rename ethernet devices according to MAC address (the ethernet devices are in the docking stations). Hotplug then runs the appropriately named network script via net.agent to start the service. Critically, the various net.* scripts are therefore -not- in any runlevel. |
| 8 |
|
| 9 |
This hotplugging of the network devices all kicks off early on - well before the boot level has finished. The new /sbin/runscript.sh simply drops the addition of the network device if the boot level hasn't finished - leaving me with no network (or at least, a network that has to be started manually). For now, I've commented out the check in /sbin/runscript.sh, and it all works ok. I don't know what this will break; obviously the check wasn't added just for laughs! |
| 10 |
|
| 11 |
|
| 12 |
On a somewhat related matter, I have bluetooth stuff installed, which is also started by hotplug/pcmcia. In order to prevent it being stopped by changing runlevels, I've made a softlink to net.bluetooth and started that in my hotplug config instead of 'bluetooth'. Bit of a hack, relying on the fact /sbin/rc does not automatically stop anything that begins with "net.". Is there a tidier way to prevent /sbin/rc from messing with services started & stopped via hotplug? |
| 13 |
|
| 14 |
|
| 15 |
|
| 16 |
-- |
| 17 |
gentoo-dev@g.o mailing list |
Archives