Gentoo Archives: gentoo-user

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