From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ru60W-0001X5-LI for garchives@archives.gentoo.org; Sun, 05 Feb 2012 17:36:08 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 638EBE074B; Sun, 5 Feb 2012 17:35:58 +0000 (UTC) Received: from homiemail-a83.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by pigeon.gentoo.org (Postfix) with ESMTP id 04CBFE073C for ; Sun, 5 Feb 2012 17:34:55 +0000 (UTC) Received: from homiemail-a83.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a83.g.dreamhost.com (Postfix) with ESMTP id 46FD65E063 for ; Sun, 5 Feb 2012 09:34:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=libertytrek.org; h=message-id :date:from:mime-version:to:subject:content-type: content-transfer-encoding; q=dns; s=libertytrek.org; b=lK0id/7Od 6zUK+1aDTyB7wWMOcpC/vcxid5cNUtNOtPvTDA20rWOuOvHz4EsqD5PmLbybKLap ZrGw+dglpPvok4y53Beyyq9lDU+IDTmaMNpfigo1UOtLFAW3wHZJspfIEJZza9zb B4uYQBjVXNKAf81+pBzvmDsZQSS3h1esbg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=libertytrek.org; h= message-id:date:from:mime-version:to:subject:content-type: content-transfer-encoding; s=libertytrek.org; bh=/QvEz+j2/2QnRnz wk+dj1fa/bjA=; b=FnYhf1RoggDS2ak+pAOiE84omD+oND36FnzEtKTN1auyifZ +kylEMTwJNqcgBa6SCGdlsS/KhyLFEgkAyHJhHtXa1Qhl8BnXJvU2JJY2r4UEMa1 rTAyVtmQeuhUSXt3CM+5e1hdR3o/Lj8u0fLszkQQSki/lgon8zIKqL3JafSU= Received: from [127.0.0.1] (50-76-228-201-static.hfc.comcastbusiness.net [50.76.228.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: tanstaafl@libertytrek.org) by homiemail-a83.g.dreamhost.com (Postfix) with ESMTPSA id 186125E060 for ; Sun, 5 Feb 2012 09:34:55 -0800 (PST) Message-ID: <4F2EBDC0.4090803@libertytrek.org> Date: Sun, 05 Feb 2012 12:34:56 -0500 From: Tanstaafl User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Another issue/questions updating udev from 164-r2 to 171-r5 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 3099e762-d5c9-4c49-b5ed-bbb75e72993b X-Archives-Hash: f66947ef47c6f540a3dfc82fcafb6b0f I just updated these, and am unsure how to deal with the issues... First issue: *************************** Found sources for kernel version: 3.0.6-gentoo Checking for suitable kernel configuration options... ERROR: setup CONFIG_BLK_DEV_BSG: is not set when it should be. WARN: setup Please check to make sure these options are set correctly. Failure to do so may cause unexpected problems. I can probably find this when make'ing the new kernel, but if someone knows exactly where to find it that would be appreciated. *************************** Next issue/question (from post install log): *************************** LOG: postinst Updating persistent-net rules file restarting udevd now. persistent-net does assigning fixed names to network devices. If you have problems with the persistent-net rules, just delete the rules file rm /etc/udev/rules.d/70-persistent-net.rules and then reboot. This may however number your devices in a different way than they are now. So - how do I know if I need to worry about this? **************************** Next issue/question (from post install log): **************************** WARN: postinst If you build an initramfs including udev, then please make sure that the /sbin/udevadm binary gets included, and your scripts changed to use it,as it replaces the old helper apps udevinfo, udevtrigger, ... mount options for directory /dev are no longer set in /etc/udev/udev.conf, but in /etc/fstab as for other directories. If you use /dev/md/*, /dev/loop/* or /dev/rd/*, then please migrate over to using the device names /dev/md*, /dev/loop* and /dev/ram*. The devfs-compat rules have been removed. For reference see Bug #269359. Rules for /dev/hd* devices have been removed Please migrate to libata. How do I know if I need to worry about any of this stuff? I'm a bit lost here... Thanks for any advice/comments... Charles