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