From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2FD6B198005 for ; Sat, 23 Feb 2013 17:19:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A6110E068E; Sat, 23 Feb 2013 17:19:18 +0000 (UTC) Received: from mail.muc.de (colin.muc.de [193.149.48.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 284BFE0678 for ; Sat, 23 Feb 2013 17:19:16 +0000 (UTC) Received: (qmail 48795 invoked by uid 3782); 23 Feb 2013 17:19:14 -0000 Received: from acm.muc.de (pD951B645.dip.t-dialin.net [217.81.182.69]) by colin.muc.de (tmda-ofmipd) with ESMTP; Sat, 23 Feb 2013 18:19:12 +0100 Received: (qmail 3217 invoked by uid 1000); 23 Feb 2013 17:18:42 -0000 Date: Sat, 23 Feb 2013 17:18:42 +0000 To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Kernel 3.7.9: Lots of devices are root root rw-------. Message-ID: <20130223171841.GA3178@acm.acm> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Archives-Salt: bf636d40-6431-42fb-ad95-7bbbefc4e986 X-Archives-Hash: 4d39e406471045961bb3fc23cb9f16cd Hi, Gentoo! Just built the new kernel 3.7.9 last night, and it's one of these "nothing works" situations. It seems the problems are with the device files, whose ownership is set to "root root" (rather than, e.g., "root audio") and whose permissions are set to crw------- (rather than the expected crw-rw----). I'm still running udev-171-r10. This might well make a difference. Needless to say, everything works under kernel 3.6.11. It would be nice if there were some mistake in my kernel config. Could somebody help me get this fixed, please. -- Alan Mackenzie (Nuremberg, Germany).