On Tuesday 04 January 2005 00:30, der.hans wrote: > Am 03. Jan, 2005 schwätzte Nathan England so: > I can't remember, are you using stock kernels from the distro or compiling > them yourself? I think you've done a bit of the latter. You're using > debian, right? > I'm using slackware, this box is 10.0 > Have you checked the bug tracking system for whatever distro you're using? > I presume you have, but don't remember you specifically mentioning it. > I have checked the limited resources for slackers, many seem to have the problem, but so far, lots of different fixes, none work for me! Typical... lol > Have you compared the kernel configs between the two kernels? > I used kompare to compare the differences, I love that program... There were only minor differences that I felt would make a difference, but I will probably begin investigating them soon. > I see debian packages for 2.6.7 and 2.6.8 on 686 turned off > CONFIG_CLEAN_COMPILE, whatever that is. Hmm, CONFIG_BROKEN was turned > on... > > Looks like lots of changes. > > Have you looked at the kernel changelog to see if anything obvious pops > up? > Nothing obvious to me. It's interesting that you said libc incompatibility, that was one of my first thoughts, but I have not seen anyone else say that in any of the sites I've read. > > I can't use man either. But in KDE I can use man:/whatever in Konq and it > > works out for now. > > That is strange. > > libc incompatability? > > > any other ideas I can try? The only difference is the kernel... > > And the initrd. Can you peel them apart and see if they have the same > modules? Maybe make a new initrd for 2.6.7 ( after backing up the current > one ) to see if new initrd tools installed after you installed 2.6.7 is > the cause. > I don't use an initrd. I never have. I compile most everything my laptop needs into the kernel, except pcmcia drivers and usb drivers and removeable stuff like that. If it's built in, I make it mono. Nathan > ciao, > > der.hans > > > Nathan > > > > On Monday 03 January 2005 00:22, der.hans wrote: > > > Am 29. Dec, 2004 schwätzte Nathan England so: > > > > > > moin, moin Nathan, > > > > > > did you get this resolved? > > > > > > ciao, > > > > > > der.hans > > > > > > > None of that worked. I can't ssh as root either. I get permission > > > > denied. The only option that works is if I ssh to someplace that > > > > already has my id_dsa.pub key. > > > > > > > > Otherwise, it's a no go. > > > > > > > > Thanks though! > > > > > > > > Nathan > > > > > > > > On Wednesday 29 December 2004 13:19, Kevin Geiss wrote: > > > > > it's probably a permissions error on /dev/tty > > > > > > > > > > the error sounded vaguely familiar to me, so I searched on the > > > > > gentoo forums. > > > > > > > > > > check out this thread: > > > > > > > > > > http://forums.gentoo.org/viewtopic.php?t=102463&highlight=sshaskpas > > > > >s > > > > > > > > > > hth > > > > > > > > > > On Dec 28, 2004, at 6:53 AM, Nathan England wrote: > > > > > > Anyone having trouble using sshd and any kernels over 2.6.7 ? > > > > > > I've read some discussion about it, but nothing so far helps my > > > > > > problem of not > > > > > > being able to connect to anything... > > > > > > > > > > > > I have a couple servers where I have my id_rsa.pub file included > > > > > > in the authorized keys and I can log in as normal, but when a > > > > > > password is required, > > > > > > it says: > > > > > > > > > > > > nathan@deadsoul:~$ ssh nathan@fallout > > > > > > ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or > > > > > > directory Permission denied, please try again. > > > > > > ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or > > > > > > directory Permission denied, please try again. > > > > > > ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or > > > > > > directory Permission denied > > > > > > (publickey,password,keyboard-interactive). > > > > > > > > > > > > > > > > > > But under kernel 2.6.7 it works fine. > > > > > > Also, when I try to start sshd under 2.6.10 it says it can't find > > > > > > the file /etc/ssh/sshd_config > > > > > > which doesn't exist, but under 2.6.7 it works okay, not asking > > > > > > for the file. > > > > > > > > > > > > I've tried upgraded packages, I've tried removing the slack pack > > > > > > and installing from source... nothing seems to work. Only going > > > > > > backwards in the > > > > > > kernel tree... > > > > > > > > > > > > Any ideas? > > > > > > > > > > > > Nathan > > > > > > --------------------------------------------------- > > > > > > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > > > > > > To subscribe, unsubscribe, or to change you mail settings: > > > > > > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > > > > > > > > > > --------------------------------------------------- > > > > > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > > > > > To subscribe, unsubscribe, or to change you mail settings: > > > > > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > > > > > > > > --------------------------------------------------- > > > > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > > > > To subscribe, unsubscribe, or to change you mail settings: > > > > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > > > > --------------------------------------------------- > > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > > To subscribe, unsubscribe, or to change you mail settings: > > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change you mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss