I have a problem that I think is related to udev-103 I have two network device compiled as modules in the kernel (r8169 and ipw2200) Normally the r8169 module is loaded before ipw2200 so the first device get the name "eth0" while the second is "eth1" (and my initscripts are configured this way). Sometimes udev exchange the order in which theese devices are loaded and ipw2200 gets loaded before r8169. The result is that the device names are inverted and my initscripts don't work anymore. here is my emerge --info if you need it Portage 2.1.1-r2 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.4-r4, 2.6.18-gentoo-r3 i686) ================================================================= System uname: 2.6.18-gentoo-r3 i686 Intel(R) Pentium(R) M processor 1.86GHz Gentoo Base System version 1.12.6 Last Sync: Thu, 30 Nov 2006 18:50:01 +0000 app-admin/eselect-compiler: [Not Present] dev-java/java-config: [Not Present] dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r4 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -mmmx -msse -msse2 -mfpmath=sse -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /etc/env.d/02locale /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /usr/share/keymaps/i386/qwerty/it.map.gz" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2 -march=i686 -mmmx -msse -msse2 -mfpmath=sse -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer parallel-fetch sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.switch.ch/mirror/gentoo/ http://trumpetti.atm.tut.fi/gentoo/ http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/ ftp://mirror.switch.ch/mirror/gentoo/ ftp://ftp.easynet.nl/mirror/gentoo/" LANG="it_IT@euro" LC_ALL="it_IT@euro" LDFLAGS="-Wl,-O1" LINGUAS="it" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/portage_tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 X a52 aac acpi alsa audiofile bash-completion berkdb bitmap-fonts bzip2 cairo cdr cli cracklib crypt cups dbus dga dlloader dri dv dvd dvdr dvdread elibc_glibc emboss encode fam fbcon ffmpeg firefox flac fortran gd gdbm gif glut gnutls gpm gstreamer gtk hal iconv idn ieee1394 imagemagick input_devices_evdev input_devices_keyboard input_devices_mouse input_devices_synaptics ipv6 isdnlog jpeg kdeenablefinal kernel_linux lcms libg++ linguas_it mad mikmod mmx mng mp3 mpeg ncurses nls nptl nptlonly offensive ogg opengl pam pcmcia pcre perl png ppds pppd python quicktime readline reflection samba sdl session sndfile speex spell spl sse sse2 ssl svg tcl tcpd theora tiff tk truetype truetype-fonts type1-fonts udev unicode usb userland_GNU vcd video_cards_fbdev video_cards_radeon video_cards_vesa video_cards_vga vorbis win32codecs wmf xml xorg xv xvid zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS
Not a bug. If you rely on device names, then set up custom udev rules to make the naming persistent. (See the recent thread on gentoo-dev mailing list as well).
http://marc.theaimsgroup.com/?t=116498436300001&r=1&w=2
Then maybe you could add some line in the einfo of the new udev to explain this... That would be nice since EVERYONE relied on loading order to name the network devices (at least everyone till now...). It's nice to develop new features but remember sometimes that someone is USING this os and need some continuity and compatibility with older solutions.
(In reply to comment #3) > Then maybe you could add some line in the einfo of the new udev to explain > this... Explain what exactly? That something that worked just because you were lucky enough doesn't work for you any more? I don't see how does this belong to ebuild. Ebuilds are _not_ documentation. If someone feel like mentioning this in udev guide, feel free, thought it's already explained there pretty much, right at the beginning. http://www.gentoo.org/doc/en/udev-guide.xml
(In reply to comment #4) > (In reply to comment #3) > > Then maybe you could add some line in the einfo of the new udev to explain > > this... > > Explain what exactly? That something that worked just because you were lucky > enough doesn't work for you any more? I don't see how does this belong to > ebuild. Ebuilds are _not_ documentation. If someone feel like mentioning this > in udev guide, feel free, thought it's already explained there pretty much, > right at the beginning. > > http://www.gentoo.org/doc/en/udev-guide.xml Indeed. Nothing to add on our end. The only thing udev can guarantee is persistant names, not loading order (without persistant naming schemes), as explained in the thread Jakub kindly linked. If you want consistent behavior, then you need to make sure you're properly set up persistant device names, as explained in the thread and linked in the udev guide (DSD's guide, decibel's primer). (And no, we are not going to repeat how to write udev rules/names in the guide. That's why we provide links.)
*** Bug 157050 has been marked as a duplicate of this bug. ***
