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 80B051388E8 for ; Thu, 7 Feb 2013 17:41:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7E8E7E05D9; Thu, 7 Feb 2013 17:41:04 +0000 (UTC) Received: from homiemail-a44.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by pigeon.gentoo.org (Postfix) with ESMTP id 2C68CE0230 for ; Thu, 7 Feb 2013 17:41:03 +0000 (UTC) Received: from homiemail-a44.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a44.g.dreamhost.com (Postfix) with ESMTP id A5638118060 for ; Thu, 7 Feb 2013 09:41:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=libertytrek.org; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s= libertytrek.org; bh=uULKToPtlH2B7JQ9KZqCFJlUB1U=; b=BOB4Xq6sgLby MUZRg+cFY1bBGX1lwWjoVc8j7g0DtY2CLC5BWB3rexIDw2qItYXZqAECYCQbBM4V +pF7LzdPGryt6BtJOYXsrP7/FcABPtn8pJBblXIkkf/2B0uoqLFFJ9uwHz13to36 nbY3xYs0xcjCEwYrI28ktG48n8LJgh8= Received: from [127.0.0.1] (unknown [159.63.145.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: tanstaafl@libertytrek.org) by homiemail-a44.g.dreamhost.com (Postfix) with ESMTPSA id 454A4118057 for ; Thu, 7 Feb 2013 09:41:02 -0800 (PST) Message-ID: <5113E717.7020402@libertytrek.org> Date: Thu, 07 Feb 2013 12:40:39 -0500 From: Tanstaafl User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 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: Re: [gentoo-user] udev-191 bit me. Insufficient ptys References: <20130202162110.1623aaa5@weird.wonkology.org> <20130202211738.66a72582@khamul.example.com> <20130203185145.4008d87f@weird.wonkology.org> In-Reply-To: <20130203185145.4008d87f@weird.wonkology.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 70f3ba95-8f68-469e-a571-2ee87297e703 X-Archives-Hash: 0ac324c76fd6b18f209dddffd721afff On 2013-02-03 12:51 PM, Alex Schuster wrote: >> 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 > There is one, from 2013-01-23, ending with 'Apologies if this news came > too late for you.' > > Okay, if that one came a little earlier, I would have been fine. Ok, I'm actually now toying with the idea of updating udev on my older server, since a separate /usr is now supported... So, reading this news item: > - The need of CONFIG_DEVTMPFS=y in the kernel; need to verify the > fstype for possible /dev line in /etc/fstab is devtmpfs (and not, > for example, tmpfs) So, since I have: > shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 I change the type tmpfs to devtmpfs... ok... Last... > And read every message printed by the emerge of udev and > udev-init-scripts to ensure the system is in order before booting as > this news item might not be complete. All of these messages will be in the emailed emerge message(s), correct? Meaning, I won't have to be sitting there watching the emerge output? Thanks...