Re: hotplug & PCMCIA schemes

[David Brownell <david-b@pacbell.net>]

From: <shivers@cc.gatech.edu>

> This all works fine under Hinds' standard pcmcia system -- I just use
> different "schemes" -- "home," "GT," "boston," "GT-static," etc. -- to
> determine DHCP or the static IP address, the proper encryption key, any
> funky-nonstandard options and so forth. But I see no way to do this under the
> hotplug system. 

Not the standard distro, but I believe all the necessary ingredients
are there.


>    The /etc/hotplug/net.agent script will invoke
> /etc/pcmcia/wireless if I use a wireless card, but it *won't* invoke
> /etc/pcmcia/network with a wireline network card. So it's scheme-insensitive
> in the wireline case.
> 
> The short summary here is that notebook users hook up to lots of different
> networks, depending (among other things) on location, as they cart their
> machines around. All the hotplug agent sees is "eth0". That's not enough.

The hotplug agent sees the whole filesystem, too.  Whatever tells
PCMCIA that the current "scheme" is "GT", for example, should
be accessible to hotplug agents too.


> Hind's system handles this by providing an extra user-configurable key
> in the form of the "scheme." How does one do this in hotplug?

Well, one could always submit a patch to teach hotplug that such
different schemes exist.  That facility isn't restricted to networking,
is it?  Seems to me that different kinds of docking setup would need
it for more than just network devices.

Alternatively, I think the RedHat scripts used by "ifup" are also
places that such behaviors can be hooked.

-  Dave




_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel