> le lun 25-03-2002 à 12:34, Joachim Breuer a écrit :
>> Being able to redetect a pulled card put in a different slot as a
>> "known" one giving it the same eth<i> (and associated WOL etc. config)
>> as before would of course be nice, but I can't see how this can be
>> cleanly done over reboots.
>
> Some may say that being able to give the same eth<i> to the same bus
> position, even after swapping the card for a new one, is more important
> - think of production machines which can't afford being off-service for
> too long. You just shutdown, swap the cards, poweron and you go. No
> reconfig, that's how it should run.
Reading it again I wasn't all too clear in that last posting - I meant
it to show two alternatives (eth<i> stays with bus vs. eth<i> stays
with card). Each with its own advantages and disadvantages; I don't
have a fixed preference, but a slight leaning towards fixed
bus-position based numbers (spanning different drivers, if at all
possible). That would allow Xavier's scenario even with a different
type of replacement card.
(Yes of course you'd have to reconfig to swap a PCI card for an ISA
one but let's not go there, OK?)
So long,
Joe
-- "I use emacs, which might be thought of as a thermonuclear word processor." -- Neal Stephenson, "In the beginning... was the command line" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/