Salix Forums

While installing drivers for a Brother printer via the command line terminal the brlpdwrapper file was NOT installed to the usr/lib/cups/filter folder

This anomaly occurred in both Mandriva and Salix

I could not use the printer until I'd copied over the file from another OS and installed to the said folder from the command line

Is this a problem specific to certain OS's as I never had the problem with Slack OR Suse OR Fedora???

I could not see the missing file when I opened the driver with an archiver either - should I have been able to - or is it a file generated by the system???

Is this a glitch with RPM's or just Brother drivers???

Although I have found a solution I would still like to know WHY!!!

Perhaps you need some driver files from http://solutions.brother.com/linux/sol/ ... ivers.html

Is this a problem specific to certain OS's as I never had the problem with Slack OR Suse OR Fedora???

Salix has the same cups packages than Slackware.

I don't know what installing means in this case (e.g. rpm/t?z package, compiling and installing from source, ...), but it sounds more like a problem of that product and not ours. When packaging foo2zjs for example it would only install certain files if the target directories already exist, it might be this or something similar here too.
That said the developer of foo2zjs is very defiant about packages so that might explain such troubles. Apart it contains proprietary stuff, so you won't see more than the build script published.

I can dig into this maybe tomorrow Bald Patches. I have a Brother printer and installed it correctly (was not that easy I remember, but not hard too).
I'll look at it and report it here.

As far as I understand the brlpdwrapper is part of some brother driver package.

The Brother drivers are the only ones available from their site and were converted with the rpm2tgz app in Slack.

I thought it odd that I didn't have the same problem in Slack although I do remember it wasn't plain sailing - I think I had to manually extract them in their destination folders.

Should I have converted the original drivers in Salix - would that make a difference.

I had exactly the same result in Mandriva using the RPM drivers and standard install format - the dest folder already exists there too.

I explored Suse and Fedora and Slack to be sure I knew what was missing and where it belonged and copied it over for installation.

Does the said file have anything to laterally do with the PPD file maybe when one or the other is generated???

1. What driver rpm did you use and where can we get it?
2. What arch are you using? 32 bit or 64 bit?

Perhaps the rpm has the files in another location than slack/salix needs them.

The printer is a Brother DCP117c but the linux drivers used are the lpr and cupswrapper MFC210c downloadable from the Brother Solutions Center. http://welcome.solutions.brother.com/bs ... index.html

I'm using 32bit Salix13.

I did look manually for the missing brlpdwrapper in the filesystem but I'll have another hunt just in case I missed it!

The cupswrapper rpm contains a script, that has to be run as root:
/usr/local/Brother/cupswrapper/cupswrapperMFC210C-1.0.0 -i

How did you install the rpm? With rpm2tgz?

I did use RPM2TGZ + Install.

I always logon as root in Slack but in Salix I can only Su in a terminal when I want to install something.

So... Is Salix simply Slack in a new dress or is it different at a more fundamental level???