1 |
On Wed, 30 Jan 2013 22:35:06 -0500 |
2 |
Michael Mol <mikemol@×××××.com> wrote: |
3 |
|
4 |
> So, I botched the upgrade to udev-191. I thought I'd followed the |
5 |
> steps, but I apparently only covered them for one machine, not both. |
6 |
> |
7 |
> The news item instructions specified that I had to remove |
8 |
> udev-postmount from my runlevels. I didn't have udev-postmount in my |
9 |
> runlevels, so I didn't remove it. Turns out, that dictum also applies |
10 |
> to udev-mount. So after removing that[1], I was able to at least boot |
11 |
> again. |
12 |
> |
13 |
> Udev also complained about DEVTMPFS not being enabled in the |
14 |
> kernel.[2] I couldn't get into X, but I could log in via getty and a |
15 |
> plain old vt, so I enabled it, rebuilt the kernel, installed it and |
16 |
> rebooted...and now that's presumably covered. |
17 |
> |
18 |
> I'm now able to get into X, but when I try to run an xterm, it fails. |
19 |
> Checking ~/.xsession_errors, I find: |
20 |
> |
21 |
> xterm: Error 32, error 2: No such file or directory |
22 |
> Reason: get_pty: not enough ptys |
23 |
> |
24 |
> I find this bizarre, as I'd never had any trouble with xterm in this |
25 |
> way before. What'd I do wrong, and how do I recover? I don't trust |
26 |
> emerging at this point; I tried re-emerging udev, and I aborted after |
27 |
> I saw an stderr line about failing to open a pty, even though portage |
28 |
> does quiet builds for parallel building by default...so I doubt |
29 |
> whatever emitted that line on stderr was being properly guarded |
30 |
> against the failure. |
31 |
> |
32 |
> [1] I didn't have a boot cd or similar to work with, so I used the old |
33 |
> init=/bin/sh trick on the command line. That was functional. And then |
34 |
> I tried init=/usr/bin/vim, and things got real. :) |
35 |
> |
36 |
> [2] Sparking a bemused discussion with a friend at tonight's LUG |
37 |
> meeting over the devfs->udev->udev+devtmpfs progression, but that's a |
38 |
> different story. |
39 |
|
40 |
I can't get any kernel >=gentoo-sources-3.7.1 to work properly with |
41 |
vtys either. |
42 |
|
43 |
3.7.1 is fine, anything earlier is fine. |
44 |
I haven't bothered tracking it down further than that (have a severe |
45 |
dose of laziness right now...) |
46 |
|
47 |
What kernel are you running on these affected hosts? |
48 |
|
49 |
-- |
50 |
Alan McKinnon |
51 |
alan.mckinnon@×××××.com |