SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: 3rd electron on the left getting mugged by the nutrinos at Quarks
Distribution: Pop_OS
Posts: 140
Rep:
Man Page Blues & Errors
Straight to the point, I'm getting this error message after I open any man page and it closes: [pts/1][19:53][gelnven@gelnven][~] man man
gunzip: stdout: Broken pipe
gunzip: stdout: Broken pipe
grotty:<standard input>:4212:fatal error: output error
I have found some references to some errors with 2.6.x kernel and they requesting to make changes in the /etc/udev/rules.d file. Mine is already running with the correct entries:
# pty devices
KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k"
KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k"
Another reference talks about disk space. At present this is not an issue: [pts/1][19:53][gelnven@gelnven][~] df -h | sort
/dev/hda1 23M 8.5M 13M 41% /boot
/dev/hda2 5.6G 2.8G 2.9G 50% /
/dev/hda3 2.8G 1.6G 1.1G 60% /home
/dev/hda5 628M 370M 259M 59% /usr/local
Googling hasn't been much help either, or at least I'm not looking for the right thing in the right way.
Any input on this would be greatly appreciated. I am running kernel 2.6.8.1 on Slackware 10.0
Originally posted by Imyrryr Straight to the point, I'm getting this error message after I open any man page and it closes: [pts/1][19:53][gelnven@gelnven][~] man man
gunzip: stdout: Broken pipe
gunzip: stdout: Broken pipe
grotty:<standard input>:4212:fatal error: output error
I have found some references to some errors with 2.6.x kernel and they requesting to make changes in the /etc/udev/rules.d file. Mine is already running with the correct entries:
# pty devices
KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k"
KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k"
Another reference talks about disk space. At present this is not an issue: [pts/1][19:53][gelnven@gelnven][~] df -h | sort
/dev/hda1 23M 8.5M 13M 41% /boot
/dev/hda2 5.6G 2.8G 2.9G 50% /
/dev/hda3 2.8G 1.6G 1.1G 60% /home
/dev/hda5 628M 370M 259M 59% /usr/local
Googling hasn't been much help either, or at least I'm not looking for the right thing in the right way.
Any input on this would be greatly appreciated. I am running kernel 2.6.8.1 on Slackware 10.0
Location: 3rd electron on the left getting mugged by the nutrinos at Quarks
Distribution: Pop_OS
Posts: 140
Original Poster
Rep:
Thank you very much that seemed to fix it right up. Every time I think I've got things down pat. something new comes along and I get to be brought back to the level of newbie status.
Thank you for your prompt reply and very useful solution.
Dont' feel bad, I spent nearly a day trying to figure out what was wrong with man after I went from 2.4.26 to 2.6.9. I finally compared the udev versions between Slack 10.0 and that which was on the udev site. To my surprise it was nearly 20 versions behind, I updated udev and that solved my problem. I also learned that the 2.6.x Kernel requires udev to be up to date.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.