| 1 |
On 7 Feb, David Relson wrote: |
| 2 |
> On Sun, 7 Feb 2010 02:20:19 -0800 |
| 3 |
> James Ausmus wrote: |
| 4 |
> |
| 5 |
>> On Sat, Feb 6, 2010 at 8:07 PM, David Relson |
| 6 |
>> <relson@×××××××××××××.com>wrote: |
| 7 |
>> |
| 8 |
>> > On Sat, 6 Feb 2010 19:13:33 -0500 |
| 9 |
>> > Willie Wong wrote: |
| 10 |
>> > |
| 11 |
>> > > On Sat, Feb 06, 2010 at 06:29:27PM -0500, David Relson wrote: |
| 12 |
>> > > > Your replies are much appreciated as we're in an area of Linux |
| 13 |
>> > > > about which I'm poorly informed. |
| 14 |
>> > > > |
| 15 |
>> > > > Output (below) of "rc-status sysinit" indicated devfs stopped, |
| 16 |
>> > > > so I started devfs (which didn't change /dev/pt*), then |
| 17 |
>> > > > restarted udev (which didn't affect /dev/pt*). |
| 18 |
>> > > |
| 19 |
>> > > Right, but can you ssh in to the machine now (or open a terminal |
| 20 |
>> > > emulator in X)? |
| 21 |
>> > > |
| 22 |
>> > > /dev/pts is just the mount point for the devpts pseudo |
| 23 |
>> > > filesystem. In modern versions of linux the pts devices are |
| 24 |
>> > > created on-the-fly when requested (as opposed to other versions |
| 25 |
>> > > and some modern unixes where there will be a fixed number of |
| 26 |
>> > > device nodes under /dev/pts or equivalent). All that just goes to |
| 27 |
>> > > say that if /dev/pts is empty right after you restart the devfs |
| 28 |
>> > > service, it is normal. A device file should be created |
| 29 |
>> > > automatically now when userspace programs demand it. (E.g. if you |
| 30 |
>> > > now ssh in, and if it succeeds, ls /dev/pts should show one |
| 31 |
>> > > entry.) |
| 32 |
>> > > |
| 33 |
>> > > Try it, let me know if the problem is still there. |
| 34 |
>> > |
| 35 |
>> > Nope. Both ssh and X terminal emulators are still broken. No |
| 36 |
>> > change in behavior. |
| 37 |
>> > |
| 38 |
>> > FWIW, most of the entries in /dev are timestamped 02/02 23:34 which |
| 39 |
>> > is when I updated udev earlier this week. Today's upgrade/downgrade |
| 40 |
>> > emerge hasn't affected the timestamps. |
| 41 |
>> > |
| 42 |
>> > A comparison of /etc/udev/rules.d to a saved copy didn't show |
| 43 |
>> > much. The only puzzling difference is: |
| 44 |
>> > --- 90-hal.rules (revision 51) |
| 45 |
>> > +++ 90-hal.rules (working copy) |
| 46 |
>> > @@ -1,2 +1,2 @@ |
| 47 |
>> > # pass all events to the HAL daemon |
| 48 |
>> > -RUN+="socket:/org/freedesktop/hal/udev_event" |
| 49 |
>> > +RUN+="socket:@/org/freedesktop/hal/udev_event" |
| 50 |
>> > |
| 51 |
>> > removing the "@" and restarting udev hasn't helped. Since the rule |
| 52 |
>> > is hal related, I also restarted hald -- which hasn't helped. |
| 53 |
>> > |
| 54 |
>> > |
| 55 |
>> What happens if you do: |
| 56 |
>> |
| 57 |
>> mount -t devpts none /dev/pts |
| 58 |
>> |
| 59 |
>> Does the problem go away? |
| 60 |
>> |
| 61 |
>> -James |
| 62 |
> |
| 63 |
> Eureka! Problem fixed. |
| 64 |
> |
| 65 |
> Looking in /etc/mtab, the last line is: |
| 66 |
> |
| 67 |
> none /dev/pts devpts rw 0 0 |
| 68 |
> |
| 69 |
> Perhaps the mount devpts command should have been issued as part of |
| 70 |
> emerging udev, openrc, or sysinit ??? Should this be reported to |
| 71 |
> b.g.o.?? |
| 72 |
> |
| 73 |
> David |
| 74 |
> |
| 75 |
|
| 76 |
I have the following line in my /etc/fstab (I can't remember if I put it |
| 77 |
there myself or not) |
| 78 |
|
| 79 |
devpts /dev/pts devpts mode=0620,gid=5 0 0 |
| 80 |
|
| 81 |
Since a "mount -a" is issued quite early during boot, this is mounted, |
| 82 |
as well. |
| 83 |
|
| 84 |
Helmut. |
| 85 |
|
| 86 |
-- |
| 87 |
Helmut Jarausch |
| 88 |
|
| 89 |
Lehrstuhl fuer Numerische Mathematik |
| 90 |
RWTH - Aachen University |
| 91 |
D 52056 Aachen, Germany |
Archives