[vdr] [ANNOUNCE] VDR developer version 1.3.38

[Patrick Cernko]

Jere Malila wrote:
> Patrick Cernko wrote:
> 
>> Tommi Lundell wrote:
>>  
>>
>>> Peter Bieringer wrote:
>>>
>>>   
>>>
>>>> For those who get following error during compilation (like me on Fedora
>>>> Core 4):
>>>>
>>>> vdr.c:34:28: error: sys/capability.h: No such file or directory
>>>> vdr.c: In function 'bool SetCapSysTime()':
>>>> vdr.c:106: error: 'cap_t' was not declared in this scope
>>>> vdr.c:106: error: expected `;' before 'caps'
>>>> vdr.c:107: error: 'caps' was not declared in this scope
>>>> vdr.c:111: error: 'caps' was not declared in this scope
>>>> vdr.c:111: error: 'cap_set_proc' was not declared in this scope
>>>> vdr.c:113: error: 'cap_free' was not declared in this scope
>>>> vdr.c:116: error: 'caps' was not declared in this scope
>>>> vdr.c:116: error: 'cap_free' was not declared in this scope
>>>> make: *** [vdr.o] Error 1
>>>>
>>>> The missing file is included in package "libcap-devel".
>>>>
>>>>    Peter
>>>>
>>>>
>>>>     
>>>
>>> Hello
>>>
>>> I use debian (testing release) and after installing "apt-get install
>>> libcap-bin libcap-dev libcap1" packages vdr (1.3.38) compiling fine.
>>> But when i try to start it "source/vdr/vdr-1.3.38# ./vdr -c /etc/vdr -L
>>> /usr/local/lib/vdr/ -w 60 -E /var/cache/vdr/ -Pdxr3" I get error "vdr:
>>> cap_set_proc failed: Operation not permitted"
>>>
>>> Even command "./vdr --help" gives that "vdr: cap_set_proc failed:
>>> Operation not permitted" error.
>>>
>>> Any idea how i get vdr 1.3.38  working?
>>>
>>>   
>>
>>
>> I remember that  once did a "modprobe capability" as the module seams
>> not to be loaded automatically on capability access. So this might be a
>> reason for capabilities access to fail.
>>
>> @Klaus: Maybe you should make a note in the documentation about that.
>>  
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> vdr mailing list
>> vdr at linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>>  
>>
> Did you ever found any solution for this problem? I'm currently facing
> this.
> 

With your type of quoting, I'm not sure, if you are asking me, but
anyway, here is my answer:

Quiet easy solution:

echo capability >> /etc/modules

will make sure capability module is loaded early enough on a Debian
system that vdr will have capability kernel support for sure! :-)

I don't know how to force modules to be loaded at boot time in other
Linux distros, but I'm pretty sure you'll find it with something like

grep -E 'modprobe|insmod' /etc/rcS.d/*

So long,
-- 
Patrick Cernko | mailto:errror at errror.org | http://www.errror.org

"You don't need to power-up a computer to see if Windows is installed.
 Just check, if the writing on the reset-keys is readable." (anonym)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://www.linuxtv.org/pipermail/vdr/attachments/20060114/e3dae250/signature.pgp