On Sun, 29.09.02 21:44, Nicolas Boullis (nboullis@debian.org) wrote:
> > - It may beep on successful (or failed) interface configuration or
> > when the plug is pulled/connected
>
> Ideally, I would like this to be an option.
In fact, it is an option. (-b)
> > - Has a --ignore-fail mode which makes it compatible with PCMCIA
> > network drivers, which are not loaded all the time
>
> I don't understand what this option does/how you use it.
pcmcia network drivers are only loaded when a card is inserted. when
it is removed, the driver is removed as well. An example:
you want that the network interface of your pcmcia network card (eth0)
is only configured when it is inserted and attached to network. When
you boot the machine without the PCMCIA card inserted, miid starts up,
fails to find eth0, and quits. However if ifplugd is run with the -f
switch it treats "could not open eth0" as "no cable attached". Thus
everything works fine. In the moment the card is inserted and eth0
exists it starts to query the link beat normally.
Short: With -f supplied, ifplugd doesn't fail when it cannot open
eth0 but retries to open it constantly.
> > - And most important: it works. miid doesn't. At least on my
> > machine. First miid did not want to startup because the interface
> > wasn't up. This is somewhat a paradoxon, I think. After doing
> > "ifconfig eth0 up" by hand miid simply locked up my machine. After
> > rebooting I got miid working for 2 minutes, than my machine locked
> > up again. this simply doesn't occur with ifplugd. The need of
> > "ifconfig eth0 up" may be caused by some strangeness of the 8193too
> > driver I am using. However, ifplugd works around this
> > maybe-bug. miid is unusable on my machine, while ifplugd is.
>
> This looks very interesting to me, since I have a laptop with a
> RTL8139C-based builtin NIC, and miid does not work fine on this laptop.
> However, I consider this as a bug in the kernel 8139too module, not a bug
> in miid. But miid works on my other laptop.
> I will probably give ifplugd a try soon...
My card is not a 8139C, it is an older version. The driver 8139too
driver is for 8139, 8139A and 8139B chips, not for 8139c!
> While this may be true with your hardware, are you sure ifplugd works
> everywhere miid works?
ifplugd should work everywhere where miid works, since it falls back
to the same ioctls when the never ETHTOOL ioctls don't work.
I don't see why ifplugd shouldn't work on all the hardware miid
does. In contrary, I believe it works on much broader quantity of
machines that miid does.
However, ifplugd is currently just version 0.1, so I cannot guarantee
for this.
> I consider Debian does not need several miid/ifplugd-like packages. I
> wish you wil try to work with Graeme and give Debian a single
> perfectly-working miid/ifplugd/whateveritiscalled package.
You may be right.
Graeme, please consider to package ifplugd instead of miid! I
currently see no advantage in packaging miid, if there is ifplugd
available.
As I see you are both the upstream author of miid and the one who
intents to package miid. Strange situation for me to beg you for
replacing your own software with mine... ;-)
Please tell me what you think about improving ifplugd instead of miid!
lp
--
name { Lennart Poettering } mail { lennart@poettering.de }
icq { 11060553 } www { http://www.poettering.de/lennart/ }
loc { hamburg, germany } pgp { 0x1A015CC4 } hack { .phi. }
Attachment:
pgpU0JTk38Wid.pgp
Description: PGP signature