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 I wouldn't deny the need, because obviously there a single user out there who does need it, strange enough ...
But to change it in a global way like this is IMHO not a way to go. The correct solution would be that any user needing it, must decide and configure something. So, a kind of a switch like an OSD option or even a better way, VDR does check existence of a file in this video directory, e.g. ".vdrro", something similar to ".nodelete" ...
=== Kind regards fnu
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: warning, not readable: exit. Is that a problem for real-life systems?
The correct solution would be that any user needing it, must decide and configure something. So, a kind of a switch like an OSD option or even a better way, VDR does check existence of a file in this video directory, e.g. ".vdrro", something similar to ".nodelete" ...
Of course: why use the simple way, when there is a complex one... ;)
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 read-only is a plain error?
Read-only CAN for e.g. happen after an error when the filesystem is mounted with "error=read-only" (ignoring the runtime-case, when VDR is already running when that happens).
And you may not see a warning and only notice that something went wrong after you lost a recording that didn't happen. A not starting VDR is a little more noticable than an apparrently working one that just can't record anything.
So if VDR suddenly changes behaviour i can gurantee you that at least 1 person will be bitten by it.
As you said you are a single person, would you think it is fair to the person that will losse a recording to have lost it because you wanted a change in behaviour that was only for yourself with no apparent gain for others?
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 just forget about my request, since I'm probably the only vdr-user with such a setup.
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 than have an exited VDR and hearing complaints about the tv not working until I'm able to find out and fix whatever happened to /video access.
VDR should only exit when there's no other option or the user actually wants that behavior. Otherwise, it should be avoided.
-
fnu -
Matthias Schniedermeyer -
Peter Münster -
VDR User