Re: OT(?) -- Should the net.agent script cause "ifup lo" to be run?

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

> > I think the plan of record for 2.4 is to make hotplug handle cardbus
> > and pcmcia_cs/cardmgr handle pcmcia.  If anyone thinks it's
> > something else, please speak up!
> 
> That's rather ugly (cardmgr will still print messages for everything
> that's inserted), 

Noise in /var/log/messages that will normally be ignored.
(If it's a problem, wouldn't it be a cardmgr problem?)


>    inconsistent in UI (cardmgr beeps, etc., hotplug
> doesn't), 

If there are only two possible devices, and you're in an
environment where the noise is OK, beeps are unlikely
to be annoying.  Even two at boot time.

Systems with a dozen USB devices are not uncommon;
I'd rather rely on hub LEDs for feedback than get lots of
noise on reboot, or when I plug in a hub that has a bunch
of devices already connected.

Though if you really think that CardBus hotplugging should
beep, that should be an easy patch ... cPCI evidently uses
blue lights in its feedback (doesn't Compaq's Hotplug PCI
use LEDs too?), so that shouldn't be a PCI-wide policy.


>    and just generally odd from an end-user's perspective
> (You see, if you plug *that* card into the slot, you need cardmgr
> running; if you plug that other card in, you need hotplug.)

"Have both these installed and any supported card will work"
doesn't seem odd!  Quite the opposite.


> It's actually not too hard to make cardmgr work fine with 2.4.

Never said it was.  The question is how to handle cardbus
support, given that pcmcia_cs (with cardmgr) is oriented
towards pcmcia while the overall Linux direction seems to
be to towards a more general framework for pci hotplug.

- Dave


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