SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Slackware 11.0; Kubuntu 6.06; OpenBSD 4.0; OS X 10.4.10
Thanks for the suggestions, but an lprng <-> cups mismatch wasn't it.
I removed both cups and lprng, then reinstalled cups. Tried to start cups using /etc/rc.d/rc.cups. No go. Still got the error 98.
So, I thought I would reboot and see if that did anything. (I normally don't reboot to fix problems - this isn't a Windows box - and sometimes it can make things worse. Anyway...) While the machine was booting up and still in BIOS phase, I realized that the only thing that had changed on this machine recently other than the new kernel was the Terrarec Cinergy T2 USB DBV-T adapter I attached to it. So, I pulled it. Machine booted, and cups started normally. I printed something to make sure.
Then I stuck the T2 back in and rebooted. Cups refused to start the scheduler - error 98. I pulled the T2 again, and then tried to start cups without rebooting. No go.
Rebooted. Cups started again like a charm.
Therefore, I believe the problem I am having has to do with the Cinergy T2 and some conflict with cups. I just plugged in the adapter, and cups still prints, so it either has to do with having the adapter plugged in during boot or with something I haven't discovered yet. (Udev/hotplug seem like good suspects.) I guess I will watch some TV and then see if I can print.