cordel wrote:Use /dev/video0
/dev/video s just a symlink
Yes... I know it is a symlink. A symlink will function one-for-one the same as the real hard file.
Besides, using /dev/video0 in the command line makes no difference. Same error message.
Okay if you say so.
Last time I checked, zmfix needed direct access to the actual device to change permissions as you can't change permissions on the device through a symlink, but what do I know?
Also please next time create a new thread under the appropriate topic and don't hijack a thread and take it off subject.
Take it how you wish, if you want to resort to name calling and never return that's fine too, your prerogative.
But I have found that the symlink as far as ZM is concerned does not translate correctly for what ever reason. I tried to research several years ago to no avail.
And yes the discussion was about implementing V4L2, Not troubleshooting your card, so it was digressing the topic of which was old, and my suggestion and splitting the topic was for you benefit to make it more visible under the topic of the version your using.
Gee... I am sure Cordel really wants to help you now. I am not much interested either. I guess that Leaves Phil, or James Willson, and then you are just out of luck. Too bad you insulted the most helpful guy on the board first.
I wish I had good theory on it
Here is what I do know:
The only difference from using a symlink is that a symlink has it's own inode and points to the full path to the file unlike a hardlink that has the inode of the file as it points to the inode.
What we have seen under no certain circumstances, The symlink does not work for the video device, which leaves us to wonder if something is trying to use the inode which gets lost using the symlink inode.
