How to give me perms to use the firewire port?
Gene Heskett
gheskett at wdtv.com
Mon Jun 24 08:52:32 UTC 2013
On Monday 24 June 2013 04:12:13 Ric Moore did opine:
> On 06/23/2013 10:12 PM, Karl Auer wrote:
> > On Sun, 2013-06-23 at 21:45 -0400, Gene Heskett wrote:
> >> So, while I have a root session going, what do I have to do to make
> >> the user 1000, me, be able to use the firewire port?
> >
> > Kino reports the device it is trying to open. The quick and dirty
> > answer is to change the group ownership on that device file
> > (/dev/whatever) to your own group. The module/device has "1394" in
> > the name, I think.
> >
> > The nicer, tidier, more extensible, and arguably *right* way to do it
> > would be to set up a firewire users group, put yourself in it, and
> > give the device that group ownership. You will then need to set that
> > group ownership on each boot, of course. There is a mechanism for
> > that which I can't remember off the top of my head, but it's used to
> > do things like provide access to serial ports to the dialout users
> > group.
>
> Regarding Kino, since it's EOL, when you start it use "padsp kino" in
> your command line at run time so that you will get sound via pulse.
> Otherwise, no sound. :) Ric
I know kino is EOL, but when I ran kdenlive, its replacement, after I had
gotten kino to run as me so I knew there weren't any perms problems, it was
not A: capable of opening the captured from the camera "dv" file from kino.
And B: It has not grown the knobs needed to run my camera. So its
incapable of pulling a fresh copy of the a/v stream from my camera.
Why kino development was stopped I am not privy to, but kdenlive as its
replacement, will, to replace kino here, have to grow far better controls.
There is no intuitiveness to how to run it, its something designed by a
committee, no two members of which spoke a common language.
The movie I was working on, a tad over 2 minutes of watching my lathe run
slowly while doing a 'rigid tapping operation", can be looked at now by
adding "/lathe-stf/lathe-pix/G33.1-demo.mpeg" to the link in the sig.
It won't mean much if you aren't a machinist, and I'm only hobbyist grade,
but making it actually run that 30 lines of gcode added about 100 lines to
the "my-lathe.hal" configuration file because that spindle stop and
reversal you see is synthesized completely by LinuxCNC. It could well be
the longest .hal file ever and the next mods to put much better braking on
the spindle for stopping will push it well past the 300 line marker. Just
visualizing it as a logic flow diagram, using rockhopper, gets one an .svg
file, which when scaled up to be readable, with the text labels about 8
postscript points high, takes 6 letter sized landscape pages to print it.
Cheers, Gene
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
My views
<http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml>
"Then you admit confirming not denying you ever said that?"
"NO! ... I mean Yes! WHAT?"
"I'll put `maybe.'"
-- Bloom County
A pen in the hand of this president is far more
dangerous than 200 million guns in the hands of
law-abiding citizens.
More information about the ubuntu-users
mailing list