dvbtime: enable transponder time sync by default

and refuse to disable it when the system time is invalid
InfoBar: Add confirmation before exit Movieplayer

As there were conserns that when press exit in the movieplayer
that you suddenly stop the movie player I added a confirmation
simple message box. With selecting No or simply press exit again
you get do not stop the movie. When selecting yes or simply press
OK you will still exit the movie (as yes is default).

This avoid a new configuration setting and adds functionality so
that you also can stop a movie with the exit button which did
orriginally nothing there.
InfoBar: Slightly streamline my previous path
InfoBarEPG: do not subscribe to events till we are initialized

Should avoid a potential evUpdatedEventInfo race

TODO: fix many similar situations
InfoBarGenerics: Try to fix GSOD by declaring epgList
InfoBarGenerics: fix typo in 5c22d0f7e58b4ad04c84c5df5d756272b43a8216
Revert "InfoBarGenerics: Try to fix GSOD by declaring epgList"

This reverts commit 17e7823e1d958b6f74123f0eb6bcc89182186abe.

self.epgList should not be used, it was introduced by an apparent case typo
InfoBarGenerics: init self.epglist
InfoBarGenerics: fix EventView fallback from EIT to epgcache
InfoBarGenerics: fix typo in 9537a01db8a8e45f90234a7f8751d334599c86aa

pass the 'now' event, instead of the now/next list
InfoBarGenerics: Really look to current bouquet first during NumberZap
InfoBarGenerics: Add option for EPG instead of secondInfoBar

As it was requested on the forum for a long time and I suggest
users get used to it as it was also avaiable in the orriginal
secondinfobar plugin
EventName: Make Now Next better translatable

As these are short strings I added the : to it so now these short
strings could be better translated.
I know there is a better solution for it, but I wasn't patient in
this special case.
NextEpgInfo: See the previous commit - for translations
NextEpgInfo: Fix a typo
use posix_fadvise, instead of using syscalls directly

posix_fadvise should be ok for all platforms
with recent kernel and glibc
do not use POSIX_FADV_RANDOM for an O_WRONLY file

POSIX_FADV_RANDOM disables readahead caching,
and since there is no readahead caching for a
writeonly file, POSIX_FADV_RANDOM is not needed
rewrite eDVBRecordFileThread flushing strategy

based on Linus' advise:
http://lkml.indiana.edu/hypermail/linux/kernel/1005.2/01845.html

-start async (SYNC_FILE_RANGE_WRITE) writeback after an aio_write completes
-wait (SYNC_FILE_RANGE_WAIT_AFTER) for writeback of the previous 8MB
block to complete, when we have written the next 8MB block
-POSIX_FADV_DONTNEED up to 'current - 8MB' point, to remove the old cache pages

If it turns out that sync_file_range(SYNC_FILE_RANGE_WAIT_AFTER) is
blocking eDVBRecordFileThread::asyncWrite for too long (causing demux
buffer overflows), we might consider removing the
sync_file_range(SYNC_FILE_RANGE_WAIT_AFTER) call.
POSIX_FADV_DONTNEED then would not drop all cache pages (because it
does not touch dirty pages), however one of the next times we call
POSIX_FADV_DONTNEED, those pages will have eventually been written out,
and will be dropped.

config.misc.flush_size is now obsolete, and has been removed.
The old flush strategy did not actually flush a lot of cache,
because POSIX_FADV_DONTNEED does not touch dirty pages, and
after writing a flush_size'd block, most pages in that block
would still be dirty by the time posix_fadvise was called.
eRawFile: mark old data POSIX_FADV_DONTNEED

Every 4MB read interval, advise POSIX_FADV_DONTNEED
up to the current offset.
When closing a file, advise POSIX_FADV_DONTNEED for the entire file.

This avoids keeping too many cache pages with data which
we are not likely to be needing again soon, during pvr playback.
remove obsolete BYTE_ORDER stuff