On Sat, 6 Feb 2010 19:13:33 -0500
Willie Wong wrote:

> On Sat, Feb 06, 2010 at 06:29:27PM -0500, David Relson wrote:
> > Your replies are much appreciated as we're in an area of Linux about
> > which I'm poorly informed.
> >
> > Output (below) of "rc-status sysinit" indicated devfs stopped, so I
> > started devfs (which didn't change /dev/pt*), then restarted udev
> > (which didn't affect /dev/pt*).
>
> Right, but can you ssh in to the machine now (or open a terminal
> emulator in X)?
>
> /dev/pts is just the mount point for the devpts pseudo filesystem. In
> modern versions of linux the pts devices are created on-the-fly when
> requested (as opposed to other versions and some modern unixes where
> there will be a fixed number of device nodes under /dev/pts or
> equivalent). All that just goes to say that if /dev/pts is empty
> right after you restart the devfs service, it is normal. A device file
> should be created automatically now when userspace programs demand it.
> (E.g. if you now ssh in, and if it succeeds, ls /dev/pts should show
> one entry.)
>
> Try it, let me know if the problem is still there.

Nope. Both ssh and X terminal emulators are still broken. No change
in behavior.

FWIW, most of the entries in /dev are timestamped 02/02 23:34 which is
when I updated udev earlier this week. Today's upgrade/downgrade emerge
hasn't affected the timestamps.

A comparison of /etc/udev/rules.d to a saved copy didn't show
much. The only puzzling difference is:
--- 90-hal.rules (revision 51)
+++ 90-hal.rules (working copy)
@@ -1,2 +1,2 @@
# pass all events to the HAL daemon
-RUN+="socket:/org/freedesktop/hal/udev_event"
+RUN+="socket:@/org/freedesktop/hal/udev_event"

removing the "@" and restarting udev hasn't helped. Since the rule is
hal related, I also restarted hald -- which hasn't helped.

On Sat, Feb 6, 2010 at 8:07 PM, David Relson <relson@osagesoftware.com> wrote:

On Sat, 6 Feb 2010 19:13:33 -0500

Willie Wong wrote:



> On Sat, Feb 06, 2010 at 06:29:27PM -0500, David Relson wrote:

> > Your replies are much appreciated as we're in an area of Linux about

> > which I'm poorly informed.

> >

> > Output (below) of "rc-status sysinit" indicated devfs stopped, so I

> > started devfs (which didn't change /dev/pt*), then restarted udev

> > (which didn't affect /dev/pt*).

>

> Right, but can you ssh in to the machine now (or open a terminal

> emulator in X)?

>

> /dev/pts is just the mount point for the devpts pseudo filesystem. In

> modern versions of linux the pts devices are created on-the-fly when

> requested (as opposed to other versions and some modern unixes where

> there will be a fixed number of device nodes under /dev/pts or

> equivalent). All that just goes to say that if /dev/pts is empty

> right after you restart the devfs service, it is normal. A device file

> should be created automatically now when userspace programs demand it.

> (E.g. if you now ssh in, and if it succeeds, ls /dev/pts should show

> one entry.)

>

> Try it, let me know if the problem is still there.



Nope. *Both ssh and X terminal emulators are still broken. *No change

in behavior.



FWIW, most of the entries in /dev are timestamped 02/02 23:34 which is

when I updated udev earlier this week. Today's upgrade/downgrade emerge

hasn't affected the timestamps.



A comparison of /etc/udev/rules.d to a saved copy didn't show

much. *The only puzzling difference is:

*--- 90-hal.rules * * *(revision 51)

* +++ 90-hal.rules * * (working copy)

* @@ -1,2 +1,2 @@

* *# pass all events to the HAL daemon

* -RUN+="socket:/org/freedesktop/hal/udev_event"

* +RUN+="socket:@/org/freedesktop/hal/udev_event"



removing the "@" and restarting udev hasn't helped. *Since the rule is

hal related, I also restarted hald -- which hasn't helped.



What happens if you do:

mount -t devpts none /dev/pts

Does the problem go away?

-James

On Sun, 7 Feb 2010 02:20:19 -0800
James Ausmus wrote:

> On Sat, Feb 6, 2010 at 8:07 PM, David Relson
> <relson@osagesoftware.com>wrote:
>
> > On Sat, 6 Feb 2010 19:13:33 -0500
> > Willie Wong wrote:
> >
> > > On Sat, Feb 06, 2010 at 06:29:27PM -0500, David Relson wrote:
> > > > Your replies are much appreciated as we're in an area of Linux
> > > > about which I'm poorly informed.
> > > >
> > > > Output (below) of "rc-status sysinit" indicated devfs stopped,
> > > > so I started devfs (which didn't change /dev/pt*), then
> > > > restarted udev (which didn't affect /dev/pt*).
> > >
> > > Right, but can you ssh in to the machine now (or open a terminal
> > > emulator in X)?
> > >
> > > /dev/pts is just the mount point for the devpts pseudo
> > > filesystem. In modern versions of linux the pts devices are
> > > created on-the-fly when requested (as opposed to other versions
> > > and some modern unixes where there will be a fixed number of
> > > device nodes under /dev/pts or equivalent). All that just goes to
> > > say that if /dev/pts is empty right after you restart the devfs
> > > service, it is normal. A device file should be created
> > > automatically now when userspace programs demand it. (E.g. if you
> > > now ssh in, and if it succeeds, ls /dev/pts should show one
> > > entry.)
> > >
> > > Try it, let me know if the problem is still there.
> >
> > Nope. Both ssh and X terminal emulators are still broken. No
> > change in behavior.
> >
> > FWIW, most of the entries in /dev are timestamped 02/02 23:34 which
> > is when I updated udev earlier this week. Today's upgrade/downgrade
> > emerge hasn't affected the timestamps.
> >
> > A comparison of /etc/udev/rules.d to a saved copy didn't show
> > much. The only puzzling difference is:
> > --- 90-hal.rules (revision 51)
> > +++ 90-hal.rules (working copy)
> > @@ -1,2 +1,2 @@
> > # pass all events to the HAL daemon
> > -RUN+="socket:/org/freedesktop/hal/udev_event"
> > +RUN+="socket:@/org/freedesktop/hal/udev_event"
> >
> > removing the "@" and restarting udev hasn't helped. Since the rule
> > is hal related, I also restarted hald -- which hasn't helped.
> >
> >
> What happens if you do:
>
> mount -t devpts none /dev/pts
>
> Does the problem go away?
>
> -James

Eureka! Problem fixed.

Looking in /etc/mtab, the last line is:

none /dev/pts devpts rw 0 0

Perhaps the mount devpts command should have been issued as part of
emerging udev, openrc, or sysinit ??? Should this be reported to
b.g.o.??

David

On Sun, Feb 07, 2010 at 09:35:54AM -0500, David Relson wrote:
> Looking in /etc/mtab, the last line is:
>
> none /dev/pts devpts rw 0 0
>
> Perhaps the mount devpts command should have been issued as part of
> emerging udev, openrc, or sysinit ??? Should this be reported to
> b.g.o.??

Odd, that's one of the two things /etc/init.d/devfs is supposed to
do. (The other is to mount tmpfs.) The whole point of that script is
to provide those two filesystems in case the user "forgot" to specify
them in /etc/fstab.

If this is reproducible (say, after next reboot devpts still doesn't
come up, while devfs is started), then something is wrong. Filing a
bug report likely won't help because it works on mostly everyone
else's system; you should probably ping the list again to find out
what the source of the problem is.

A work around would be to just add the appropriate line to /etc/fstab.
the devfs script is smart enough to check if the devpts and tmpfs are
already mounted, so it should break anything additional.

Cheers,

W
--
Willie W. Wong wwong@math.princeton.edu
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire
et vice versa ~~~ I. Newton

On 7 Feb, David Relson wrote:
> On Sun, 7 Feb 2010 02:20:19 -0800
> James Ausmus wrote:
>
>> On Sat, Feb 6, 2010 at 8:07 PM, David Relson
>> <relson@osagesoftware.com>wrote:
>>
>> > On Sat, 6 Feb 2010 19:13:33 -0500
>> > Willie Wong wrote:
>> >
>> > > On Sat, Feb 06, 2010 at 06:29:27PM -0500, David Relson wrote:
>> > > > Your replies are much appreciated as we're in an area of Linux
>> > > > about which I'm poorly informed.
>> > > >
>> > > > Output (below) of "rc-status sysinit" indicated devfs stopped,
>> > > > so I started devfs (which didn't change /dev/pt*), then
>> > > > restarted udev (which didn't affect /dev/pt*).
>> > >
>> > > Right, but can you ssh in to the machine now (or open a terminal
>> > > emulator in X)?
>> > >
>> > > /dev/pts is just the mount point for the devpts pseudo
>> > > filesystem. In modern versions of linux the pts devices are
>> > > created on-the-fly when requested (as opposed to other versions
>> > > and some modern unixes where there will be a fixed number of
>> > > device nodes under /dev/pts or equivalent). All that just goes to
>> > > say that if /dev/pts is empty right after you restart the devfs
>> > > service, it is normal. A device file should be created
>> > > automatically now when userspace programs demand it. (E.g. if you
>> > > now ssh in, and if it succeeds, ls /dev/pts should show one
>> > > entry.)
>> > >
>> > > Try it, let me know if the problem is still there.
>> >
>> > Nope. Both ssh and X terminal emulators are still broken. No
>> > change in behavior.
>> >
>> > FWIW, most of the entries in /dev are timestamped 02/02 23:34 which
>> > is when I updated udev earlier this week. Today's upgrade/downgrade
>> > emerge hasn't affected the timestamps.
>> >
>> > A comparison of /etc/udev/rules.d to a saved copy didn't show
>> > much. The only puzzling difference is:
>> > --- 90-hal.rules (revision 51)
>> > +++ 90-hal.rules (working copy)
>> > @@ -1,2 +1,2 @@
>> > # pass all events to the HAL daemon
>> > -RUN+="socket:/org/freedesktop/hal/udev_event"
>> > +RUN+="socket:@/org/freedesktop/hal/udev_event"
>> >
>> > removing the "@" and restarting udev hasn't helped. Since the rule
>> > is hal related, I also restarted hald -- which hasn't helped.
>> >
>> >
>> What happens if you do:
>>
>> mount -t devpts none /dev/pts
>>
>> Does the problem go away?
>>
>> -James
>
> Eureka! Problem fixed.
>
> Looking in /etc/mtab, the last line is:
>
> none /dev/pts devpts rw 0 0
>
> Perhaps the mount devpts command should have been issued as part of
> emerging udev, openrc, or sysinit ??? Should this be reported to
> b.g.o.??
>
> David
>

I have the following line in my /etc/fstab (I can't remember if I put it
there myself or not)

devpts /dev/pts devpts mode=0620,gid=5 0 0

Since a "mount -a" is issued quite early during boot, this is mounted,
as well.

Helmut.

--
Helmut Jarausch

Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany

chrome://messenger/locale/messengercompose/composeMsgs.properties:

On 7 Feb, David Relson wrote:


On Sun, 7 Feb 2010 02:20:19 -0800
James Ausmus wrote:



On Sat, Feb 6, 2010 at 8:07 PM, David Relson
<relson@osagesoftware.com>wrote:



On Sat, 6 Feb 2010 19:13:33 -0500
Willie Wong wrote:



On Sat, Feb 06, 2010 at 06:29:27PM -0500, David Relson wrote:


Your replies are much appreciated as we're in an area of Linux
about which I'm poorly informed.

Output (below) of "rc-status sysinit" indicated devfs stopped,
so I started devfs (which didn't change /dev/pt*), then
restarted udev (which didn't affect /dev/pt*).


Right, but can you ssh in to the machine now (or open a terminal
emulator in X)?

/dev/pts is just the mount point for the devpts pseudo
filesystem. In modern versions of linux the pts devices are
created on-the-fly when requested (as opposed to other versions
and some modern unixes where there will be a fixed number of
device nodes under /dev/pts or equivalent). All that just goes to
say that if /dev/pts is empty right after you restart the devfs
service, it is normal. A device file should be created
automatically now when userspace programs demand it. (E.g. if you
now ssh in, and if it succeeds, ls /dev/pts should show one
entry.)

Try it, let me know if the problem is still there.


Nope. Both ssh and X terminal emulators are still broken. No
change in behavior.

FWIW, most of the entries in /dev are timestamped 02/02 23:34 which
is when I updated udev earlier this week. Today's upgrade/downgrade
emerge hasn't affected the timestamps.

A comparison of /etc/udev/rules.d to a saved copy didn't show
much. The only puzzling difference is:
--- 90-hal.rules (revision 51)
+++ 90-hal.rules (working copy)
@@ -1,2 +1,2 @@
# pass all events to the HAL daemon
-RUN+="socket:/org/freedesktop/hal/udev_event"
+RUN+="socket:@/org/freedesktop/hal/udev_event"

removing the "@" and restarting udev hasn't helped. Since the rule
is hal related, I also restarted hald -- which hasn't helped.




What happens if you do:

mount -t devpts none /dev/pts

Does the problem go away?

-James


Eureka! Problem fixed.

Looking in /etc/mtab, the last line is:

none /dev/pts devpts rw 0 0

Perhaps the mount devpts command should have been issued as part of
emerging udev, openrc, or sysinit ??? Should this be reported to
b.g.o.??

David



I have the following line in my /etc/fstab (I can't remember if I put it
there myself or not)

devpts /dev/pts devpts mode=0620,gid=5 0 0

Since a "mount -a" is issued quite early during boot, this is mounted,
as well.

Helmut.




Here's something odd, I don't have that line in mine.

root@smoker / # cat /etc/fstab | grep /dev/pts
root@smoker / #

However it is mounted:

root@smoker / # mount | grep /dev/pts
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
root@smoker / #

Mine is a old install with a really old fstab so that may matter. I'm
still on the old baselayout and openrc too.


Dale

:-) :-)