[mythtv-users] Who's running Myth on Arch, and what do you think?

Nick Rout nick.rout at gmail.com
Sat Nov 23 05:23:10 UTC 2013


On Sat, Nov 23, 2013 at 2:17 PM, James Linder <jam at tigger.ws> wrote:
>
> On 23/11/2013, at 6:10 AM, mythtv-users-request at mythtv.org wrote:
>
>>> systemd is a wonderous fix for a problem that *almost nobody actually had*,
>>> complicating the most important part of system operations, the boot
>>> sequence, by at least an order of magnitude, if not two.
>> Well - it depends what problem You want to solve.
>> If Your problem is too complicated init subsystem - then systemd isn't
>> for You.
>
> But ... despite pleas for help, pouring through the wiki, I have a problem that at boot time the mythtv service fails to start because the firmware has not yet been loaded. It does start manually after boot.
>
> So what must be a common problem has no offers of a solution, and the wiki is rather bad saying "do this, trust me" so when it does not work well you are up-the-creek-without-a-paddle
>
> James
>
> PS my references
> http://www.mythtv.org/wiki/Systemd_mythbackend_Configuration
>
> and
>
> Wants=dev-dvb-adapter200-frontend0.device
> After=dev-dvb-adapter200-frontend0.device
>
> Where on earth do the names come from?

Well apart from the 200, it seems reasonably self explanatory - it is
looking for a device which created a device node

/dev/dvb/adapter/frontend0

Although why a simpler syntax like

wantsdev(or wantsfile)=/dev/svb/adapter/frontend0

couldn't be adopted I have no idea.

I thought the 200 might be a device node number, but it doesn't seem to be.


More information about the mythtv-users mailing list