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