Skimming the recent threads, I notice that Carlos has discovered SSHFS. ;-) I do not recall if this was already installed, or if I installed it with the Yast installer. It is in the repositories. I use it regularly for connectivity between my system and my Android device (a Moto E). The command I use is in this format: sshfs gerry@xxx.xxx.xxx.xxx: /home/my_local_username/0_moto_e -o uid=1000,gid=100,follow_symlinks to connect wirelessly inside my own LAN. Of course, I pre-created the 0_moto_e directory in my home directory. On the device, I am using the SSHelper app. The reason for the uid and gid options is because of the way Android handles security, and Unison transfers are done using the "fat" boolean option (actually, could use just a subset) so that unchanged files do not constantly throw up a "properties changed" listing in Unison. (uid and gid above are the default first user id and default Users group id) To make certain which uid and gid a User should use in the above command, simply run: cat /etc/passwd | grep your_username Of course, for SSHelper, you would generate a key: ssh-keygen -t dsa -f ~/.ssh/id_dsa -N '' Then transfer it to the device: ssh-copy-id -i ~/.ssh/id_dsa.pub -p 2222 xxx.xxx.xxx.xxx The LAN IP address of the Android device is used where the xxx+ exists. If you use rsync, you would need to do similar there, or every time (probably) you connect the uid or gid can change, giving false change flags on the unchanged files. This allows me to access the device and operate on it as if it is just another local drive. On my main PC, I use Unison, run commands such as sha256sum *.mp4 > videos.mp4.sha256 on the device, can use anything available in my openSUSE system (CLI or GUI) to deal with the device. Of all the different experiments I have run with openSUSE to Android Connectivity, I have found this is, so far, the fastest, most usefull and most reliable method for connecting and moving things around. I have been using the checksums on large videos, and so far have had no failures using this method. All other methods I have tried to date have ended up with some of the files changed (files more than a short few seconds long) with errors, sometimes even different sizes. They would then play -- sort of -- in openSUSE, but with artifacts and other glitches, sometimes slight, often severe. Why do I know this? I am busy running all Connectivity experiments I can between an unrooted Android device and an openSUSE machine so that I can write up an extensive guide to the interoperability. Gerry Makaro aka Fraser_Bell -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On February 2, 2017 10:32:52 PM PST, Fraser_Bell
Skimming the recent threads, I notice that Carlos has discovered SSHFS. ;-)
I do not recall if this was already installed, or if I installed it with the Yast installer. It is in the repositories.
I use it regularly for connectivity between my system and my Android device (a Moto E).
The command I use is in this format:
sshfs gerry@xxx.xxx.xxx.xxx: /home/my_local_username/0_moto_e -o uid=1000,gid=100,follow_symlinks
to connect wirelessly inside my own LAN. Of course, I pre-created the 0_moto_e directory in my home directory.
On the device, I am using the SSHelper app.
The reason for the uid and gid options is because of the way Android handles security, and Unison transfers are done using the "fat" boolean
option (actually, could use just a subset) so that unchanged files do not constantly throw up a "properties changed" listing in Unison.
(uid and gid above are the default first user id and default Users group id)
To make certain which uid and gid a User should use in the above command, simply run: cat /etc/passwd | grep your_username
Of course, for SSHelper, you would generate a key: ssh-keygen -t dsa -f ~/.ssh/id_dsa -N ''
Then transfer it to the device: ssh-copy-id -i ~/.ssh/id_dsa.pub -p 2222 xxx.xxx.xxx.xxx
The LAN IP address of the Android device is used where the xxx+ exists.
If you use rsync, you would need to do similar there, or every time (probably) you connect the uid or gid can change, giving false change flags on the unchanged files.
This allows me to access the device and operate on it as if it is just another local drive.
On my main PC, I use Unison, run commands such as sha256sum *.mp4 > videos.mp4.sha256 on the device, can use anything available in my openSUSE system (CLI or
GUI) to deal with the device.
Of all the different experiments I have run with openSUSE to Android Connectivity, I have found this is, so far, the fastest, most usefull and most reliable method for connecting and moving things around.
I have been using the checksums on large videos, and so far have had no
failures using this method.
All other methods I have tried to date have ended up with some of the files changed (files more than a short few seconds long) with errors, sometimes even different sizes. They would then play -- sort of -- in openSUSE, but with artifacts and other glitches, sometimes slight, often severe.
Why do I know this? I am busy running all Connectivity experiments I can between an unrooted Android device and an openSUSE machine so that I can write up an extensive guide to the interoperability.
Gerry Makaro aka Fraser_Bell
Or you could have used KDE Connect. I wouldn't have top posted except the task of scrolling that wall of text would have been exhausting. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/02/2017 10:37 PM, John Andersen wrote:
Or you could have used KDE Connect. I wouldn't have top posted except the task of scrolling that wall of text would have been exhausting.
Experimented with KDE Connect, as well. As I said, I am searching out and experimenting with all methods. So far, as I said, I think sshfs is the superior method. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On February 2, 2017 10:53:13 PM PST, Fraser_Bell
On 02/02/2017 10:37 PM, John Andersen wrote:
Or you could have used KDE Connect. I wouldn't have top posted except the task of scrolling that wall of text would have been exhausting.
Experimented with KDE Connect, as well. As I said, I am searching out and experimenting with all methods.
So far, as I said, I think sshfs is the superior method. ;-)
You are probably right, because KDE Connect uses and requires sshfs. Which is how I first encountered it. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen
On February 2, 2017 10:32:52 PM PST, Fraser_Bell
wrote: Skimming the recent threads, I notice that Carlos has discovered SSHFS. ;-) [....] Or you could have used KDE Connect.
I wouldn't have top posted except the task of scrolling that wall of text would have been exhausting.
or you could have trimmed the "wall of text" that anyone interested in the thread would have alread read and posted and easy to read reply, even including wrapping your long lines! -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/03/2017 04:45 AM, Patrick Shanahan wrote:
or you could have trimmed the "wall of text" that anyone interested in the thread would have alread read and posted and easy to read reply, even including wrapping your long lines!
Do you have any idea how difficult and time consuming it is to delete that much text when posting on a smartphone? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-03 18:45, John Andersen wrote:
On 02/03/2017 04:45 AM, Patrick Shanahan wrote:
or you could have trimmed the "wall of text" that anyone interested in the thread would have alread read and posted and easy to read reply, even including wrapping your long lines!
Do you have any idea how difficult and time consuming it is to delete that much text when posting on a smartphone?
Yes :-( In that case, it is easier to tick "no quotes". -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Fri, 3 Feb 2017 09:45:39 -0800
John Andersen
On 02/03/2017 04:45 AM, Patrick Shanahan wrote:
or you could have trimmed the "wall of text" that anyone interested in the thread would have alread read and posted and easy to read reply, even including wrapping your long lines!
Do you have any idea how difficult and time consuming it is to delete that much text when posting on a smartphone?
So get a better mail client on the phone or stop using the phone to post. Simples! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 03/02/2017 à 22:34, Dave Howorth a écrit :
On Fri, 3 Feb 2017 09:45:39 -0800
Do you have any idea how difficult and time consuming it is to delete that much text when posting on a smartphone?
So get a better mail client on the phone or stop using the phone to post. Simples!
it's not a client problem, simply a touch versus mouse problem, and not always possible to have an other system, jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 03/02/2017 à 18:45, John Andersen a écrit :
On 02/03/2017 04:45 AM, Patrick Shanahan wrote:
or you could have trimmed the "wall of text" that anyone interested in the thread would have alread read and posted and easy to read reply, even including wrapping your long lines!
Do you have any idea how difficult and time consuming it is to delete that much text when posting on a smartphone?
then you can remove all the text, at least I can do this on my android one sometime better jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-03 07:32, Fraser_Bell wrote:
Skimming the recent threads, I notice that Carlos has discovered SSHFS. ;-)
:-)
I use it regularly for connectivity between my system and my Android device (a Moto E).
Ah!
The command I use is in this format:
sshfs gerry@xxx.xxx.xxx.xxx: /home/my_local_username/0_moto_e -o uid=1000,gid=100,follow_symlinks
to connect wirelessly inside my own LAN. Of course, I pre-created the 0_moto_e directory in my home directory.
On the device, I am using the SSHelper app.
Could you expand on the Android side of things? For instance, I assume you mean "SSHelper from Paul Lutus". How does it work? You have to create a user and password, perhaps, although I see you upload a key.
Why do I know this? I am busy running all Connectivity experiments I can between an unrooted Android device and an openSUSE machine so that I can write up an extensive guide to the interoperability.
To transfer to my android devices I typically use Thunar. In fact, once that Thunar (or Nautilus) has opened the Android filesystem, you can use any other browser, even 'mc', navigating to /run/user/.../mtp:something I have tried connecting from Android to PC, using ES File Explorer and its ssh connector, but I found it terribly slow. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 02/03/2017 02:32 AM, Carlos E. R. wrote:
On 2017-02-03 07:32, Fraser_Bell wrote:
Skimming the recent threads, I notice that Carlos has discovered SSHFS. ;-)
:-)
I use it regularly for connectivity between my system and my Android device (a Moto E). Ah!
The command I use is in this format:
sshfs gerry@xxx.xxx.xxx.xxx: /home/my_local_username/0_moto_e -o uid=1000,gid=100,follow_symlinks
to connect wirelessly inside my own LAN. Of course, I pre-created the 0_moto_e directory in my home directory.
On the device, I am using the SSHelper app. Could you expand on the Android side of things?
For instance, I assume you mean "SSHelper from Paul Lutus". How does it work? You have to create a user and password, perhaps, although I see you upload a key.
Indeed, yes. Very simple to install and use, very straightforward and extremely well-designed, IMHO. Paul also provides very good, indepth instructions and help at the SSHelper site, something quite extra-ordinary when compared to most Android apps. Check it out here: http://arachnoid.com/android/SSHelper/ Once you are using it, you will not go back, I am willing to bet. Oh ... and sure is nice to "see" you again, Carlos. Miss you on the forums. You can send me private e-mail at any time. I am an openSUSE member, so I am certain you can figure out the masked part of my e-mail address. (Of course, I think it shows when you get the e-mail downloaded. I am completely new to mailing lists, so learning that as I go.) -Gerry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Carlos E. R.
-
Dave Howorth
-
Fraser_Bell
-
jdd
-
John Andersen
-
Patrick Shanahan