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 AFDEE138802 for ; Sat, 2 Feb 2013 19:18:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 08E6CE051E; Sat, 2 Feb 2013 19:18:35 +0000 (UTC) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8E9BAE04C1 for ; Sat, 2 Feb 2013 19:18:33 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id l13so1165714wie.8 for ; Sat, 02 Feb 2013 11:18:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:subject:message-id:in-reply-to:references :organization:x-mailer:mime-version:content-type :content-transfer-encoding; bh=AEYF+THZVFsr+EvqROu0QpJXVmT6JQCo0/BPIH0/lU0=; b=Wt9cszdYkJIxs8kYvnmJqZYkIIElZt/wPcMzOTQNU9Vjjo71t2BuZw/DB8OEoysAj2 KtC9sYs4+snUJUg3fDF2dDwWzBgGzDxC7CK3cGeH6FtjiJm7CutaDgv6b+NWWMq8Utd1 VIwbhIHHCVXLezPPjbX18mgGU8MeDC3xRrZTNt76bhrQO4+r1CknqlLTdqDWUhDRfW/y FPm7W1rS/2gH+touPAp3YSRNXgqoppqeeKnUKwrtz2KrF8Gq9d05M4wVFLF1xwhcPn1M 2faFEszl6zCoEXThb2aNuOA77F4nEQLQc7Q5HPkd1SOLXhlH0fWzQR/QeitVJSRX/v2V C1Bg== X-Received: by 10.194.77.13 with SMTP id o13mr27681093wjw.58.1359832712084; Sat, 02 Feb 2013 11:18:32 -0800 (PST) Received: from khamul.example.com (196-215-2-98.dynamic.isadsl.co.za. [196.215.2.98]) by mx.google.com with ESMTPS id q13sm17179410wie.0.2013.02.02.11.18.29 (version=SSLv3 cipher=RC4-SHA bits=128/128); Sat, 02 Feb 2013 11:18:31 -0800 (PST) Date: Sat, 2 Feb 2013 21:17:38 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] udev-191 bit me. Insufficient ptys Message-ID: <20130202211738.66a72582@khamul.example.com> In-Reply-To: <20130202162110.1623aaa5@weird.wonkology.org> References: <20130202162110.1623aaa5@weird.wonkology.org> Organization: Internet Solutions X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.14; x86_64-pc-linux-gnu) 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-Transfer-Encoding: 7bit X-Archives-Salt: 7ad3e8a9-ba08-44bd-bdba-fba96a955aba X-Archives-Hash: 459df3a419a82e396d022f1fc913084f On Sat, 2 Feb 2013 16:21:10 +0100 Alex Schuster wrote: > Michael Mol writes: > > > So, I botched the upgrade to udev-191. I thought I'd followed the > > steps, but I apparently only covered them for one machine, not both. > > [...] > > > Udev also complained about DEVTMPFS not being enabled in the > > kernel.[2] I couldn't get into X, but I could log in via getty and > > a plain old vt, so I enabled it, rebuilt the kernel, installed it > > and rebooted...and now that's presumably covered. > > Ran into the same problem, with my sister's PC. Which I had updated > from remote, so I did not see the elogs. I do not think it is correct > behaviour to continue building udev although the system wouldn't boot > with that kernel option missing. I would expect the udev ebuild to > check the running kernel for that option, and refuse to build until > it has it set. Or until building is forced by some USE flag or an > environment variable. > > Had these things not been handled better in the past? There's a furious debate going on in -dev about this very thing, and the bottom line is that your statements above are way too simplistic. - there is no guarantee that /proc/config.gz represents the kernel the binary will actually run on (this emerge might well be the last process you ever run on that kernel) - there is no guarantee that /usr/src/linux corresponds to anything at all (it's a symlink and can point to anything, even invalid stuff) - there is no guarantee that the build host will run the code (think build farms, crossdev etc, so every available config cannot possibly be valid) - and a couple more Basically, the only thing left for the ebuild devs is to notify the user with the important information. The question is not whether to halt the build or not (that cannot and will not be done) but how to do the communication: - news item - elog - README - some arb notice on a web site somewhere ..... This is gentoo, the distro that does not hold your hand and gives you every opportunity to keep both pieces. This is a good example of such. -- Alan McKinnon alan.mckinnon@gmail.com