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 2D73C13879D for ; Thu, 31 Jan 2013 15:24:16 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1A25221C0DD; Thu, 31 Jan 2013 15:24:06 +0000 (UTC) Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4FE6221C00E for ; Thu, 31 Jan 2013 15:24:04 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id dr13so2166143wgb.14 for ; Thu, 31 Jan 2013 07:24:03 -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=Y/2JpKxyJz9LKr4tg500sWRV53GTSKwiNGMfPASUdKI=; b=C97Nfuw88qJ0y6tV1nYHbDiQ2BgrF3DYGxeqosQzMtufzg6IYsO9gf7ht/40BGRKlG 2bn4UGCIuLQ6HwCrQvbVFl+/6HBU3AKziLTNh38dK+xjIuCuyYgFJ/xmk5ICD0933nme IcAQI6NdV2RwWpuJHQWNX43Gg9K8vTsxJ+xUyYUtwt2crP6TOpa5qGiee4h5fwqQqHf+ bHmaf/Dp1jl1iA3pDH8Zzjyq74hNsyXl9mO6wcAX/CWnmhk3MG3FI2wLCuRMj+2/S+0P XqpUICe2z1t5OBh3/Xezkg1AfryH40Igzemt1RAkYrZ2Un4Gcs9CffTONiiBQieqwxUW HxMg== X-Received: by 10.194.48.74 with SMTP id j10mr16162815wjn.36.1359645842973; Thu, 31 Jan 2013 07:24:02 -0800 (PST) Received: from khamul.example.com (dustpuppy.is.co.za. [196.14.169.11]) by mx.google.com with ESMTPS id ex6sm9957587wid.3.2013.01.31.07.24.00 (version=SSLv3 cipher=RC4-SHA bits=128/128); Thu, 31 Jan 2013 07:24:02 -0800 (PST) Date: Thu, 31 Jan 2013 17:23:12 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] udev-191 bit me. Insufficient ptys Message-ID: <20130131172312.4595fc24@khamul.example.com> In-Reply-To: References: 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: 77e9771b-8a7a-4f54-b76d-f45cf9ab40de X-Archives-Hash: 833f8a259c5fcfa99d13eb1f98f9345d On Wed, 30 Jan 2013 22:35:06 -0500 Michael Mol wrote: > 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. > > The news item instructions specified that I had to remove > udev-postmount from my runlevels. I didn't have udev-postmount in my > runlevels, so I didn't remove it. Turns out, that dictum also applies > to udev-mount. So after removing that[1], I was able to at least boot > again. > > 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. > > I'm now able to get into X, but when I try to run an xterm, it fails. > Checking ~/.xsession_errors, I find: > > xterm: Error 32, error 2: No such file or directory > Reason: get_pty: not enough ptys > > I find this bizarre, as I'd never had any trouble with xterm in this > way before. What'd I do wrong, and how do I recover? I don't trust > emerging at this point; I tried re-emerging udev, and I aborted after > I saw an stderr line about failing to open a pty, even though portage > does quiet builds for parallel building by default...so I doubt > whatever emitted that line on stderr was being properly guarded > against the failure. > > [1] I didn't have a boot cd or similar to work with, so I used the old > init=/bin/sh trick on the command line. That was functional. And then > I tried init=/usr/bin/vim, and things got real. :) > > [2] Sparking a bemused discussion with a friend at tonight's LUG > meeting over the devfs->udev->udev+devtmpfs progression, but that's a > different story. I can't get any kernel >=gentoo-sources-3.7.1 to work properly with vtys either. 3.7.1 is fine, anything earlier is fine. I haven't bothered tracking it down further than that (have a severe dose of laziness right now...) What kernel are you running on these affected hosts? -- Alan McKinnon alan.mckinnon@gmail.com