Fernando de Oliveira wrote:
> --- Em dom, 4/11/12, Bruce Dubbs escreveu:
>
>> De: Bruce Dubbs
>> Assunto: Re: [blfs-dev] Finishing up BLFS checks for LFS-7.2
>> Para: "BLFS Development List"
>> Data: Domingo, 4 de Novembro de 2012, 22:55
>> Fernando de Oliveira wrote:
>>> --- Em qua, 31/10/12, Bruce Dubbs escreveu:
>>
>>>> I updated the instructions yesterday.  They
>> build OK, but have not
>>>> been tested.  Please use the most current
>> instructions and let me
>>>> know how it goes.
>>
>>> After solving some problems, I could install sane and
>> xsane today,
>>> unfortunately, not yet working. I need to recall what I
>> did for it to
>>> run in previous LFS version.
>>
>> Possibly a configuration issue.
>
> Two problems: permissions and configure switch in sane.
>
> Configure Switch:
>
> I had the message like "No libusb support".
>
> Solution:
>
> --enable-libusb_1_0
>
> Permissions
>
> Multi-function printer/scanner device is /dev/bus/usb/00{1,2}. From CUPS, 
> group is lp (one is root):
>
> # ls -lh /dev/bus/usb/00{1,2}
> /dev/bus/usb/001:
> total 0
> crw-rw-r-- 1 root lp 189, 0 Nov  5 10:47 001
> crw-rw-r-- 1 root lp 189, 1 Nov  5 12:01 002
>
> /dev/bus/usb/002:
> total 0
> crw-rw-r-- 1 root lp   189, 128 Nov  5 10:47 001
> crw-rw-r-- 1 root lp   189, 129 Nov  5 10:47 002
> crw-rw-r-- 1 root lp   189, 130 Nov  5 10:47 003
> crw-rw-r-- 1 root root 189, 131 Nov  5 10:47 004
>
> Solution:
>
> usermod -a -G lp <user>
>
> I cannot understand what mistake I did that I do not have the same as in 
> LFS"7.1":
>
> $ ls -lh /dev/bus/usb/00{1,2}
> /dev/bus/usb/001:
> total 0
> crw-rw-r-- 1 root root    189, 0 Nov  5 12:33 001
> crw-rw-r-- 1 root scanner 189, 1 Nov  5 12:34 002
>
> /dev/bus/usb/002:
> total 0
> crw-rw-r-- 1 root lp   189, 128 Nov  5 12:33 001
> crw-rw-r-- 1 root root 189, 129 Nov  5 12:33 002
> crw-rw-r-- 1 root root 189, 130 Nov  5 12:33 003
> crw-rw-r-- 1 root root 189, 131 Nov  5 12:33 004
>
>>>  From chroot, problems building sane:
>>>
>>> # ls -lh /{var,run}/lock ls: não é possível acessar
>> /run/lock:
>>> Arquivo ou diretório não encontrado lrwxrwxrwx 1 root
>> root 9 Set 20
>>> 14:08 /var/lock -> /run/lock
>
> I issued the command just to show /var/lock was a broken symlink.
>>
>>> [ls : not possible accessing /run/lock: File or
>> directory not
>>> found.]
>>>
>>> /bin/sh ../mkinstalldirs -m 775 /var/lock/sane mkdir -m
>> 775 -p --
>>> /var/lock/sane mkdir: é impossível criar o diretório
>> “/var/lock”:
>>> Arquivo existe
>>   > ****************** My free translation:
>>   > [mkdir: not
>>> possible to create "/var/lock": File exists]
>> ******************
>>
>> That's odd, the -p option for mkdir means "no error if
>> existing, make
>> parent directories as needed"
>>
>> I build remotely all the time via ssh, but not chroot.
>> Perhaps when
>> entering chroot you need to mkdir -p /run/lock.
>
> Thanks, Bruce.
>
> Now, sane and xsane are built and working and so they can be tagged?

OK, I'll do that.

   -- Bruce



-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to