[mythtv-users] upgrading to 0.24... (partly succesfull)

Gavin Hurlbut gjhurlbu at gmail.com
Sat Dec 4 19:20:48 UTC 2010


On Sat, Dec 4, 2010 at 2:19 AM, Udo van den Heuvel <udovdh at xs4all.nl> wrote:
> Starting mythbackend: setfacl: /dev/dvb/: Operation not supported
> setfacl: /dev/dvb//adapter0: Operation not supported
> setfacl: /dev/dvb//adapter0/demux0: Operation not supported
> setfacl: /dev/dvb//adapter0/frontend0: Operation not supported
> setfacl: /dev/dvb//adapter0/net0: Operation not supported
> setfacl: /dev/dvb//adapter0/dvr0: Operation not supported
> setfacl: /dev/dvb//adapter0/ca0: Operation not supported
> setfacl: /dev/snd/: Operation not supported
> setfacl: /dev/snd//controlC0: Operation not supported
> setfacl: /dev/snd//pcmC0D1p: Operation not supported
> setfacl: /dev/snd//pcmC0D0c: Operation not supported
> setfacl: /dev/snd//pcmC0D0p: Operation not supported
> setfacl: /dev/snd//by-path: Operation not supported
> setfacl: /dev/snd//controlC1: Operation not supported
> setfacl: /dev/snd//pcmC1D3p: Operation not supported
> setfacl: /dev/snd//seq: Operation not supported
> setfacl: /dev/snd//timer: Operation not supported
> setfacl: /dev/video*: No such file or directory
> setfacl: /dev/vbi*: No such file or directory
>
>
> This worked fine for 0.23. mythtv is in the video group which can write
> to the device.
> Now, even if we make mythtv owner of /dev/dvb/* and below, it says the same.
>
> But the backend starts and records.
>
> What did I do wrong, if any?
> How do I fix the setfacl stuff?

There is no direct call to setfacl anywhere in MythTV code.  What *is*
setfacl anyways?  It sounds like you need to trace down your
mythbackend startup script, and see what shenanigans it's trying to
do.


More information about the mythtv-users mailing list