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