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 A8D2613879B for ; Thu, 31 Jan 2013 14:32:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DA18021C0C9; Thu, 31 Jan 2013 14:32:00 +0000 (UTC) Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 47245E0281 for ; Thu, 31 Jan 2013 14:31:59 +0000 (UTC) Received: by mail-oa0-f44.google.com with SMTP id h1so458569oag.31 for ; Thu, 31 Jan 2013 06:31:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=2CrFAbNAsofFIH880SAn+7y9g1JXbasBsOjV5bVDn7g=; b=YjLplZne6Bd5SPJ81fkl5e6lUBf0bEv8LIpMRhd+HzpJc/1DDiswr1rB5HWazamkrT pf+woArElVfkUih8SY1I6AWEfCvawCTolEUIm1Yfrwy/sMtfa10s6OW5W2gDh0CNhz2U f2AtqBLf4cBukM4cFGFRe+O4STfDSp5N39aWMmoUbe8tERiiRSifFTILntFqyUUdiP95 ms81x5Ne3+MM01/+JFQZ+7nV78Ey4yglWjv97kN/sHmutqvVZO2wrGWF0qg+gDjqnhCJ GQqgAS09wA6T+t4fGO5giRo7GlgwsmAp4WZYFzWS9J2fF9LHcUuIxtrcdE1ou1vecvvZ P7pQ== 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 u9mr6896680oeh.28.1359642718459; Thu, 31 Jan 2013 06:31:58 -0800 (PST) Received: by 10.76.20.243 with HTTP; Thu, 31 Jan 2013 06:31:58 -0800 (PST) In-Reply-To: References: Date: Thu, 31 Jan 2013 09:31:58 -0500 Message-ID: Subject: Re: [gentoo-user] udev-191 bit me. Insufficient ptys From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: a49eb8ee-0273-45f9-8e46-06bc2b11a74f X-Archives-Hash: 96072932b4adaadc361ad716abecbc13 On Thu, Jan 31, 2013 at 9:05 AM, Michael Mol wrote: > On Thu, Jan 31, 2013 at 8:47 AM, Michael Mol wrote: >> On Thu, Jan 31, 2013 at 8:26 AM, Michael Mol wrote: >>> On Wed, Jan 30, 2013 at 11:48 PM, Canek Pel=C3=A1ez Vald=C3=A9s wrote: >>>> On Wed, Jan 30, 2013 at 10:45 PM, Canek Pel=C3=A1ez Vald=C3=A9s wrote: >>>>> On Wed, Jan 30, 2013 at 9:35 PM, Michael Mol wrot= e: >>>>>> 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 applie= s >>>>>> to udev-mount. So after removing that[1], I was able to at least boo= t >>>>>> 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 >>>>> >>>>> Do you have CONFIG_LEGACY_PTYS=3Dy? If so, do you really need it? A >>>>> little over a year ago[1] I had an annoying issue for having that >>>>> option enabled in my kernel, with a lot of virtual ttys reported in >>>>> systemctl. This is a shot in the dark (I really don't know if it's >>>>> related to your problem), but perhaps having the LEGACY_PTYS option >>>>> enabled somehow depleted your available pseudo terminals (which any X >>>>> terminal needs to run)? I suppose screen is also out of the question >>>>> for the same reason. >>> >>> No, I don't have CONFIG_LEGACY_PTYs. I do have UNIX98 PTYs, and I >>> tried enabling alternate namespaces, but that didn't help either. >>> >>>> >>>> Also related, if you have LEGACY_PTYS: >>>> >>>> "LEGACY_PTY_COUNT: >>>> >>>> The maximum number of legacy PTYs that can be used at any one time. >>>> The default is 256, and should be more than enough. Embedded >>>> systems may want to reduce this to save memory. >>>> >>>> When not in use, each legacy PTY occupies 12 bytes on 32-bit >>>> architectures and 24 bytes on 64-bit architectures." >>> >>> Yeah, I'm not using CONFIG_LEGACY_PTY, so LEGACY_PTY_COUNT doesn't >>> even make itself available in menuconfig. >> >> Hm. Some googling suggests this might be a permissions issue. >> >> I do have consolekit enabled, but I'm using gdm, so I'd expect that to >> take care of itself. (Although screen fails to launch from vt1, so >> it's not a consolekit problem.) > > OK, it looks like /dev/pts is not mounted. But darned if I know > why...Isn't udev supposed to handle that? SOLVED. Two pieces missing. One, I didn't notice the "unable to create /dev/pts" and "unable to create /dev/shm" messages in the boot sequence...and they didn't appear in /var/log/messages for whatever reason. Two, I'm not using an initramfs on this machine, so in *addition* to needing to have CONFIG_DEVTMPFS enabled, I also needed to have CONFIG_DEVTMPFS_MOUNT enabled. Rebuilding the kernel with that, and rebooting, seems to have fixed things. -- :wq