On Thu, 2005-05-26 at 15:04 +0200, Kevin F. Quinn wrote:
> 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.
> 
> 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!
> 


emerge ifplugd and get that to monitor your interfaces. It will bring
them up/down when a cable is inserted/removed.
You'll probably have to tell it to not fail if the interfaces don't
exist as you're using udev to rename them.

A better solution would be to allow configuration via MAC address, which
we may put into baselayout-1.12.0

> 
> 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?
> 
> 
> 

Try experimenting with the RC_STRICT_NET_CHECKING in /etc/conf.d/rc

-- 
Roy Marples <[EMAIL PROTECTED]>
Gentoo Linux Developer

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to