Your message dated Wed, 15 Nov 2006 14:45:41 +0100 with message-id <20061115134541.GL2560@mails.so.argh.org> and subject line Commited to release notes has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Should document NIC naming issue with udev
- From: Frans Pop <aragorn@tiscali.nl>
- Date: Sun, 18 Dec 2005 16:18:02 +0100
- Message-id: <200512181618.02980.aragorn@tiscali.nl>
Package: release-notes When udev is used, drivers for network interface cards can be loaded in a different order than previously, basically because drivers are loaded in parallel. This can result in interfaces being swapped. The best solution currently appears to be to create udev rewriting rules to fix the interface names. This should be documented in the release notes for Etch.Attachment: pgpSlWqifyjDN.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: 343892-done@bugs.debian.org
- Subject: Commited to release notes
- From: Andreas Barth <aba@not.so.argh.org>
- Date: Wed, 15 Nov 2006 14:45:41 +0100
- Message-id: <20061115134541.GL2560@mails.so.argh.org>
Hi, during merge of the kernel team's release notes, I added this section to the release notes: <sect1><heading>Device enumeration reordering</heading> <p>Etch features a more robust mechanism for hardware discovery than previous releases. However, this may cause changes in the order devices are discovered on your system affecting the order in which device names are assigned. For example, if you have two network adapters that are associated with two different drivers, the devices eth0 and eth1 refer to maybe swapped.</p> <p>For network devices, you can avoid this reordering by using the <prgn>ifrename</prgn> utility to bind physical devices to specific names at boot time. <!-- TODO: add ifupdown-scripts-zg2 as well here? --> See <manref name="ifrename" section="8"> and <manref name="iftab" section="5"> for more information.</p> <!-- TODO: *** maks: please review the initramfs stuff for accuracy - I'm going *** by what I remember, and haven't tested this recently --> <p>For storage devices, you can avoid this reordering by using <prgn>initramfs-tools</prgn> and configuring <prgn>initramfs-tools</prgn> to load storage devices in the same order they are currently loaded. [...] Cheers, Andi -- http://home.arcor.de/andreas-barth/
--- End Message ---