man broken in 2.6.9?
 

Is man working for those of you who've upgraded to 2.6.9? It's not for me.

I get:
Somebody on alt.os.linux.slackware said to disable udev, but that didn't do the trick for me.

Any ideas?

man is working fine for me. I don't see how you could break it through a kernel compile.

Disabling udev did finally bring man back to life, but I had to reboot first.

The way I was told to disable udev was: as root, "chmod -x /etc/rc.d/rc.udev".

Is there a better way? I confess I don't know what udev is, but I hate to lose it just so I can have man working.

If I understood correctly, it has to do with a goofed up udev rule. If that's the case, what I'm trying to find out is if udev really has to be disabled, or if the rule can be fixed, or if I can just update udev.

Somebody said a flakey version of udev.rules was circulating on current for a while, but is supposed to be fixed now. Maybe this crept into my setup somehow.

Nobody else has seen this? There are several reports on the Slack NG. I assumed it was connected with the kernel compile, since man worked for me before. One guy reported it after upgrading from 2.4.x to 2.6.9. I went form 2.6.7 to 2.6.9. OTOH, I did do a swaret --upgrade a few days ago, so maybe it happened then rather than when I installed the new kernel.

When you upgrade, do you locate all .new conf files and upgrade config files from them ?

Umm, not intentionally, no. I just let swaret do its thing by using "swaret --upgrade -a". Should I have intervened?

he means after each upgrade you should search for all the new config files(usually like xxxx.conf.new). They don't like to overwrite old conf files automatically to prevent breaking some vital configs. Sometimes they have important info for new installs though.

Just noticed that man is broken for me too after upgrading to 2.6.9 so I tried booting up the "old" 2.6.8.1 kernel and man was working again. I didn't change anything before/after upgrading the kernel so it must be kernel related, if not please correct me, I'm still really new to Linux.

EDIT: Disabling udev as suggested solved the problem in 2.6.9.

This is from someone on alt.os.linux.slackware.

You can also open /etc/udev/rules.d/udev.rules and see if you have this line:

If so, then the "tty/s%n" is wrong; it should be "pty/s%n".

After you edit the file, you can reenable udev:

"chmod +x /etc/rc.d/rc.udev"

[Somebody might want to check me out on this. I'm a Slack noob and don't want to pretend to know what I'm talking about ...]

Guess I'll wait until 2.6.9.1 :)

Kent

Guess it wouldn't hurt to try, after all it can't get any worse then that it stops working at all ;)

From everything I've read, this particular problem isn't related to the new kernel but rather to a goofed up upgrade of udev. In my case, the problem was easy to fix, and the kernel hasn't give me any trouble at all.

Thanks, clawhead, your fix worked like a charm. My "less" command also broke after the 2.6.9 upgrade, and your suggestion fixed that as well.

thanks clawhead. the fix you posted was just the ticket. my more, less, cat, man, etc... did not work after the upgrade to 2.6.9.

I also was not able to ssh out to another machine because of an ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory error and it fixed that as well.

@brodieman

look what i've wrote here:
http://www.linuxquestions.org/questi...10#post1249510