From: David Relson <relson@osagesoftware.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] trouble starting bash
Date: Sat, 6 Feb 2010 23:07:28 -0500 [thread overview]
Message-ID: <20100206230728.6866b21c@osage.osagesoftware.com> (raw)
In-Reply-To: <20100207001333.GA29714@math.princeton.edu>
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.
next prev parent reply other threads:[~2010-02-07 4:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 13:33 [gentoo-user] trouble starting bash David Relson
2010-02-06 15:00 ` Willie Wong
2010-02-06 15:13 ` Willie Wong
2010-02-06 21:24 ` David Relson
2010-02-06 21:08 ` David Relson
2010-02-06 22:27 ` Willie Wong
2010-02-06 23:29 ` David Relson
2010-02-07 0:13 ` Willie Wong
2010-02-07 4:07 ` David Relson [this message]
2010-02-07 10:20 ` James Ausmus
2010-02-07 14:35 ` David Relson
2010-02-07 18:53 ` Willie Wong
2010-02-08 8:46 ` Helmut Jarausch
2010-02-08 9:21 ` Dale
2010-02-06 15:11 ` Willie Wong
2010-02-06 21:41 ` David Relson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100206230728.6866b21c@osage.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox