> > That IS the problem ...
>
> nope, doesn't seem to be. i just recompiled the kernel (2.2.12 now) with
> unix98 pty support enabled, on the off chance that you were right (even
> though xterm seemed to be trying to access /dev/ttyXX), with the same
> results:
Sorry, you're right. I had misread the original post - the ttypX group has
nothing to do with the Unix98 ptys. It's plain old pseudo-terminals.
> > xterm
>
> /dev/ttyp1: Operation not permitted
Did you try erasing your wtmp/utmp files? There's an issue on
incompatibility (there's even a daemon included with glibc - utmpd IIRC)
in which libc5 applications will break if the utmp is libc6, and
vice-versa. I think I can remember the _same_ problem as you had, that
went away when I killed some files in /var/log
> > w
> 8:10am up 11 min, 2 users, load average: 0.08, 0.09, 0.08
> USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
> root tty1 - 8:02am 7:44 0.17s 0.17s -bash
> damon ttyp2ric :0.0 8:08am 0.00s 29.48s ? -
> damon@odin/08:10:05:~$
Is w libc5 or libc6? What about who?
> any further suggestions?
stracing xterm might give your a hand
> i'm going to try recompiling glibc2 next, just in case... though glibc-2.1
> should be ok, shouldn't it? (that's what i have right now - compiling
> 2.1.1 with gcc-2.95 as i type)
You shouldn't need to recompile glibc2 - I don't think your problem lies
there. It's always nice to install a new glibc, however, specially when
you switch binutils versions.. I had a major crash doing it a while back.
k.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/