In message <27958.1102537524@munnari.OZ.AU>,

Robert Elz writes:

>Which code do you believe it isn't time for?

>Why?   That makes no sense to me.   We always had (well, always for 11+ years)
>multiple loopback interface capability (working "properly" or not).
>If anyone felt a need to fix that, they've had plenty of time.

Robert, are you serious, or are you just playing dumb to win an
argument?  Before, I could force correct behaviour by configuring a
kernel with a single loopback instance at config-time.  After Peter
committed his change to -current -current, I can't.

Since I'm in a minority on this, why don't we move it off-list?