[linux-help] Re: Printer on Red Hat 6.2

[Steven Saner <ssaner@xxxxxxxxxxxxxxx>]

It looks to me like you don't have parallel port (parport) and line
printer (lp) support compiled into your kernel. Because of that,
installing xwindows is not going to help matters.

The /proc file system is not made up of real files. It is a view into
the internals of the kernel in a way. You can not create directories
and move files around like you can in a file system on disk.

I think you are simply going to have to deal with compiling a kernel,
which is good practice anyway. It is not particularly difficult, but
it does require some work to understand the various steps
involved. The best reference I can refer you to is the Kernel Compile
HOWTO. That is what I used several years ago to figure out how to
configure and compile the kernel the first time.

Now it is possible that you do have parport and lp support compiled
already as kernel modules, but they are not getting loaded. As root,
try typing "lsmod" to get a listing of the currently loaded
modules. Then try typing "modprobe lp". See what happens. Type "lsmod"
again and see if anything has changed. If when you do this things
refering to parport and lp show up, you may then be in business to try
using lpr to print something. If not, you are back to learning how to
compile the kernel.

Perhaps some people familiar with Red Hat can give you better
information than I can.

Steve


On Sun, Oct 01, 2000 at 05:24:30PM -0500, Bruce Bales wrote:
> I found a website that explains that many folks setting up servers didn't 
> want xwindows so RH left it out
> of the regular server set-up.  This site also tells how to add xwindows.  I 
> may have to go ahead and do
> that so that (hopefully) I can use printtool.
> 
> Had hoped I could avoid windows, but that may be the only way I'll get the 
> printer to work.
> 
> I don't understand the /proc directory, but on the Mandrake machine, there is 
> a directory /proc/parport.
> I tried to mkdir to add a parport directory to the RH box, but "permission 
> denied."
> bruce
> 
> 
> >
> >                 In /proc/interrupts, I go straight from
> >                 2 to 5, with no mention of parport any-
> >                 where; 'course, this is RH, too.
> >                 If this same setup worked fine under Man-
> >                 drake (all the same hdwr.) then these lines
> >                 sure seem like the answer, but what puts
> >                 those lines in the boot process that dmesg
> >                 records?
> >                 My dmesg has been non-functional since the
> >                 first of the year (am I the only one who can
> >                 actually claim to have had a Y2K misadventure?)
> >                 All it will say (100+ lines of it) is "VFS:
> >                 Disk change detected on device ide1 (22.64)"
> >                 Not much help...
> >                 You're right; not a single word begins with
> >                 a ~N, although if the whole word...
> > "Become a monk. The food is better
> >  and the hours are no worse."
> >
> > -- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
> > visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi
> 
> 
> -- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
> visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi

-- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi