1 |
On Thu, Jan 31, 2013 at 9:05 AM, Michael Mol <mikemol@×××××.com> wrote: |
2 |
> On Thu, Jan 31, 2013 at 8:47 AM, Michael Mol <mikemol@×××××.com> wrote: |
3 |
>> On Thu, Jan 31, 2013 at 8:26 AM, Michael Mol <mikemol@×××××.com> wrote: |
4 |
>>> On Wed, Jan 30, 2013 at 11:48 PM, Canek Peláez Valdés <caneko@×××××.com> wrote: |
5 |
>>>> On Wed, Jan 30, 2013 at 10:45 PM, Canek Peláez Valdés <caneko@×××××.com> wrote: |
6 |
>>>>> On Wed, Jan 30, 2013 at 9:35 PM, Michael Mol <mikemol@×××××.com> wrote: |
7 |
>>>>>> So, I botched the upgrade to udev-191. I thought I'd followed the |
8 |
>>>>>> steps, but I apparently only covered them for one machine, not both. |
9 |
>>>>>> |
10 |
>>>>>> The news item instructions specified that I had to remove |
11 |
>>>>>> udev-postmount from my runlevels. I didn't have udev-postmount in my |
12 |
>>>>>> runlevels, so I didn't remove it. Turns out, that dictum also applies |
13 |
>>>>>> to udev-mount. So after removing that[1], I was able to at least boot |
14 |
>>>>>> again. |
15 |
>>>>>> |
16 |
>>>>>> Udev also complained about DEVTMPFS not being enabled in the |
17 |
>>>>>> kernel.[2] I couldn't get into X, but I could log in via getty and a |
18 |
>>>>>> plain old vt, so I enabled it, rebuilt the kernel, installed it and |
19 |
>>>>>> rebooted...and now that's presumably covered. |
20 |
>>>>>> |
21 |
>>>>>> I'm now able to get into X, but when I try to run an xterm, it fails. |
22 |
>>>>>> Checking ~/.xsession_errors, I find: |
23 |
>>>>>> |
24 |
>>>>>> xterm: Error 32, error 2: No such file or directory |
25 |
>>>>>> Reason: get_pty: not enough ptys |
26 |
>>>>> |
27 |
>>>>> Do you have CONFIG_LEGACY_PTYS=y? If so, do you really need it? A |
28 |
>>>>> little over a year ago[1] I had an annoying issue for having that |
29 |
>>>>> option enabled in my kernel, with a lot of virtual ttys reported in |
30 |
>>>>> systemctl. This is a shot in the dark (I really don't know if it's |
31 |
>>>>> related to your problem), but perhaps having the LEGACY_PTYS option |
32 |
>>>>> enabled somehow depleted your available pseudo terminals (which any X |
33 |
>>>>> terminal needs to run)? I suppose screen is also out of the question |
34 |
>>>>> for the same reason. |
35 |
>>> |
36 |
>>> No, I don't have CONFIG_LEGACY_PTYs. I do have UNIX98 PTYs, and I |
37 |
>>> tried enabling alternate namespaces, but that didn't help either. |
38 |
>>> |
39 |
>>>> |
40 |
>>>> Also related, if you have LEGACY_PTYS: |
41 |
>>>> |
42 |
>>>> "LEGACY_PTY_COUNT: |
43 |
>>>> |
44 |
>>>> The maximum number of legacy PTYs that can be used at any one time. |
45 |
>>>> The default is 256, and should be more than enough. Embedded |
46 |
>>>> systems may want to reduce this to save memory. |
47 |
>>>> |
48 |
>>>> When not in use, each legacy PTY occupies 12 bytes on 32-bit |
49 |
>>>> architectures and 24 bytes on 64-bit architectures." |
50 |
>>> |
51 |
>>> Yeah, I'm not using CONFIG_LEGACY_PTY, so LEGACY_PTY_COUNT doesn't |
52 |
>>> even make itself available in menuconfig. |
53 |
>> |
54 |
>> Hm. Some googling suggests this might be a permissions issue. |
55 |
>> |
56 |
>> I do have consolekit enabled, but I'm using gdm, so I'd expect that to |
57 |
>> take care of itself. (Although screen fails to launch from vt1, so |
58 |
>> it's not a consolekit problem.) |
59 |
> |
60 |
> OK, it looks like /dev/pts is not mounted. But darned if I know |
61 |
> why...Isn't udev supposed to handle that? |
62 |
|
63 |
SOLVED. |
64 |
|
65 |
Two pieces missing. |
66 |
|
67 |
One, I didn't notice the "unable to create /dev/pts" and "unable to |
68 |
create /dev/shm" messages in the boot sequence...and they didn't |
69 |
appear in /var/log/messages for whatever reason. |
70 |
|
71 |
Two, I'm not using an initramfs on this machine, so in *addition* to |
72 |
needing to have CONFIG_DEVTMPFS enabled, I also needed to have |
73 |
CONFIG_DEVTMPFS_MOUNT enabled. |
74 |
|
75 |
Rebuilding the kernel with that, and rebooting, seems to have fixed things. |
76 |
|
77 |
-- |
78 |
:wq |