Re: 2.6.21-rc6-mm1

[J.A. MagallÃn]

On Tue, 24 Apr 2007 04:58:01 -0700, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:

> On Tue, 24 Apr 2007 10:10:41 +0200 "J.A. MagallÃn" <jamagallon@xxxxxxx> wrote:
> 
> > On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> > 
> > > 
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
> > > 
> > > 
> > > - Lots of x86 updates
> > > 
> > 
> > Has somthing related with PTY's changed in this kernel ?
> 
> Not as far as I know, but there were some kobject_uevent changes which
> might have caused udev upcalls to break.  Perhaps.
> 
> > I have to enable legacy PTY handling in a couple boxes to get ssh working.
> > If not, I had openpty() errors and nor sshd nor virtual terminals (aterm) were
> > able to get a terminal.
> 
> I have CONFIG_PM_LEGACY unset in at least one of my test configs and it
> works OK here.
> 
> > User space (udev) is the same in three boxes and one works and two fail.
> > I had /dev/ptmx everywhere and /dev/pts mounted
> > 
> > Any idea ?
> 
> Nope.  Can you please check 2.6.21-rc7-mm1, see if that fixed it?  If so,
> it might have been the kobject_uevent thing.
> 

I will, thanks.

A couple questions (as far as udev behaviour is sooooooo distro dependent):
- What should I have in /dev if I don't use legacy ptys ? As I understand
  it, only /dev/ptmx and /dev/pts/*, no /dev/tty* nor /dev/pty* ?
- If my setup, for whatever strange reasons has /dev/tty* stored anyware
  (/dev/.udev, links.conf...) and they get created, I supose that opening
  /dev/tty will give a ENODEV ?

TIA

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2008.0 (Cooker) for i586
Linux 2.6.20-jam10 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #4 SMP PREEMPT
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/