From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ne4Gf-0002b2-9P for garchives@archives.gentoo.org; Sun, 07 Feb 2010 10:21:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 32829E09BD; Sun, 7 Feb 2010 10:20:20 +0000 (UTC) Received: from mail-gx0-f211.google.com (mail-gx0-f211.google.com [209.85.217.211]) by pigeon.gentoo.org (Postfix) with ESMTP id 0AAA9E09BD for ; Sun, 7 Feb 2010 10:20:20 +0000 (UTC) Received: by gxk3 with SMTP id 3so1686900gxk.6 for ; Sun, 07 Feb 2010 02:20:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=LfTlg0cckN24pMrhWD+HoiNw9NlQhavExp6MFdu1XjY=; b=KiwYXUo8XB/+NsnM16q3GWi4bfa3fiIh6P92b0sJj8YwfiP2EHOiTCxyKw4w3s++xX NIZEsePGyl/RHI7D6PqApgkCYzBMzXoQ33MNaRYi9KCsilE1bTMeeRCavkFoU/ccJHeW md4drKVWIYvIgy4Inh5/e6QfopRX5xed5WrZg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=wSjGqSwHulc5UgzHu5ePCCDb8h5Bb0n+adtNZJkMT3BmBlgXUQ/TJw4Z61TY+pCqMj iGQHrowfyW88AXR4OTnLnV6f8SKZL+bQa39DfQe8fyhJnpYK13HdkV9XjpmIP5rKqhz6 i4wgLIFzXshMfGGLZ00YtgONiwHMZSTxCbLOU= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.91.193.19 with SMTP id v19mr4485589agp.4.1265538019605; Sun, 07 Feb 2010 02:20:19 -0800 (PST) In-Reply-To: <20100206230728.6866b21c@osage.osagesoftware.com> References: <20100206151107.GB4059@math.princeton.edu> <20100206164122.7e71bc88@osage.osagesoftware.com> <20100206083344.2ff96f9c@osage.osagesoftware.com> <20100206150033.GA4059@math.princeton.edu> <20100206160858.5b36abcf@osage.osagesoftware.com> <20100206222714.GA25438@math.princeton.edu> <20100206182927.4dabf1a3@osage.osagesoftware.com> <20100207001333.GA29714@math.princeton.edu> <20100206230728.6866b21c@osage.osagesoftware.com> Date: Sun, 7 Feb 2010 02:20:19 -0800 Message-ID: Subject: Re: [gentoo-user] trouble starting bash From: James Ausmus To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=0016e64713b21bbf6f047f000869 X-Archives-Salt: bf7210ef-ec6f-4527-95a4-9935bdcb62a8 X-Archives-Hash: f1e247ab1a1879efb98f79f03173c86b --0016e64713b21bbf6f047f000869 Content-Type: text/plain; charset=ISO-8859-1 On Sat, Feb 6, 2010 at 8:07 PM, David Relson 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 --0016e64713b21bbf6f047f000869 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Sat, Feb 6, 2010 at 8:07 PM, David Re= lson <rels= on@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 Linu= x about
> > which I'm poorly informed.
> >
> > Output (below) of "rc-status sysinit" indicated devfs s= topped, 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<= br> > 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. =A0Both ssh and X terminal emulators are still broken. =A0No ch= ange
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. =A0The only puzzling difference is:
=A0--- 90-hal.rules =A0 =A0 =A0(revision 51)
=A0 +++ 90-hal.rules =A0 =A0 (working copy)
=A0 @@ -1,2 +1,2 @@
=A0 =A0# pass all events to the HAL daemon
=A0 -RUN+=3D"socket:/org/freedesktop/hal/udev_event"
=A0 +RUN+=3D"socket:@/org/freedesktop/hal/udev_event"

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


What happens if you do:

mount -t devpts no= ne /dev/pts

Does the problem go away?

-James
--0016e64713b21bbf6f047f000869--