From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FBk0A-0002Ow-4b for garchives@archives.gentoo.org; Wed, 22 Feb 2006 02:45:14 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k1M2iB5g014415; Wed, 22 Feb 2006 02:44:11 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k1M2eCqx009640 for ; Wed, 22 Feb 2006 02:40:13 GMT Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by smtp.gentoo.org with esmtp (Exim 4.54) id 1FBjvI-0006j7-99 for gentoo-user@lists.gentoo.org; Wed, 22 Feb 2006 02:40:12 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FBjv4-0001ME-To for gentoo-user@gentoo.org; Wed, 22 Feb 2006 03:39:59 +0100 Received: from www.buffer.net ([24.73.161.102]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Feb 2006 03:39:58 +0100 Received: from wireless by www.buffer.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Feb 2006 03:39:58 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: James Subject: [gentoo-user] Re: odd /dev/null beharvior Date: Wed, 22 Feb 2006 02:39:38 +0000 (UTC) Message-ID: References: <20060218213633.GC27035@rescomp.berkeley.edu> <20060221235046.GA13544@rescomp.berkeley.edu> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 24.73.161.102 (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051215) Sender: news X-Archives-Salt: 1ca39cb6-f2a8-4763-9213-255086268381 X-Archives-Hash: 26dd670d9b21b2ebd11c3d055994d576 Christopher Cowart rescomp.berkeley.edu> writes: > Sounds like this is related to the bug that's in an earlier thread. > Do as root: > # ebuild `equery which udev` digest >>> Generating digest file... <<< udev-079.tar.bz2 >>> Generating manifest file... <<< ChangeLog <<< files/05-udev-early.rules-078 <<< files/05-udev-early.rules-079 <<< files/digest-udev-068-r1 <<< files/digest-udev-069 <<< files/digest-udev-070-r1 <<< files/digest-udev-071 <<< files/digest-udev-072 <<< files/digest-udev-073 <<< files/digest-udev-077 <<< files/digest-udev-077-r1 <<< files/digest-udev-077-r2 <<< files/digest-udev-077-r3 <<< files/digest-udev-077-r4 <<< files/digest-udev-077-r5 <<< files/digest-udev-078 <<< files/digest-udev-079 <<< files/digest-udev-079-r1 <<< files/digest-udev-081 <<< files/digest-udev-081-r1 <<< files/digest-udev-084 <<< files/udev-021-udev_add_c-gcc295-compat.patch <<< files/udev-050-udev_volume_id.patch <<< files/udev-parisc-path_id-again.patch <<< files/udev-parisc-path_id.patch <<< files/udev-start-077-r2.sh <<< files/udev-start-077-r4.sh <<< files/udev-start-077.sh <<< files/udev-start-079.sh <<< files/udev-start.sh <<< files/udev-stop.sh <<< files/udev.conf <<< files/udev.conf.post_024 <<< files/udev.conf.post_046 <<< files/udev.conf.post_050 <<< files/udev.conf.post_059 <<< files/udev.conf.post_081 <<< files/udev.hotplug.empty <<< files/udev.permissions <<< files/udev.rules <<< files/udev.rules-018 <<< files/udev.rules-064-r1 <<< files/udev.rules-077 <<< files/udev.rules-077-r1 <<< files/udev.rules-077-r5 <<< files/udev.rules-078 <<< files/udev.rules-084 <<< files/udev.rules.post_012 <<< metadata.xml <<< udev-068-r1.ebuild <<< udev-069.ebuild <<< udev-070-r1.ebuild <<< udev-071.ebuild <<< udev-072.ebuild <<< udev-073.ebuild <<< udev-077-r1.ebuild <<< udev-077-r2.ebuild <<< udev-077-r3.ebuild <<< udev-077-r4.ebuild <<< udev-077-r5.ebuild <<< udev-077.ebuild <<< udev-078.ebuild <<< udev-079-r1.ebuild <<< udev-079.ebuild <<< udev-081-r1.ebuild <<< udev-081.ebuild <<< udev-084.ebuild >>> Computed message digests. > This will update the digest for now. The changes will be overwritten the > next time you sync portage, but it won't matter til the next time you > emerge udev. At which time, hopefully they'll have it fixed in portage. WEll in 'unmerge' the udev, so now I have to keep the system online until an emerge sync brings a new, installable udev. I even tried to got back to udev-079, but that would not install either.... ideas? which bug do I watch for resolution? James -- gentoo-user@gentoo.org mailing list