Bret Hughes wrote:
>
> "Rev. David P. Giffen" wrote:
>
> > I tried what it said in Red Hat Linux 6.1 Gotchas and Workarounds.
> >
> > ----------------------------------------------------------------------
> > 6.19 Problems with Printer not being detected
> >
> > Problem:
> >
> > For several kinds of systems, local printers are not found when
> > printtool is searching for > local printers. You should be presented
> > with an error saying no local printer was found.
> >
> > Fix:
> >
> > Get the the latest modutils RPM from
> > ftp://rawhide.redhat.com/pub/rawhide/i386/RedHat/RPMS/.
> >
> > For detailed instructions on how to install a package, please see our
> > FAQ.
> >
> > Alternatively, you can add
> >
> > alias parport_lowlevel parport_pc
> >
> > to your
> >
> > /etc/conf.modules file.
> >
> > Then run /sbin/rmmod lp, and start printtool.
> > ----------------------------------------------------------------------
> >
> > The latest modutil RPM is modutil-2.3.14-2.i386.rpm. I thought "cool,
> > download the package and load it, problem solved." However when I try to
> > load the package using the rpm -Uvh modutil-2.3.14-2.i386.rpm command. I
> > get the following error. Only packages with major numbers <=3 are
> > supported by this version of RPM error: modutil-2.3.14-2.i386.rpm cannot
> > be installed. Bum!
>
> Go get the rpm version 3.0.5 rpm and upgrade rpm. There have been a lot of
> probs with this
>
> > So I try the alternative. Hacked the conf.modules.
> > and ran the command. This cased so many problems that I had to
> > completely reload Linux to fix it.
>
> wow! I can't imagine what you could do to conf modules to necessitate a
> reinstall. A good practiice is to copy a file to a backup before editing
> it so that you can always go back. I usually start with cp filetobeedited
> filetobeedited.orig
>
> Did you do this and still had to reinstall? I am curious because if so I
> will be more carefull what I do to conf.modules in the future.
>
> Bret
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
Actually, That is standard change control practice with me as well.
Before I make a change for the first time I make a copy and call it
<name>.original. So I can fall back to the original. Any changes after
that I make a copy of the current file and name is <name>.ddmmyy (dd=Day
mm=month yy=year) I also keep a change log in the file when ever I can.
I did follow my change control procedure. However this time for some
reason I lost the vmlinuz file and couldn't recover it. Losing the
vmlinuz makes booting just spin it's wheels. I also copy pernamnet
changes to disk on my LS-120 as well. That way I can recover them
quickly.
--
**********************************************************************
Rev. David P. Giffen ICQ# 2857084 AIM Handle# Rev Coyote
----------------------------------------------------------------------
"Imagination is more importnant than knowledge" - Albert Einstein
**********************************************************************
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
