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
| ||
|
Message-ID: <646765f40710150206j75af4c4dwac4f4565451b64b1@mail.gmail.com> Date: Mon, 15 Oct 2007 19:06:20 +1000 From: "Julian Calaby" <julian.calaby@...il.com> To: "Rob Landley" <rob@...dley.net> Cc: "Theodore Tso" <tytso@....edu>, "James Bottomley" <James.Bottomley@...eleye.com>, "Matthew Wilcox" <matthew@....cx>, linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org, "Jens Axboe" <axboe@...e.de>, "Suparna Bhattacharya" <suparna@...ibm.com>, "Nick Piggin" <piggin@...erone.com.au> Subject: Re: What still uses the block layer? On 10/15/07, Rob Landley <rob@...dley.net> wrote: > I note that the eth0 and eth1 names are dynamically assigned on a first come > first serve basis (like scsi). This never causes me a problem because the > driver loading order is constant, and once you figure out that eth0 is > gigabit and eth1 is the 80211g it _stays_ that way across reboots, reliably. > Yeah, it's a heuristic. Hands up everybody relying on such a heuristic in > the real world. Umm, not quite, from my experiences with pre-production wireless drivers, (another story, another time) fancy stuff is being done in udev to make sure that your gigabit card is always assigned to eth0. -- Julian Calaby Email: julian.calaby@...il.com - 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/
Powered by blists - more mailing lists