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 D1801138785 for ; Thu, 31 Jan 2013 03:35:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4D3A721C031; Thu, 31 Jan 2013 03:35:09 +0000 (UTC) Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 70E87E05E8 for ; Thu, 31 Jan 2013 03:35:07 +0000 (UTC) Received: by mail-ob0-f171.google.com with SMTP id lz20so2436840obb.16 for ; Wed, 30 Jan 2013 19:35:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ZAE8MH3aYWL/5HHpVpVfiP/KBNioLyo+iCgHl4OGTM4=; b=L8KY0z/BevZcz1HAVTGyWfMvf/dZMU9S3zLofw9lT38wY6kClnUT8cOeV9XDFcXjmQ M9uZI3XqVo8tS6xRKjT6njUSgG8TtnPQf1fHky/KVxyo0snBH4GH3VxGdRtfFKjxlXjG JJjjNLepNvq00GphMVhmVrA02Kp45YJRIJGfo4QNWy8Obw/dJPyKWj7RmBXsi+zTYOIS 2tX0PqZ6A6rJcR2QxTbNfTCnngigLiE5f/70AZS4IrHu5A3XzbrWyryTNUgsvCZJqz/A QybVuMbghzrZNoPNc/P+J9I0x0rYZrSWmfrph9GqbUCN+xkBGnBbY4EHqfYMB99ZYUeS Ilfw== 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 X-Received: by 10.60.30.201 with SMTP id u9mr5646527oeh.28.1359603306591; Wed, 30 Jan 2013 19:35:06 -0800 (PST) Received: by 10.76.20.243 with HTTP; Wed, 30 Jan 2013 19:35:06 -0800 (PST) Date: Wed, 30 Jan 2013 22:35:06 -0500 Message-ID: Subject: [gentoo-user] udev-191 bit me. Insufficient ptys From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 1ae395a2-16b1-4291-96df-a4daec786848 X-Archives-Hash: c06e4c866089225b15dc562b1122f88b 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. -- :wq