On Tue, Sep 18, 2012 at 3:23 PM, Grant Edwards <[email protected]> wrote: > On 2012-09-18, Mark Knecht <[email protected]> wrote: >> On Tue, Sep 18, 2012 at 12:54 PM, Neil Bothwick <[email protected]> wrote: >>> On Tue, 18 Sep 2012 10:37:57 -0700, Mark Knecht wrote: >>> >>>> mark@c2stable ~ $ cat /etc/udev/rules.d/51-android.rules >>>> UBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0007", >>>> MODE="0666" mark@c2stable ~ $ >>>> >>>> Anyway, it's all usable but a bit clumsy. Is there a sensible way I >>>> can have the device recognized and mounted via rules in fstab? (Or any >>>> other fixed file?) >>> >>> You could have your udev rule RUN mtpfs to mount the device. It takes a >>> few seconds to mount it, so I'd run it with &. > >> Seems like a reasonable enough solution for my needs. > > Does jmtpfs seem to be working reliably? > > I just ordered a Nexus Galaxy (which uses MTP), and Google has found > reports of flakey behavior with mtpfs. I've heard good things about > go-mtpfs (but you have to set up the Go compiler). > > And there's also gmtp... > > -- > Grant Edwards grant.b.edwards Yow! Gee, I feel kind of > at LIGHT in the head now, > gmail.com knowing I can't make my > satellite dish PAYMENTS! > >
If mounting once and transferring 4GB of data in 6 files, unmounting and then playing 5 minutes of video quaifies as reliable then yep, it's reliable. ;-) All I can say at this point is it seemed to work the way it was advertised on the link in the first post. I'll post back over time as I learn more. Possibly you an others who run into similar usage models will too. Cheers, Mark
