Re: Whats happened to my psuedo ttys
On Friday 27 Apr 2007, Florian Kulzer wrote:
> On Thu, Apr 26, 2007 at 21:39:41 +0100, Alan Chandler wrote:
> > On Thursday 26 Apr 2007, Scott Gifford wrote:
> > > Sorry to jump in on an old discussion, but...
> > >
> > >
> > > Alan Chandler writes:
> > >
> > > [...]
> > >
> > > > OK, I think its the latest kernel and some interaction with my
> > > > motherboard. I just booted a hand compiled 2.6.19 (originally
> > > > done when Debian was on 2.6.18 - because was needed to load the
> > > > AGPGART module) and I've got my ptys back.
> > > >
> > > > Looks to be a problem with 2.6.20.
> > >
> > > Is it possible that konsole is using "legacy PTYs", and you
> > > compiled one kernel with "CONFIG_LEGACY_PTYS=y" and the other
> > > without?
> >
> > Well I only compiled the one that works - and yes it has
> > CONFIG_LEGACY_PTYS=y.
> >
> > 2.6.20 is the standard debian package (2.6.20-1-686), and its the
> > one that doesn't work. How do I find out what its compiled with?
>
> grep PTYS /boot/config-2.6.20-1-686
>
> Here is what I get:
>
> $ grep PTYS /boot/config-2.6.20-1-amd64
> CONFIG_UNIX98_PTYS=y
> # CONFIG_LEGACY_PTYS is not set
My system is like that also. This looks like it could be a problem.
Is there a module I should load perhaps
>
> I have no problems with my ptys or konsole, so the legacy option does
> not seem to be critical. (I would expect that it is the same for a
> 32-bit system.)
>
> > I also notice that when I load up 2.6.20 kernel bootlogd fails to
> > start with a message related to having problems with /dev/ttyzf.
> > Looks like a similar issue to me.
No comment on this bit?
--
Alan Chandler
http://www.chandlerfamily.org.uk
Reply to: