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.
I have read some previous posts, but they don't seem to deal specifically with my issue...
Steps I followed:
First, I modprobed usbcore, printer and usb-uhci. Then, I ran the ptal-setup program that came with the HP printer drivers. It located my HP Photosmart 1115 connected via USB cable, and made it my default. I've echo'd it and gotten neat serial numbers, and everything seems to be communicating fine.
As I was installing the drivers, I got an error message about not being able to find an init.d script. The HP driver documentation seems to take this issue seriously. Apparently, I must modify the init.d script for each runlevel to make sure that the ptal-init script is run BEFORE the print-spooler, otherwise my system will hang when I try to boot. As I was perusing the /etc/rc.d directory, I noticed a filed called "rc.sysvinit" that said that Slackware did not use SystemV-style init file. Hence the error when I compiled the driver, right? But, apparently this "rc.sysvinit" file exists if some piece of commercial software needs it to.
1. Is there another way to make sure I run the ptal-init script BEFORE the print spooler on bootup besides using a SysV-style init script?
if no, then
2. How do I modify the rc.sysvinit file to suit my purposes?