linux-kernel - Re: VIA EPIA EK: strange eth dev numbering

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0708021246200.24572@fbirervta.pbzchgretzou.qr>
Date:	Thu, 2 Aug 2007 12:49:16 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Herbert Rosmanith <kernel@...dsau.enemy.org>
cc:	Michael Tokarev <mjt@....msk.ru>, linux-kernel@...r.kernel.org
Subject: Re: VIA EPIA EK: strange eth dev numbering

On Aug 2 2007 12:42, Herbert Rosmanith wrote:
>
>hu. where are the days when eth0 was eth0 ...

If you and/or your distribution accidentally or incidentally loaded modules in
the wrong order (which may happen in e.g. parallel-running boot scripts), you
suddenly have eth0 as eth1. Or, when you changed the PCI slots (i.e. swapped
cards around), eth0 would also suddenly become a different one. There never
*were* days when eth0 remained eth0 across such changes.

>which translates:
>
>    "Haha, that's randy, that's like in Windows, which
>    notices that you've got a new mainboard"

In Linux, the user recognizes he got himself a new mainboard,
e.g. when the IDE chip changed and the new module is not in the initrd.

	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/