The /etc/hotplug.d/default/default.hotplug script doesn't appear to be compatible with udev-059. At boot time, references to /dev/null in default.hotplug generate console errors stating that the device does not exist. I have not tested whether or not hotplugging actually works yet. I run hotplug 20040923, run level boot and coldplug 20040920, also run level boot. Changing the runlevel from boot to default makes no difference. Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.12-gentoo-r3 i686) ================================================================= System uname: 2.6.12-gentoo-r3 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 23 2005, 20:58:40)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo ftp://gentoo.mirrors.pair.com http://gentoo.ccccom.com" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 X alsa avi cdr cups divx4linux dvd dvdr encode fbcon gif gpm gtk gtk2 jpeg mad mikmod mmx mpeg ncurses nls nptl oggvorbis opengl oss png python readline sdl slang spell sse ssl tcpd truetype xml2 xprint xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
You should not be running the hotplug init script. It does not do anything at all. What exactly is the errors? hotplug/coldplug should be running way after udev starts up, so there should not be an issue.
I'm getting the same error on two different systems after upgrading to udev-059. This occurs well before any scripts from /etc/init.d are run: * Configuring system to use udev ... /etc/hotplug.d/default/default.hotplug: line 26: /dev/null: No such file or directory [...repeats several times...] /etc/hotplug.d/default/default.hotplug: line 26: /dev/null: No such file or directory * Setting /sbin/udevsend as hotplug agent ... [ ok ] It looks like this has also been reported on the forums: http://forums.gentoo.org/viewtopic-t-355069-highlight-udev.html?sid=5dc06f5d41745be621a82d2316baece6
Ok, I can duplicate this now, odd that I couldn't before.
Anyone in the base-system group who has some good bash-foo, know how to change the following lines: exec < /dev/null test -t 1 || exec > /dev/null test -t 2 || exec 2>&1 to not use /dev/null if it's not there? I think we are trying to close all fd and then route stdin and stdout nowhere. Have a better idea how to do it?
I'm getting some upstream ackowledgement that this is likely a udev-059 issue. Other distros are reporting the problem, e.g. Debian. I'm masking off 059 locally for now and using 058.
Anyone in the base-system group who has some good bash-foo, know how to change the following lines: exec < /dev/null test -t 1 || exec > /dev/null test -t 2 || exec 2>&1 to not use /dev/null if it's not there? I think we are trying to close all fd and then route stdin and stdout nowhere. Have a better idea how to do it? Greg, How about: exec 0<&- exec 1>&- exec 2>&- Those will close the stdin, stdout and stderr, respectively. Phil
It's not a udev 059 issue, it's how I wrote the gentoo udev config file. I'll have a new update in a bit to fix this, sorry about this...
*** Bug 97702 has been marked as a duplicate of this bug. ***
Fixed in 060 release
