Scott wrote:
> Hi Mikkel,
>
> Okay I just peed in /dev and saw neither no scanner or brother
> directory. So that is where the problem is. Now from what I understand
> is in the 60-libsane.rules file that is to create the sym link itself or
> is that a manual process? If so where should the sym link be made from?
>
> Scott
>
It is an automatic process. The scanner and brother will be files,
and not directories. They will also be something like scanner-1 or
brother-1. You will only get the brother-1 symlink if you created
the rule file we talked about. But if your printer/scanner is not
listed in 60-libsane.rules then the device entry and syslink are
probably not going to be created, or be created with a name that you
will not recognize. This is why I said you may have to create your
own rule file for it. On my system, I see a listing for a MFC-420CN
but not a 420C (I am guessing that it is a MFC-420C).
Try creating a 61-brother.rules file, and putting a line something
like this in it. (All on one line, even though it gets wrapped here.):
SYSFS{idVendor}=="04f9", SYSFS{idProduct}=="<240C product ID>",
MODE="0666", SYMLINK+="brother-%n"
You will have to replace <240C product ID> with the correct product
ID for your device. I already covered how to find it, so I will not
repeat it here. This should create a symlink called brother-1. Note
- this rule is different then the ones found in 60-libsane.rules. It
will not create a scanner-<something> symlink. Because of this, the
permissions will not be subject to console.perms changes, so you
will keep the 0666 permissions you want. If you would rather have a
scanner-<something> symlink, I can create one for you. I already
posted the console.perms file you would need to override the
permissions set in 50-default.perms.
If you have a hard time with the Product ID, let me know. If you
post the output of lsusb with the printer plugged in, I can help you
identify the correct value.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
