[ANNOUNCE] VDR developer version 1.3.30

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Gregoire Favre wrote:
> On Mon, Aug 22, 2005 at 01:38:51PM +0200, Klaus Schmidinger wrote:
> 
> 
>>I guess it's a matter of coincidence whether or not the driver
>>will be completely up and running when VDR tries to access the
>>devices. You should always wait until the driver is ready
>>before starting VDR.
> 
> 
> On my gentoo I have this in the vdr init scripts :
> 
> until [ -e /dev/dvb/adapter0/frontend0 ] && [ -e /dev/dvb/adapter1/frontend0 ] && [ -e /dev/dvb/adapter2/frontend0 ]; do
> sleep 1
> done
> 
> then vdr start :)

The main problem with udev is modprobe returns while udev keeps working
asynchronously.  Is "frontend0" the last device created?  The last one is
probably the one you want to check for.

Best Regards.


[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux