1 |
On Wed, Jan 30, 2013 at 9:35 PM, Michael Mol <mikemol@×××××.com> wrote: |
2 |
> So, I botched the upgrade to udev-191. I thought I'd followed the |
3 |
> steps, but I apparently only covered them for one machine, not both. |
4 |
> |
5 |
> The news item instructions specified that I had to remove |
6 |
> udev-postmount from my runlevels. I didn't have udev-postmount in my |
7 |
> runlevels, so I didn't remove it. Turns out, that dictum also applies |
8 |
> to udev-mount. So after removing that[1], I was able to at least boot |
9 |
> again. |
10 |
> |
11 |
> Udev also complained about DEVTMPFS not being enabled in the |
12 |
> kernel.[2] I couldn't get into X, but I could log in via getty and a |
13 |
> plain old vt, so I enabled it, rebuilt the kernel, installed it and |
14 |
> rebooted...and now that's presumably covered. |
15 |
> |
16 |
> I'm now able to get into X, but when I try to run an xterm, it fails. |
17 |
> Checking ~/.xsession_errors, I find: |
18 |
> |
19 |
> xterm: Error 32, error 2: No such file or directory |
20 |
> Reason: get_pty: not enough ptys |
21 |
|
22 |
Do you have CONFIG_LEGACY_PTYS=y? If so, do you really need it? A |
23 |
little over a year ago[1] I had an annoying issue for having that |
24 |
option enabled in my kernel, with a lot of virtual ttys reported in |
25 |
systemctl. This is a shot in the dark (I really don't know if it's |
26 |
related to your problem), but perhaps having the LEGACY_PTYS option |
27 |
enabled somehow depleted your available pseudo terminals (which any X |
28 |
terminal needs to run)? I suppose screen is also out of the question |
29 |
for the same reason. |
30 |
|
31 |
> I find this bizarre, as I'd never had any trouble with xterm in this |
32 |
> way before. What'd I do wrong, and how do I recover? I don't trust |
33 |
> emerging at this point; I tried re-emerging udev, and I aborted after |
34 |
> I saw an stderr line about failing to open a pty, even though portage |
35 |
> does quiet builds for parallel building by default...so I doubt |
36 |
> whatever emitted that line on stderr was being properly guarded |
37 |
> against the failure. |
38 |
|
39 |
I don't see how an error about pseudo terminals could affect the |
40 |
compilation. You could also try to compile with &> to a log file, and |
41 |
prepare a binary package instead of installing it immediately. The log |
42 |
file actually could help to find the problem. |
43 |
|
44 |
[1] http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/3609 |
45 |
|
46 |
Regards. |
47 |
-- |
48 |
Canek Peláez Valdés |
49 |
Posgrado en Ciencia e Ingeniería de la Computación |
50 |
Universidad Nacional Autónoma de México |