Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
This is not STRICTLY an installation issue, but it certainly is hampering my installation effort.
I am developing or rather rewriting an application to run on linux (the original was DOS based, written in Clipper). Outside of my control, the chosen language has been FlagShip, a unix based system, which runs a large percentage of Clipper Code.
Anyway, started off on Red Hat 9, but for a number of reasons, it was decided to change to Slackware 10. This has been working well until my current showstopper.
The FlagShip Printing System is simple, as i understand it, based around lpd. I was able to set up CUPS on Red Hat to emulate LPD (CUPS-LPD, launched from XINETD) and all way well.
On my Slackware box, however, (after I enabled the parallel port) I was able to install a local DOT MATRIX printer, with a RAW print queue, and send it a test page.
BUT, when I attempt the following : lp -d locdot /etc/passwd
I get the following errors :
Status Information, attempt 1 of 3:
sending job 'root@thebitch+666' locdot @localhost
connecting to 'localhost', attempt 1
cannot open connection to localhost - No such file or directory
Make sure the remote host supports the LPD protocol
Waiting 10 seconds before retry
Problem is, I am not even aiming at a remote host - this attempts and fails 3 times - bang I am stumped.
I imagine there is some stupid, arcane file that I have to alter, but i simply have no idea where to look. So if anyone can point me in the right direction, I would be eternally grateful.
thanking you kindly sir, you nailed it - i also needed to change lpr -> lpr-cups,
but once I had, voila, thrings sprung gleefully from the printing device.
And I have licked the local printing problem - but now I cannot connect to a remote printer - I have tried all I can but CUPS seems adamant that I should not be able to do a simple maping to a remote printer. Well to be fair, it stumps me - It asks for a server, which I think I know the obvious answer to, & a print queue - the default being "/print/queue1" which apparently doesnt work. So how do I know what the print queue should be?
The Web interface (localhost:631) is no more helpful, it requires a URI, how should I know what that should be??
Sheeesh, why on earth does it all have to be so ridiculously complicated? Please help?!