and it's important for me, that vdr cannot write anything to the video
directory.
Since this is important for you personaly, you want to change VDR for all
users, are you serious?
From my personal point of view a read only video directory with an video
disk recorder doesn't make much sense. But
On 09.03.2013 21:24, Peter Münster wrote:
Hi Klaus,
Could you please delete line 577 from vdr.c or do something similar to
let vdr continue even with read-only video directory?
vdr runs fine with this patch on my system, and it's important for me,
that vdr cannot write anything to the video
Am 08.03.2013 19:35, schrieb Stephan Loescher:
When you use the suggested solution with unionfs, then the client uses
the servers setup/timers/epg/etc. because it sees them in its
/video-directory.
Only until the first write, after that the client will continue with its
local writable copy.
It has been far too long since the last ttxtsubs release, so I thought
it's time for a new one.
A million thanks to all contributors:
Ville Skyttä, Jussi Tepponen, Matti Horila, Dimitri Petrovski
(Please let me know, if I missed someone here..)
The changes:
* Removed obsolete (unused since
VDR developer version 1.7.40 is now available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.40.tar.bz2
A 'diff' against the previous version is available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.39-1.7.40.diff
MD5 checksums:
f59a7ac199248a870e157c66a6ffc24d vdr-1.7.40.tar.bz2
The release of VDR version 2.0.0 is imminent, but there are still
several untranslated internationalized texts.
This is the final call for translations for version 2.0.0.
Please don't rely on the original translators to complete these
files, some of them may not have time or are no longer
On 10.03.2013 16:05, Klaus Schmidinger wrote:
The release of VDR version 2.0.0 is imminent, but there are still
several untranslated internationalized texts.
This is the final call for translations for version 2.0.0.
...
hu_HU.po: 1
I just received the missing Hungarian translation.
Thanks to
On 10.03.2013 16:05, Klaus Schmidinger wrote:
The release of VDR version 2.0.0 is imminent, but there are still
several untranslated internationalized texts.
This is the final call for translations for version 2.0.0.
...
ru_RU.po: 1
I just received the missing Russian translation.
Thanks to
Hi, I tried to build femon 1.7.18 against vdr 1.7.40 and got the following
log:
== Starting build()...
g++ -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='femon' -o femonosd.o
Am 10.03.2013 18:01, schrieb YUP:
Hi, I tried to build femon 1.7.18 against vdr 1.7.40 and got the following
log:
== Starting build()...
g++ -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c
Hi,
I solved it this way
--- /home/VDR/vdr-1.7.39/PLUGINS/src/femon/femonosd.c2013-02-10
03:20:00.0 +0100
+++ /home/VDR/vdr-1.7.40/PLUGINS/src/femon/femonosd.c2013-03-10
17:01:00.754613217 +0100
@@ -472,7 +472,7 @@
offset += OSDROWHEIGHT;
Thanks, Gianni, it works!
Regards,
Yarema
2013/3/10 Gianni Jan 23jan...@gmail.com
Hi,
I solved it this way
--- /home/VDR/vdr-1.7.39/PLUGINS/src/femon/femonosd.c2013-02-10
03:20:00.0 +0100
+++ /home/VDR/vdr-1.7.40/PLUGINS/src/femon/femonosd.c2013-03-10
17:01:00.754613217
On Sun, Mar 10 2013, fnu wrote:
Since this is important for you personaly, you want to change VDR for all
users, are you serious?
Yes, where is the problem?
But to change it in a global way like this is IMHO not a way to go.
Did you understand my suggestion? Here again: not writable:
On Sun, Mar 10 2013, Klaus Schmidinger wrote:
I'm afraid we're too close to releasing version 2.0.0 to make such
changes now.
No problem. I would just like to know, if you agree with such a patch
(or something more elaborated).
Besides, why don't you just use a writeable video directory and
On 10.03.2013 20:40, Peter Münster wrote:
On Sun, Mar 10 2013, fnu wrote:
But to change it in a global way like this is IMHO not a way to go.
Did you understand my suggestion? Here again: not writable: warning, not
readable: exit. Is that a problem for real-life systems?
For most people
On Sun, Mar 10 2013, Matthias Schniedermeyer wrote:
Read-only CAN for e.g. happen after an error when the filesystem is
mounted with error=read-only
Sorry, didn't know about such a configuration option. Therefore I agree
with a somewhat more elaborated solution as mentioned by fnu.
Or please
not writable: warning, not readable: exit. Is that a problem for real-life
systems?
A lot of people, myself included, don't like VDR exiting on its' own
unless it's completely unavoidable (such as a crash). I'd much rather
miss some recordings but have live tv available for everyone to use
17 matches
Mail list logo
