Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
How to mount the entire mobile device file system on the Mac
13 views
Skip to first unread message
harry newton
Oct 14, 2017, 7:35:40 AM10/14/17
to
How best to mount the entire mobile device file system on the Mac
I want to learn how to best mount all mobile devices (both iOS and Android)
in the household on the Mac over the local LAN (i.e., over Wi-Fi) so I
would like to know the "basic" approach for how the Mac mounts mobile
devices over the LAN.
The basic approach I used to mount phones on Windows 10 is documented here:
How to mount the entire mobile device file system on Windows
<https://groups.google.com/d/msg/comp.mobile.ipad/ix8xgTcexAY/dlY4nLMfAgAJ>
For example, here's how I copy over the HOSTS file from Windows to a phone:
<http://wetakepic.com/images/2017/10/10/hosts8407d.jpg>
How would you suggest one best approach this same mounting task on the Mac?
I want to learn how to best mount all mobile devices (both iOS and Android)
in the household on the Mac over the local LAN (i.e., over Wi-Fi) so I
would like to know the "basic" approach for how the Mac mounts mobile
devices over the LAN.
The basic approach I used to mount phones on Windows 10 is documented here:
How to mount the entire mobile device file system on Windows
<https://groups.google.com/d/msg/comp.mobile.ipad/ix8xgTcexAY/dlY4nLMfAgAJ>
For example, here's how I copy over the HOSTS file from Windows to a phone:
<http://wetakepic.com/images/2017/10/10/hosts8407d.jpg>
How would you suggest one best approach this same mounting task on the Mac?
nospam
Oct 14, 2017, 10:35:38 AM10/14/17
to
In article <orssq9$13tt$1...@gioia.aioe.org>, harry newton
choose connect to server..., next either click browse and select from
the list of available servers or directly enter the protocol and mdns
name, e.g., smb://myserver.local. in the address bar, then supply
login/password when asked.
<ha...@is.invalid> wrote:
> How best to mount the entire mobile device file system on the Mac
for any shared network device, the easiest way is in finder: go menu,
> How best to mount the entire mobile device file system on the Mac
choose connect to server..., next either click browse and select from
the list of available servers or directly enter the protocol and mdns
name, e.g., smb://myserver.local. in the address bar, then supply
login/password when asked.
Snit
Oct 14, 2017, 11:11:11 AM10/14/17
to
On 10/14/17, 4:35 AM, in article orssq9$13tt$1...@gioia.aioe.org, "harry
Is there a task you are looking at accomplishing other than just looking at
the whole file system?
--
Personal attacks from those who troll show their own insecurity. They cannot
use reason to show the message to be wrong so they try to feel somehow
superior by attacking the messenger.
They cling to their attacks and ignore the message time and time again.
<https://youtu.be/H4NW-Cqh308>
the whole file system?
--
Personal attacks from those who troll show their own insecurity. They cannot
use reason to show the message to be wrong so they try to feel somehow
superior by attacking the messenger.
They cling to their attacks and ignore the message time and time again.
<https://youtu.be/H4NW-Cqh308>
harry newton
Oct 14, 2017, 1:39:57 PM10/14/17
to
He who is Snit said on Sat, 14 Oct 2017 08:11:03 -0700:
> Is there a task you are looking at accomplishing other than just looking at
> the whole file system?
I've been interconnecting Apple and Unix and Windows "users" and "devices"
on the local network forever; so it's a never-ending task where each year
someone gives me new ideas for interconnecting the three.
As just one example, in the early nineties, I would run Samba and CAP
(Columbia AppleTalk Protocol) on SunOS and/or Solaris servers so that all
the PCs and Macs and UNIX people could share (literally) the *same* files,
taking into account that specific resource fork and data fork stuff which
drove the admins (well, they were called "secretaries" in those days) nuts
if I didn't *hide* the fork from them that they didn't need.
As another example, in the very early days of Adobe PDF, when nobody knew
anything about PDF (but they knew about PostScript since all the printers
used it) so there wasn't any "print to PDF" option in the software yet,
when I was trying to get my IT department to set up a common "distiller"
location where anyone on Mac or Unix or Windows could pop a file into the
folder where it would be instantly converted to a PDF that everyone could
read.
I also dealt with writing automatic line feed and carriage return
converters just to make sure everyone saw a text file the same way, etc.
This is just a far simpler and just as common task which is simply to get
all the mobile devices in any house in the world to be able to share their
file systems over WiFi with the Mac desktops, as long as they're all on the
same local network.
I would think this is something anyone in any household might want to do
since it allows you to maintain common files (e.g., hosts files) which I've
been doing for decades, and to maintain a family photo album without having
to put it on the Internet (where it doesn't belong).
All I'm asking here is for advice from the Mac system gurus on how best to
architect a general solution that works for iOS and Android and Mac users
alike.
The thread is simply asking for advice on how you either did it already, or
how you would accomplish the task in your own home WiFi network.
> Is there a task you are looking at accomplishing other than just looking at
> the whole file system?
on the local network forever; so it's a never-ending task where each year
someone gives me new ideas for interconnecting the three.
As just one example, in the early nineties, I would run Samba and CAP
(Columbia AppleTalk Protocol) on SunOS and/or Solaris servers so that all
the PCs and Macs and UNIX people could share (literally) the *same* files,
taking into account that specific resource fork and data fork stuff which
drove the admins (well, they were called "secretaries" in those days) nuts
if I didn't *hide* the fork from them that they didn't need.
As another example, in the very early days of Adobe PDF, when nobody knew
anything about PDF (but they knew about PostScript since all the printers
used it) so there wasn't any "print to PDF" option in the software yet,
when I was trying to get my IT department to set up a common "distiller"
location where anyone on Mac or Unix or Windows could pop a file into the
folder where it would be instantly converted to a PDF that everyone could
read.
I also dealt with writing automatic line feed and carriage return
converters just to make sure everyone saw a text file the same way, etc.
This is just a far simpler and just as common task which is simply to get
all the mobile devices in any house in the world to be able to share their
file systems over WiFi with the Mac desktops, as long as they're all on the
same local network.
I would think this is something anyone in any household might want to do
since it allows you to maintain common files (e.g., hosts files) which I've
been doing for decades, and to maintain a family photo album without having
to put it on the Internet (where it doesn't belong).
All I'm asking here is for advice from the Mac system gurus on how best to
architect a general solution that works for iOS and Android and Mac users
alike.
The thread is simply asking for advice on how you either did it already, or
how you would accomplish the task in your own home WiFi network.
nospam
Oct 14, 2017, 2:05:08 PM10/14/17
to
In article <orti5a$6ku$1...@gioia.aioe.org>, harry newton
there is also no need to 'architect a general solution' for something
so trivial.
> The thread is simply asking for advice on how you either did it already, or
> how you would accomplish the task in your own home WiFi network.
the task you claim to want to do is best done in other ways, which has
also been explained to you in other threads, and which you also
ignored.
<ha...@is.invalid> wrote:
> All I'm asking here is for advice from the Mac system gurus on how best to
> architect a general solution that works for iOS and Android and Mac users
> alike.
answered elsewhere, which you of course ignored.
> All I'm asking here is for advice from the Mac system gurus on how best to
> architect a general solution that works for iOS and Android and Mac users
> alike.
there is also no need to 'architect a general solution' for something
so trivial.
> The thread is simply asking for advice on how you either did it already, or
> how you would accomplish the task in your own home WiFi network.
also been explained to you in other threads, and which you also
ignored.
Frank Slootweg
Oct 14, 2017, 4:21:05 PM10/14/17
to
nospam <nos...@nospam.invalid> wrote:
> In article <orti5a$6ku$1...@gioia.aioe.org>, harry newton
> <ha...@is.invalid> wrote:
>
> > All I'm asking here is for advice from the Mac system gurus on how best to
> > architect a general solution that works for iOS and Android and Mac users
> > alike.
>
> answered elsewhere, which you of course ignored.
I dare you to quote *one* example where you actually gave *specific*
> In article <orti5a$6ku$1...@gioia.aioe.org>, harry newton
> <ha...@is.invalid> wrote:
>
> > All I'm asking here is for advice from the Mac system gurus on how best to
> > architect a general solution that works for iOS and Android and Mac users
> > alike.
>
> answered elsewhere, which you of course ignored.
how-to instructions, instead of unspecific, unhelpful, pathetic
soundbites like the ones you're uttering in this thread.
> there is also no need to 'architect a general solution' for something
> so trivial.
>
> > The thread is simply asking for advice on how you either did it already, or
> > how you would accomplish the task in your own home WiFi network.
>
> the task you claim to want to do is best done in other ways, which has
> also been explained to you in other threads, and which you also
> ignored.
another way? When you utter your usual sound bites, please try to make
them at least somewhat on topic.
He asked a question and - as usual -, you belittle, dodge, divert,
etc.. Why is that? Because you don't *have* an answer? Never mind
humouring 'harry', humour the rest of us by - for once - putting your
money where your mouth is.
So I [1] will ask the same question:
<quote>
I want to learn how to best mount all mobile devices (both iOS and Android)
in the household on the Mac over the local LAN (i.e., over Wi-Fi) so I
would like to know the "basic" approach for how the Mac mounts mobile
devices over the LAN.
[1] Yes, I have the same question. Not for my 'household', but for that
of a close relative.
nospam
Oct 14, 2017, 5:55:52 PM10/14/17
to
In article <oru2k7...@ID-201911.user.individual.net>, Frank Slootweg
<nos...@nospam.invalid> wrote:
> In article <orssq9$13tt$1...@gioia.aioe.org>, harry newton
> > there is also no need to 'architect a general solution' for something
> > so trivial.
> >
> > > The thread is simply asking for advice on how you either did it already,
> > > or
> > > how you would accomplish the task in your own home WiFi network.
> >
> > the task you claim to want to do is best done in other ways, which has
> > also been explained to you in other threads, and which you also
> > ignored.
>
> What "other ways"? He did not mention a way,
yes he did.
he insists on mounting the entire file system for all of his devices,
including mobile, to copy a hosts file.
the correct solution is to do that on the router, as many people have
suggested.
> so how can there be
> another way? When you utter your usual sound bites, please try to make
> them at least somewhat on topic.
unlike your trolling, they're on topic.
> He asked a question and - as usual -, you belittle, dodge, divert,
> etc.. Why is that?
no, that's what *you* do.
<th...@ddress.is.invalid> wrote:
> > > All I'm asking here is for advice from the Mac system gurus on how best to
> > > architect a general solution that works for iOS and Android and Mac users
> > > alike.
> >
> > answered elsewhere, which you of course ignored.
>
> I dare you to quote *one* example where you actually gave *specific*
> how-to instructions, instead of unspecific, unhelpful, pathetic
> soundbites like the ones you're uttering in this thread.
In article <141020171035363330%nos...@nospam.invalid>, nospam
> > > All I'm asking here is for advice from the Mac system gurus on how best to
> > > architect a general solution that works for iOS and Android and Mac users
> > > alike.
> >
> > answered elsewhere, which you of course ignored.
>
> I dare you to quote *one* example where you actually gave *specific*
> how-to instructions, instead of unspecific, unhelpful, pathetic
> soundbites like the ones you're uttering in this thread.
<nos...@nospam.invalid> wrote:
> In article <orssq9$13tt$1...@gioia.aioe.org>, harry newton
> <ha...@is.invalid> wrote:
> > How best to mount the entire mobile device file system on the Mac
>
> > How best to mount the entire mobile device file system on the Mac
>
> for any shared network device, the easiest way is in finder: go menu,
> choose connect to server..., next either click browse and select from
> the list of available servers or directly enter the protocol and mdns
> name, e.g., smb://myserver.local. in the address bar, then supply
> login/password when asked.
since he isn't interested in actual answers, he ignored it.
> choose connect to server..., next either click browse and select from
> the list of available servers or directly enter the protocol and mdns
> name, e.g., smb://myserver.local. in the address bar, then supply
> login/password when asked.
> > there is also no need to 'architect a general solution' for something
> > so trivial.
> >
> > > The thread is simply asking for advice on how you either did it already,
> > > or
> > > how you would accomplish the task in your own home WiFi network.
> >
> > the task you claim to want to do is best done in other ways, which has
> > also been explained to you in other threads, and which you also
> > ignored.
>
> What "other ways"? He did not mention a way,
he insists on mounting the entire file system for all of his devices,
including mobile, to copy a hosts file.
the correct solution is to do that on the router, as many people have
suggested.
> so how can there be
> another way? When you utter your usual sound bites, please try to make
> them at least somewhat on topic.
> He asked a question and - as usual -, you belittle, dodge, divert,
> etc.. Why is that?
Frank Slootweg
Oct 15, 2017, 11:37:40 AM10/15/17
to
nospam <nos...@nospam.invalid> wrote:
> In article <oru2k7...@ID-201911.user.individual.net>, Frank Slootweg
> <th...@ddress.is.invalid> wrote:
>
> > > > All I'm asking here is for advice from the Mac system gurus on
> > > > how best to architect a general solution that works for iOS and
> > > > Android and Mac users alike.
> > >
> > > answered elsewhere, which you of course ignored.
> >
> > I dare you to quote *one* example where you actually gave *specific*
> > how-to instructions, instead of unspecific, unhelpful, pathetic
> > soundbites like the ones you're uttering in this thread.
>
> In article <141020171035363330%nos...@nospam.invalid>, nospam
> <nos...@nospam.invalid> wrote:
> > In article <orssq9$13tt$1...@gioia.aioe.org>, harry newton
> > <ha...@is.invalid> wrote:
> > > How best to mount the entire mobile device file system on the Mac
> >
> > for any shared network device, the easiest way is in finder: go menu,
> > choose connect to server..., next either click browse and select from
> > the list of available servers or directly enter the protocol and mdns
> > name, e.g., smb://myserver.local. in the address bar, then supply
> > login/password when asked.
>
> since he isn't interested in actual answers, he ignored it.
Are you saying that - out of the box - an iOS device can be accessed
> In article <oru2k7...@ID-201911.user.individual.net>, Frank Slootweg
> <th...@ddress.is.invalid> wrote:
>
> > > > All I'm asking here is for advice from the Mac system gurus on
> > > > how best to architect a general solution that works for iOS and
> > > > Android and Mac users alike.
> > >
> > > answered elsewhere, which you of course ignored.
> >
> > I dare you to quote *one* example where you actually gave *specific*
> > how-to instructions, instead of unspecific, unhelpful, pathetic
> > soundbites like the ones you're uttering in this thread.
>
> In article <141020171035363330%nos...@nospam.invalid>, nospam
> <nos...@nospam.invalid> wrote:
> > In article <orssq9$13tt$1...@gioia.aioe.org>, harry newton
> > <ha...@is.invalid> wrote:
> > > How best to mount the entire mobile device file system on the Mac
> >
> > for any shared network device, the easiest way is in finder: go menu,
> > choose connect to server..., next either click browse and select from
> > the list of available servers or directly enter the protocol and mdns
> > name, e.g., smb://myserver.local. in the address bar, then supply
> > login/password when asked.
>
> since he isn't interested in actual answers, he ignored it.
as a Network Share, i.e. it has a SMB server? If not, then it's indeed
again unspecific and hence unhelpful.
> > > there is also no need to 'architect a general solution' for something
> > > so trivial.
> > >
> > > > The thread is simply asking for advice on how you either did it
> > > > already, or how you would accomplish the task in your own home
> > > > WiFi network.
> > >
> > > the task you claim to want to do is best done in other ways, which has
> > > also been explained to you in other threads, and which you also
> > > ignored.
> >
> > What "other ways"? He did not mention a way,
>
> yes he did.
>
> he insists on mounting the entire file system for all of his devices,
> including mobile, to copy a hosts file.
*said* so. It's about copying fileS, not just the hosts file. For
example, he also mentioned "family photo album".
nospam
Oct 15, 2017, 12:17:28 PM10/15/17
to
In article <os06cr...@ID-201911.user.individual.net>, Frank Slootweg
all that's needed is an app that supports the desired protocol. many of
them are free and some support more than just one protocol.
he already said he had no issue with installing an ftp server app on
ios/android, nor did he ask about that part. i considered that part
done.
there are much easier ways to transfer stuff, but that's what he asked
for.
> > > > > The thread is simply asking for advice on how you either did it
> > > > > already, or how you would accomplish the task in your own home
> > > > > WiFi network.
> > > >
> > > > the task you claim to want to do is best done in other ways, which has
> > > > also been explained to you in other threads, and which you also
> > > > ignored.
> > >
> > > What "other ways"? He did not mention a way,
> >
> > yes he did.
> >
> > he insists on mounting the entire file system for all of his devices,
> > including mobile, to copy a hosts file.
>
> Pathetic dodge and divert. The hosts file is an *example*, and he
> *said* so. It's about copying fileS, not just the hosts file. For
> example, he also mentioned "family photo album".
i'm not dodging at all.
the hosts file is an example, one which he said he plans on doing on
all of his devices. it was not a generic example.
transferring a 'family photo album' does not need mounting the file
system either.
there is no reason to mount the file system at all to copy files.
clearer now?
there are *much* easier ways to do what he claims to want to do, except
that he is fixated on mounting the file system to do it and refuses any
alternatives.
<th...@ddress.is.invalid> wrote:
> Are you saying that - out of the box - an iOS device can be accessed
> as a Network Share, i.e. it has a SMB server? If not, then it's indeed
> again unspecific and hence unhelpful.
almost out of the box.
> Are you saying that - out of the box - an iOS device can be accessed
> as a Network Share, i.e. it has a SMB server? If not, then it's indeed
> again unspecific and hence unhelpful.
all that's needed is an app that supports the desired protocol. many of
them are free and some support more than just one protocol.
he already said he had no issue with installing an ftp server app on
ios/android, nor did he ask about that part. i considered that part
done.
there are much easier ways to transfer stuff, but that's what he asked
for.
> > > > > The thread is simply asking for advice on how you either did it
> > > > > already, or how you would accomplish the task in your own home
> > > > > WiFi network.
> > > >
> > > > the task you claim to want to do is best done in other ways, which has
> > > > also been explained to you in other threads, and which you also
> > > > ignored.
> > >
> > > What "other ways"? He did not mention a way,
> >
> > yes he did.
> >
> > he insists on mounting the entire file system for all of his devices,
> > including mobile, to copy a hosts file.
>
> Pathetic dodge and divert. The hosts file is an *example*, and he
> *said* so. It's about copying fileS, not just the hosts file. For
> example, he also mentioned "family photo album".
the hosts file is an example, one which he said he plans on doing on
all of his devices. it was not a generic example.
transferring a 'family photo album' does not need mounting the file
system either.
there is no reason to mount the file system at all to copy files.
clearer now?
there are *much* easier ways to do what he claims to want to do, except
that he is fixated on mounting the file system to do it and refuses any
alternatives.
Snit
Oct 15, 2017, 12:31:44 PM10/15/17
to
Frank Slootweg
Oct 15, 2017, 1:39:50 PM10/15/17
to
nospam <nos...@nospam.invalid> wrote:
> In article <os06cr...@ID-201911.user.individual.net>, Frank Slootweg
> <th...@ddress.is.invalid> wrote:
>
> > Are you saying that - out of the box - an iOS device can be accessed
> > as a Network Share, i.e. it has a SMB server? If not, then it's indeed
> > again unspecific and hence unhelpful.
>
> almost out of the box.
>
> all that's needed is an app that supports the desired protocol. many of
> them are free and some support more than just one protocol.
You might think that's easy, but it very likely isn't easy at all!
> In article <os06cr...@ID-201911.user.individual.net>, Frank Slootweg
> <th...@ddress.is.invalid> wrote:
>
> > Are you saying that - out of the box - an iOS device can be accessed
> > as a Network Share, i.e. it has a SMB server? If not, then it's indeed
> > again unspecific and hence unhelpful.
>
> almost out of the box.
>
> all that's needed is an app that supports the desired protocol. many of
> them are free and some support more than just one protocol.
A SMB server on iOS probably needs jailbreaking in order to use the
standard SMB port (445). At least that's - as I described - the case on
Android and I think it's unlikely that iOS is less secure in this than
Android.
Without port 445 capability, the whole thing falls down, because
- as I described - Windows doesn't allow a non-445 SMB port, so there's
no point that OS X or/and Linux can.
So to make your suggestion a workable one, give the URL of an iOS app
which is a SMB server which uses port 445, but which does not require
jailbreaking.
> he already said he had no issue with installing an ftp server app on
> ios/android, nor did he ask about that part. i considered that part
> done.
*specific* how-to instructions, instead of meaningless soundbites.
> there are much easier ways to transfer stuff,
(i.e. OS X) device, not from the *mobile* device (which is indeed easy,
but irrelevant). See my response to Snit about this requirement.
> but that's what he asked
> for.
> > > > > > The thread is simply asking for advice on how you either did it
> > > > > > already, or how you would accomplish the task in your own home
> > > > > > WiFi network.
> > > > >
> > > > > the task you claim to want to do is best done in other ways, which has
> > > > > also been explained to you in other threads, and which you also
> > > > > ignored.
> > > >
> > > > What "other ways"? He did not mention a way,
> > >
> > > yes he did.
> > >
> > > he insists on mounting the entire file system for all of his devices,
> > > including mobile, to copy a hosts file.
> >
> > Pathetic dodge and divert. The hosts file is an *example*, and he
> > *said* so. It's about copying fileS, not just the hosts file. For
> > example, he also mentioned "family photo album".
>
> i'm not dodging at all.
>
> the hosts file is an example, one which he said he plans on doing on
> all of his devices. it was not a generic example.
definition, it's generic.
> transferring a 'family photo album' does not need mounting the file
> system either.
>
> there is no reason to mount the file system at all to copy files.
desktop. For that scenario, the desktop is the client and the iOS device
needs to be a server.
Note that "mount" should be interpreted as the concept, not the
literal term. For example on Linux, accessing a (SMB) Network Share is
not the same as accessing a mounted volume. And on Windows the concept
of mounting a volume does not really exist, but some vendors use the
term because it's a common concept.
> clearer now?
I hope the *real* requirements are now clear to you.
> there are *much* easier ways to do what he claims to want to do, except
> that he is fixated on mounting the file system to do it and refuses any
> alternatives.
free to propose - specific and detailed - alternatives, which meet the
given requirements.
Frank Slootweg
Oct 15, 2017, 2:15:51 PM10/15/17
to
Snit <use...@gallopinginsanity.com> wrote:
[...]
> He has a solution in search of a problem.
I understand people belittling 'harry'. I do so too from time to time.
But, as I said to nospam: Never mind humouring 'harry', but humour the
rest of us by giving specific how-to's for solving specific technical
issues/ requirements.
As I described, I have the same technical issue/requirement, just in a
smaller set of OSs and for a different purpose.
[*Not* to/about you (Snit):]
Moral: I - and others - don't need belittling obnoxious pompous twats
telling us what we (do not) need or/and how (not) to do them, especially
not when said twats even don't understand the issue/requirement.
[...]
> He has a solution in search of a problem.
But, as I said to nospam: Never mind humouring 'harry', but humour the
rest of us by giving specific how-to's for solving specific technical
issues/ requirements.
As I described, I have the same technical issue/requirement, just in a
smaller set of OSs and for a different purpose.
[*Not* to/about you (Snit):]
Moral: I - and others - don't need belittling obnoxious pompous twats
telling us what we (do not) need or/and how (not) to do them, especially
not when said twats even don't understand the issue/requirement.
Snit
Oct 15, 2017, 2:32:47 PM10/15/17
to
On 10/15/17, 11:15 AM, in article os0f2...@ID-201911.user.individual.net,
I have no issue with you or he wanting such a thing... but I think in most
cases it is about a philosophy of doing so more than it is about any given
feature. Does not mean this must apply to you or any other given person, nor
do I think that must be a bad thing.
cases it is about a philosophy of doing so more than it is about any given
feature. Does not mean this must apply to you or any other given person, nor
do I think that must be a bad thing.
nospam
Oct 15, 2017, 3:24:21 PM10/15/17
to
In article <os0f2...@ID-201911.user.individual.net>, Frank Slootweg
<th...@ddress.is.invalid> wrote:
> As I described, I have the same technical issue/requirement, just in a
> smaller set of OSs and for a different purpose.
then ask specific questions about your particular scenario.
> As I described, I have the same technical issue/requirement, just in a
> smaller set of OSs and for a different purpose.
nospam
Oct 15, 2017, 3:24:23 PM10/15/17
to
In article <os0dhs...@ID-201911.user.individual.net>, Frank Slootweg
> A SMB server on iOS probably needs jailbreaking in order to use the
> standard SMB port (445). At least that's - as I described - the case on
> Android and I think it's unlikely that iOS is less secure in this than
> Android.
the examples below make no mention of alternate ports and the video
looks like any other windows share.
i tried the wifi hd app, which worked on a mac using the default smb://.
and smb isnt the only protocol either. it's a 'generic example'.
> Without port 445 capability, the whole thing falls down, because
> - as I described - Windows doesn't allow a non-445 SMB port, so there's
> no point that OS X or/and Linux can.
>
> So to make your suggestion a workable one, give the URL of an iOS app
> which is a SMB server which uses port 445, but which does not require
> jailbreaking.
fhub - mac/winxp/ubuntu/win7 demoed:
https://www.youtube.com/watch?v=YLwWkC9P7hk>
skip directly to win7 mounting:
<https://www.youtube.com/watch?v=YLwWkC9P7hk&t=123>
other options:
<https://itunes.apple.com/us/app/diskonphone-wireless-smb-server-hard-di
sk-drive/id1078556448?mt=8>
- SMB Server
- Transfer files from/to your PC running Windows or from/to your
Mac/Linux using the built in SMB(Samba) protocol.
- Work flawlessly with any OS that supports SMB protocol
<https://itunes.apple.com/us/app/wifi-hd-free-wireless-smb-usb-hard-disk-
drive-nfs-network/id311170976?mt=8>
- Share Files Using the built-in HTTP, and SMB File Servers
- Works flawlessly with Windows or Mac like a normal network drive.
> > he already said he had no issue with installing an ftp server app on
> > ios/android, nor did he ask about that part. i considered that part
> > done.
>
> You (probably) thought wrong.
nope. i remember when he was proud of himself for figuring it out.
> This is exactly the reason why one needs
> *specific* how-to instructions, instead of meaningless soundbites.
i'm not interested in specifics with him, particularly in response to
his vague questions, such as 'we need to architect a general solution'.
> > there are much easier ways to transfer stuff,
>
> Such as? Note that the transfer must be initiated from the *desktop*
> (i.e. OS X) device, not from the *mobile* device (which is indeed easy,
> but irrelevant). See my response to Snit about this requirement.
artificial restrictions only makes things more difficult than they need
to be. the goal is to transfer files, not fit into some rigid method.
anyway, airdrop is by far the easiest, initiated on the sending device,
however it's mac/ios only.
for other systems, use a document provider or share extension that
supports the preferred protocol, which lets the user use their
favourite app to open and/or save to any remote system to which they
have access, even if the original app does not directly support said
protocol (thus the name extension).
the app only needs to support extensions, which is fairly common if the
app can open, create and/or modify documents.
for media (music, video, etc.) itunes is the best choice and makes
things *very* easy. new podcasts transfer while previously listened
ones are removed, entirely automatically (if configured to do so).
watch part of a movie on one device and continue later on another
device (or same device), without needing to write down times and fast
forward, which is what he said he does. smart playlists auto-update on
the fly. backups are also automatic (and for everything).
there are also cloud solutions, either on the local lan or the public
internet. documents put in the cloud can be encrypted for security
(perhaps overkill for local clouds, but still an option).
> > but that's what he asked for.
>
> Correct.
which is why i answered as i did.
> >
> > the hosts file is an example, one which he said he plans on doing on
> > all of his devices. it was not a generic example.
>
> Yes it was. It was *specifically* labeled as an example, so by
> definition, it's generic.
no.
it was a very specific example he claimed to want to do, not a random
file type.
> > transferring a 'family photo album' does not need mounting the file
> > system either.
> >
> > there is no reason to mount the file system at all to copy files.
>
> See above. It's needed if one wants to initiate the transfer from the
> desktop. For that scenario, the desktop is the client and the iOS device
> needs to be a server.
nope.
> Note that "mount" should be interpreted as the concept, not the
> literal term. For example on Linux, accessing a (SMB) Network Share is
> not the same as accessing a mounted volume. And on Windows the concept
> of mounting a volume does not really exist, but some vendors use the
> term because it's a common concept.
i'm not interested in semantic games.
> > clearer now?
>
> I hope the *real* requirements are now clear to you.
they've been clear all along.
> > there are *much* easier ways to do what he claims to want to do, except
> > that he is fixated on mounting the file system to do it and refuses any
> > alternatives.
>
> As I said, don't (only) humour him, but humour us as well. So feel
> free to propose - specific and detailed - alternatives, which meet the
> given requirements.
ask a specific question and you will get a specific answer.
so far, all you've said is you have a 'similar' situation, therefore
any answers cannot be specific and detailed because they could be
totally wrong for your particular situation.
<th...@ddress.is.invalid> wrote:
> >
> > > Are you saying that - out of the box - an iOS device can be accessed
> > > as a Network Share, i.e. it has a SMB server? If not, then it's indeed
> > > again unspecific and hence unhelpful.
> >
> > almost out of the box.
> >
> > all that's needed is an app that supports the desired protocol. many of
> > them are free and some support more than just one protocol.
>
> You might think that's easy, but it very likely isn't easy at all!
it's easy.
> >
> > > Are you saying that - out of the box - an iOS device can be accessed
> > > as a Network Share, i.e. it has a SMB server? If not, then it's indeed
> > > again unspecific and hence unhelpful.
> >
> > almost out of the box.
> >
> > all that's needed is an app that supports the desired protocol. many of
> > them are free and some support more than just one protocol.
>
> You might think that's easy, but it very likely isn't easy at all!
> A SMB server on iOS probably needs jailbreaking in order to use the
> standard SMB port (445). At least that's - as I described - the case on
> Android and I think it's unlikely that iOS is less secure in this than
> Android.
looks like any other windows share.
i tried the wifi hd app, which worked on a mac using the default smb://.
and smb isnt the only protocol either. it's a 'generic example'.
> Without port 445 capability, the whole thing falls down, because
> - as I described - Windows doesn't allow a non-445 SMB port, so there's
> no point that OS X or/and Linux can.
>
> So to make your suggestion a workable one, give the URL of an iOS app
> which is a SMB server which uses port 445, but which does not require
> jailbreaking.
https://www.youtube.com/watch?v=YLwWkC9P7hk>
skip directly to win7 mounting:
<https://www.youtube.com/watch?v=YLwWkC9P7hk&t=123>
other options:
<https://itunes.apple.com/us/app/diskonphone-wireless-smb-server-hard-di
sk-drive/id1078556448?mt=8>
- SMB Server
- Transfer files from/to your PC running Windows or from/to your
Mac/Linux using the built in SMB(Samba) protocol.
- Work flawlessly with any OS that supports SMB protocol
<https://itunes.apple.com/us/app/wifi-hd-free-wireless-smb-usb-hard-disk-
drive-nfs-network/id311170976?mt=8>
- Share Files Using the built-in HTTP, and SMB File Servers
- Works flawlessly with Windows or Mac like a normal network drive.
> > he already said he had no issue with installing an ftp server app on
> > ios/android, nor did he ask about that part. i considered that part
> > done.
>
> You (probably) thought wrong.
> This is exactly the reason why one needs
> *specific* how-to instructions, instead of meaningless soundbites.
his vague questions, such as 'we need to architect a general solution'.
> > there are much easier ways to transfer stuff,
>
> Such as? Note that the transfer must be initiated from the *desktop*
> (i.e. OS X) device, not from the *mobile* device (which is indeed easy,
> but irrelevant). See my response to Snit about this requirement.
to be. the goal is to transfer files, not fit into some rigid method.
anyway, airdrop is by far the easiest, initiated on the sending device,
however it's mac/ios only.
for other systems, use a document provider or share extension that
supports the preferred protocol, which lets the user use their
favourite app to open and/or save to any remote system to which they
have access, even if the original app does not directly support said
protocol (thus the name extension).
the app only needs to support extensions, which is fairly common if the
app can open, create and/or modify documents.
for media (music, video, etc.) itunes is the best choice and makes
things *very* easy. new podcasts transfer while previously listened
ones are removed, entirely automatically (if configured to do so).
watch part of a movie on one device and continue later on another
device (or same device), without needing to write down times and fast
forward, which is what he said he does. smart playlists auto-update on
the fly. backups are also automatic (and for everything).
there are also cloud solutions, either on the local lan or the public
internet. documents put in the cloud can be encrypted for security
(perhaps overkill for local clouds, but still an option).
> > but that's what he asked for.
>
> Correct.
> >
> > the hosts file is an example, one which he said he plans on doing on
> > all of his devices. it was not a generic example.
>
> Yes it was. It was *specifically* labeled as an example, so by
> definition, it's generic.
it was a very specific example he claimed to want to do, not a random
file type.
> > transferring a 'family photo album' does not need mounting the file
> > system either.
> >
> > there is no reason to mount the file system at all to copy files.
>
> See above. It's needed if one wants to initiate the transfer from the
> desktop. For that scenario, the desktop is the client and the iOS device
> needs to be a server.
> Note that "mount" should be interpreted as the concept, not the
> literal term. For example on Linux, accessing a (SMB) Network Share is
> not the same as accessing a mounted volume. And on Windows the concept
> of mounting a volume does not really exist, but some vendors use the
> term because it's a common concept.
> > clearer now?
>
> I hope the *real* requirements are now clear to you.
> > there are *much* easier ways to do what he claims to want to do, except
> > that he is fixated on mounting the file system to do it and refuses any
> > alternatives.
>
> As I said, don't (only) humour him, but humour us as well. So feel
> free to propose - specific and detailed - alternatives, which meet the
> given requirements.
so far, all you've said is you have a 'similar' situation, therefore
any answers cannot be specific and detailed because they could be
totally wrong for your particular situation.
Frank Slootweg
Oct 15, 2017, 4:47:21 PM10/15/17
to
nospam <nos...@nospam.invalid> wrote:
> In article <os0dhs...@ID-201911.user.individual.net>, Frank Slootweg
> <th...@ddress.is.invalid> wrote:
>
> > > > Are you saying that - out of the box - an iOS device can be accessed
> > > > as a Network Share, i.e. it has a SMB server? If not, then it's indeed
> > > > again unspecific and hence unhelpful.
> > >
> > > almost out of the box.
> > >
> > > all that's needed is an app that supports the desired protocol. many of
> > > them are free and some support more than just one protocol.
> >
> > You might think that's easy, but it very likely isn't easy at all!
>
> it's easy.
>
> > A SMB server on iOS probably needs jailbreaking in order to use the
> > standard SMB port (445). At least that's - as I described - the case on
> > Android and I think it's unlikely that iOS is less secure in this than
> > Android.
>
> the examples below make no mention of alternate ports and the video
> looks like any other windows share.
Hmmm! Strange that Android is protective of standard assigned ports,
> In article <os0dhs...@ID-201911.user.individual.net>, Frank Slootweg
> <th...@ddress.is.invalid> wrote:
>
> > > > Are you saying that - out of the box - an iOS device can be accessed
> > > > as a Network Share, i.e. it has a SMB server? If not, then it's indeed
> > > > again unspecific and hence unhelpful.
> > >
> > > almost out of the box.
> > >
> > > all that's needed is an app that supports the desired protocol. many of
> > > them are free and some support more than just one protocol.
> >
> > You might think that's easy, but it very likely isn't easy at all!
>
> it's easy.
>
> > A SMB server on iOS probably needs jailbreaking in order to use the
> > standard SMB port (445). At least that's - as I described - the case on
> > Android and I think it's unlikely that iOS is less secure in this than
> > Android.
>
> the examples below make no mention of alternate ports and the video
> looks like any other windows share.
while iOS apparently isn't.
Anyway, thanks for these! AFAICT, they fit 'harry''s bill exactly.
(That is, if he doesn't moves the goalposts! :-()
> i tried the wifi hd app, which worked on a mac using the default smb://.
(Well, at least I do.)
> and smb isnt the only protocol either. it's a 'generic example'.
NFS (barf), FTP (barf) and - AFAICT - WebDAV (Did I forget any other
candidates?).
> > Without port 445 capability, the whole thing falls down, because
> > - as I described - Windows doesn't allow a non-445 SMB port, so there's
> > no point that OS X or/and Linux can.
> >
> > So to make your suggestion a workable one, give the URL of an iOS app
> > which is a SMB server which uses port 445, but which does not require
> > jailbreaking.
>
> fhub - mac/winxp/ubuntu/win7 demoed:
> https://www.youtube.com/watch?v=YLwWkC9P7hk>
> skip directly to win7 mounting:
> <https://www.youtube.com/watch?v=YLwWkC9P7hk&t=123>
does funny things on my side (redirects to a plane tickets site) and
when accessed from their Facebook page make Facebook barf ("We believe
the link you are trying to visit is malicious. For your safety, we have
blocked it."), but that's kind of irrelevant, because the two others
seem to fit the bill.
> other options:
> <https://itunes.apple.com/us/app/diskonphone-wireless-smb-server-hard-di
> sk-drive/id1078556448?mt=8>
> - SMB Server
> - Transfer files from/to your PC running Windows or from/to your
> Mac/Linux using the built in SMB(Samba) protocol.
> - Work flawlessly with any OS that supports SMB protocol
>
> <https://itunes.apple.com/us/app/wifi-hd-free-wireless-smb-usb-hard-disk-
> drive-nfs-network/id311170976?mt=8>
> - Share Files Using the built-in HTTP, and SMB File Servers
> - Works flawlessly with Windows or Mac like a normal network drive.
[Now moot - or otherwise irrelevant - points deleted.]
> > As I said, don't (only) humour him, but humour us as well. So feel
> > free to propose - specific and detailed - alternatives, which meet the
> > given requirements.
>
> ask a specific question and you will get a specific answer.
to be helpful/useful. After pressing you, you delivered and I thank you
for that, but it would be nice if we wouldn't have to press/pull so
much every time.
> so far, all you've said is you have a 'similar' situation, therefore
> any answers cannot be specific and detailed because they could be
> totally wrong for your particular situation.
your above quoted post are spot on, because I understand what 'harry'
(says he) wants/needs and I do know that I want/need exactly the same.
But to elaborate on my wants/needs:
As I said, I want/need this functionality for myself (access files in
Android filesystems from Windows) and a close relative (access files in
iOS(/Android) file system(s) from OS X(/Windows).
For myself, the main purpose/use is to be able to use Windows-based
file backup software to make full and incremental backup of the
(exposed) file systems of my Android devices.
For my close relative, her main purpose/use is what I tell her it is!
:-)
Bottom line(s):
- For iOS, the problem is solved for all three desktop OSs, OS X,
Windows and Linux.
- For Android, the problem is *not* solved, because FTP is the 'wrong'
protocol, the Android FTP server cannot be accessed as a Network
*Share*, but only as a (Windows) Network *Drive* and setting up the
Network Drives is a clumsy process.
And thanks again!
Frank Slootweg
Oct 15, 2017, 4:48:55 PM10/15/17
to
nospam
Oct 15, 2017, 5:16:30 PM10/15/17
to
In article <os0ohb...@ID-201911.user.individual.net>, Frank Slootweg
> > and smb isnt the only protocol either. it's a 'generic example'.
>
> Indeed. But - IMO - SMB is the preferred cross-platform method (over
> NFS (barf), FTP (barf) and - AFAICT - WebDAV (Did I forget any other
> candidates?).
my preference is let the app deal with it, otherwise, sftp or http.
> > > Without port 445 capability, the whole thing falls down, because
> > > - as I described - Windows doesn't allow a non-445 SMB port, so there's
> > > no point that OS X or/and Linux can.
> > >
> > > So to make your suggestion a workable one, give the URL of an iOS app
> > > which is a SMB server which uses port 445, but which does not require
> > > jailbreaking.
> >
> > fhub - mac/winxp/ubuntu/win7 demoed:
> > https://www.youtube.com/watch?v=YLwWkC9P7hk>
> > skip directly to win7 mounting:
> > <https://www.youtube.com/watch?v=YLwWkC9P7hk&t=123>
>
> This one seems to be somewhat broken. The URL <http:/www.fhubapp.com>
> does funny things on my side (redirects to a plane tickets site) and
> when accessed from their Facebook page make Facebook barf ("We believe
> the link you are trying to visit is malicious. For your safety, we have
> blocked it."), but that's kind of irrelevant, because the two others
> seem to fit the bill.
the facebook page works here (no login necessary).
the app appears to no longer be available, with the site repurposed by
spammers. however, the video does prove that it can be done.
<http://fhubapp.blogspot.com>
<https://www.facebook.com/FHubApp/>
>
> But to elaborate on my wants/needs:
>
> As I said, I want/need this functionality for myself (access files in
> Android filesystems from Windows) and a close relative (access files in
> iOS(/Android) file system(s) from OS X(/Windows).
what tasks do you (or relative) want to do?
> For myself, the main purpose/use is to be able to use Windows-based
> file backup software to make full and incremental backup of the
> (exposed) file systems of my Android devices.
is backup the only task?
if so, itunes on mac or windows backs up everything without user
intervention (or not, if you prefer manually invoking it) and also
syncs most types of files.
> For my close relative, her main purpose/use is what I tell her it is!
> :-)
>
> Bottom line(s):
>
> - For iOS, the problem is solved for all three desktop OSs, OS X,
> Windows and Linux.
>
> - For Android, the problem is *not* solved, because FTP is the 'wrong'
> protocol, the Android FTP server cannot be accessed as a Network
> *Share*, but only as a (Windows) Network *Drive* and setting up the
> Network Drives is a clumsy process.
>
> And thanks again!
there's that android walled garden again :)
<th...@ddress.is.invalid> wrote:
> >
> > > A SMB server on iOS probably needs jailbreaking in order to use the
> > > standard SMB port (445). At least that's - as I described - the case on
> > > Android and I think it's unlikely that iOS is less secure in this than
> > > Android.
> >
> > the examples below make no mention of alternate ports and the video
> > looks like any other windows share.
>
> Hmmm! Strange that Android is protective of standard assigned ports,
> while iOS apparently isn't.
that's android's walled garden :)
> >
> > > A SMB server on iOS probably needs jailbreaking in order to use the
> > > standard SMB port (445). At least that's - as I described - the case on
> > > Android and I think it's unlikely that iOS is less secure in this than
> > > Android.
> >
> > the examples below make no mention of alternate ports and the video
> > looks like any other windows share.
>
> Hmmm! Strange that Android is protective of standard assigned ports,
> while iOS apparently isn't.
> > and smb isnt the only protocol either. it's a 'generic example'.
>
> Indeed. But - IMO - SMB is the preferred cross-platform method (over
> NFS (barf), FTP (barf) and - AFAICT - WebDAV (Did I forget any other
> candidates?).
> > > Without port 445 capability, the whole thing falls down, because
> > > - as I described - Windows doesn't allow a non-445 SMB port, so there's
> > > no point that OS X or/and Linux can.
> > >
> > > So to make your suggestion a workable one, give the URL of an iOS app
> > > which is a SMB server which uses port 445, but which does not require
> > > jailbreaking.
> >
> > fhub - mac/winxp/ubuntu/win7 demoed:
> > https://www.youtube.com/watch?v=YLwWkC9P7hk>
> > skip directly to win7 mounting:
> > <https://www.youtube.com/watch?v=YLwWkC9P7hk&t=123>
>
> This one seems to be somewhat broken. The URL <http:/www.fhubapp.com>
> does funny things on my side (redirects to a plane tickets site) and
> when accessed from their Facebook page make Facebook barf ("We believe
> the link you are trying to visit is malicious. For your safety, we have
> blocked it."), but that's kind of irrelevant, because the two others
> seem to fit the bill.
the app appears to no longer be available, with the site repurposed by
spammers. however, the video does prove that it can be done.
<http://fhubapp.blogspot.com>
<https://www.facebook.com/FHubApp/>
>
> But to elaborate on my wants/needs:
>
> As I said, I want/need this functionality for myself (access files in
> Android filesystems from Windows) and a close relative (access files in
> iOS(/Android) file system(s) from OS X(/Windows).
> For myself, the main purpose/use is to be able to use Windows-based
> file backup software to make full and incremental backup of the
> (exposed) file systems of my Android devices.
if so, itunes on mac or windows backs up everything without user
intervention (or not, if you prefer manually invoking it) and also
syncs most types of files.
> For my close relative, her main purpose/use is what I tell her it is!
> :-)
>
> Bottom line(s):
>
> - For iOS, the problem is solved for all three desktop OSs, OS X,
> Windows and Linux.
>
> - For Android, the problem is *not* solved, because FTP is the 'wrong'
> protocol, the Android FTP server cannot be accessed as a Network
> *Share*, but only as a (Windows) Network *Drive* and setting up the
> Network Drives is a clumsy process.
>
> And thanks again!
Frank Slootweg
Oct 15, 2017, 5:30:44 PM10/15/17
to
nospam <nos...@nospam.invalid> wrote:
> In article <os0ohb...@ID-201911.user.individual.net>, Frank Slootweg
> <th...@ddress.is.invalid> wrote:
[...]
> In article <os0ohb...@ID-201911.user.individual.net>, Frank Slootweg
> <th...@ddress.is.invalid> wrote:
> > Hmmm! Strange that Android is protective of standard assigned ports,
> > while iOS apparently isn't.
>
> that's android's walled garden :)
Touche! I had that one coming! :-)
> > while iOS apparently isn't.
>
> that's android's walled garden :)
[Much deleted.]
> > But to elaborate on my wants/needs:
> >
> > As I said, I want/need this functionality for myself (access files in
> > Android filesystems from Windows) and a close relative (access files in
> > iOS(/Android) file system(s) from OS X(/Windows).
>
> what tasks do you (or relative) want to do?
>
> > For myself, the main purpose/use is to be able to use Windows-based
> > file backup software to make full and incremental backup of the
> > (exposed) file systems of my Android devices.
>
> is backup the only task?
file access/copying pursposes as well. But note that for *me* it's
"access files in Android filesystems from Windows" and that's the
Android walled garden one!
> if so, itunes on mac or windows backs up everything without user
> intervention (or not, if you prefer manually invoking it) and also
> syncs most types of files.
tell me that iTunes can backup an *Android* device, are you!?)
> > For my close relative, her main purpose/use is what I tell her it is!
> > :-)
> >
> > Bottom line(s):
> >
> > - For iOS, the problem is solved for all three desktop OSs, OS X,
> > Windows and Linux.
> >
> > - For Android, the problem is *not* solved, because FTP is the 'wrong'
> > protocol, the Android FTP server cannot be accessed as a Network
> > *Share*, but only as a (Windows) Network *Drive* and setting up the
> > Network Drives is a clumsy process.
> >
> > And thanks again!
>
> there's that android walled garden again :)
for quite some time, if I don't want to have egg on my face or/and have
to eat humble pie.
Thanks for the good and pleasant outcome of this exchange!
nospam
Oct 15, 2017, 9:37:29 PM10/15/17
to
In article <os0r2q...@ID-201911.user.individual.net>, Frank Slootweg
my point is to use the best tools for the job versus a universal
solution that does a less than optimal job.
for backing up ios devices, it's itunes (and/or icloud), which can be
used alongside whatever you use for backing up android devices.
> > > For my close relative, her main purpose/use is what I tell her it is!
> > > :-)
> > >
> > > Bottom line(s):
> > >
> > > - For iOS, the problem is solved for all three desktop OSs, OS X,
> > > Windows and Linux.
> > >
> > > - For Android, the problem is *not* solved, because FTP is the 'wrong'
> > > protocol, the Android FTP server cannot be accessed as a Network
> > > *Share*, but only as a (Windows) Network *Drive* and setting up the
> > > Network Drives is a clumsy process.
> > >
> > > And thanks again!
> >
> > there's that android walled garden again :)
>
> Yeah, I'll have to refrain from referring to the Apple walled garden
> for quite some time, if I don't want to have egg on my face or/and have
> to eat humble pie.
>
> Thanks for the good and pleasant outcome of this exchange!
no problem. try to keep it that way :)
<th...@ddress.is.invalid> wrote:
> > is backup the only task?
>
> It is the main task, but once I get it going, I will use it for other
> file access/copying pursposes as well. But note that for *me* it's
> "access files in Android filesystems from Windows" and that's the
> Android walled garden one!
>
> > if so, itunes on mac or windows backs up everything without user
> > intervention (or not, if you prefer manually invoking it) and also
> > syncs most types of files.
>
> I know, I know! Don't rub it in! :-) (Long shot: You're not trying to
> tell me that iTunes can backup an *Android* device, are you!?)
no.
> > is backup the only task?
>
> It is the main task, but once I get it going, I will use it for other
> file access/copying pursposes as well. But note that for *me* it's
> "access files in Android filesystems from Windows" and that's the
> Android walled garden one!
>
> > if so, itunes on mac or windows backs up everything without user
> > intervention (or not, if you prefer manually invoking it) and also
> > syncs most types of files.
>
> I know, I know! Don't rub it in! :-) (Long shot: You're not trying to
> tell me that iTunes can backup an *Android* device, are you!?)
my point is to use the best tools for the job versus a universal
solution that does a less than optimal job.
for backing up ios devices, it's itunes (and/or icloud), which can be
used alongside whatever you use for backing up android devices.
> > > For my close relative, her main purpose/use is what I tell her it is!
> > > :-)
> > >
> > > Bottom line(s):
> > >
> > > - For iOS, the problem is solved for all three desktop OSs, OS X,
> > > Windows and Linux.
> > >
> > > - For Android, the problem is *not* solved, because FTP is the 'wrong'
> > > protocol, the Android FTP server cannot be accessed as a Network
> > > *Share*, but only as a (Windows) Network *Drive* and setting up the
> > > Network Drives is a clumsy process.
> > >
> > > And thanks again!
> >
> > there's that android walled garden again :)
>
> Yeah, I'll have to refrain from referring to the Apple walled garden
> for quite some time, if I don't want to have egg on my face or/and have
> to eat humble pie.
>
> Thanks for the good and pleasant outcome of this exchange!
harry newton
Oct 19, 2017, 2:10:09 PM10/19/17
to
He who is Frank Slootweg said on 14 Oct 2017 20:21:03 GMT:
> I dare you to quote *one* example where you actually gave *specific*
> how-to instructions, instead of unspecific, unhelpful, pathetic
> soundbites like the ones you're uttering in this thread.
Hi Frank,
You know as well as anyone that the signal-to-noise ratio for the Apple
apologists is 0:100 or at best 1:100, where 99% of their posts are their
well-practiced utterly factless trolls designed only to *destroy* any
technical factual thread on networking in the real world.
Therefore, to even respond to these incessant and utterly useless Apple
trolls (none of whom even know a megabit per second from a decibel!) is to
immediately fall prey to their experience in attrition tactics
- and - as you must be aware - none of the iOS trolls (e.g., Jolly Roger,
Snit, nospam, etc.) have any intention of ever being helpful in *any*
thread which they infests, and never one on networking in the real world
(which nospam insists doesn't exist).
Moving forward technically, I've installed the samba configuration tool on
Ubuntu 16.04LTS using the following sequence of commands that others can
follow in turn.
The problem is I haven't found a good tutorial, so I'm writing it as we
speak (but making mistakes as I go along, which I try to prevent others
from making by the writeup below).
First I installed the samba system configuration tool:
$ sudo apt-get install system-config-samba
<http://wetakepic.com/images/2017/10/19/1.jpg>
Surprisingly, it won't open without a (blank works) configuration file:
<http://wetakepic.com/images/2017/10/19/2.jpg>
$ gksu system-config-samba
File "/usr/sbin/system-config-samba", line 45, in <module>
mainWindow.MainWindow(debug_flag)
File "/usr/share/system-config-samba/mainWindow.py", line 121, in
__init__
self.basic_preferences_win =
basicPreferencesWin.BasicPreferencesWin(self, self.xml, self.samba_data,
self.samba_backend, self.main_window)
File "/usr/share/system-config-samba/basicPreferencesWin.py", line 97, in
__init__
self.admin = libuser.admin()
SystemError: could not open configuration file `/etc/libuser.conf': No such
file or directory
x@x:~$ sudo touch /etc/libuser.conf
x@x:~$ gksu system-config-samba
That trick works to bring up the samba configuration tool:
<http://wetakepic.com/images/2017/10/19/3.jpg>
I wasn't sure what to set "Preferences > Server Settings" to since I want
the shares to be wide open at first, since I want the "guest" account to
work sans challenge, so I'm still experimenting with the various settings:
<http://wetakepic.com/images/2017/10/19/4.jpg>
But at least I was able to add a share using "File > Add Share":
<http://wetakepic.com/images/2017/10/19/5.jpg>
The main problem is that there aren't any good tutorials for what I'm
trying to accomplish, which is simply to network the entire available
mobile device file system onto the Linux desktop over the LAN Wi-Fi.
> I dare you to quote *one* example where you actually gave *specific*
> how-to instructions, instead of unspecific, unhelpful, pathetic
> soundbites like the ones you're uttering in this thread.
You know as well as anyone that the signal-to-noise ratio for the Apple
apologists is 0:100 or at best 1:100, where 99% of their posts are their
well-practiced utterly factless trolls designed only to *destroy* any
technical factual thread on networking in the real world.
Therefore, to even respond to these incessant and utterly useless Apple
trolls (none of whom even know a megabit per second from a decibel!) is to
immediately fall prey to their experience in attrition tactics
- and - as you must be aware - none of the iOS trolls (e.g., Jolly Roger,
Snit, nospam, etc.) have any intention of ever being helpful in *any*
thread which they infests, and never one on networking in the real world
(which nospam insists doesn't exist).
Moving forward technically, I've installed the samba configuration tool on
Ubuntu 16.04LTS using the following sequence of commands that others can
follow in turn.
The problem is I haven't found a good tutorial, so I'm writing it as we
speak (but making mistakes as I go along, which I try to prevent others
from making by the writeup below).
First I installed the samba system configuration tool:
$ sudo apt-get install system-config-samba
<http://wetakepic.com/images/2017/10/19/1.jpg>
Surprisingly, it won't open without a (blank works) configuration file:
<http://wetakepic.com/images/2017/10/19/2.jpg>
$ gksu system-config-samba
File "/usr/sbin/system-config-samba", line 45, in <module>
mainWindow.MainWindow(debug_flag)
File "/usr/share/system-config-samba/mainWindow.py", line 121, in
__init__
self.basic_preferences_win =
basicPreferencesWin.BasicPreferencesWin(self, self.xml, self.samba_data,
self.samba_backend, self.main_window)
File "/usr/share/system-config-samba/basicPreferencesWin.py", line 97, in
__init__
self.admin = libuser.admin()
SystemError: could not open configuration file `/etc/libuser.conf': No such
file or directory
x@x:~$ sudo touch /etc/libuser.conf
x@x:~$ gksu system-config-samba
That trick works to bring up the samba configuration tool:
<http://wetakepic.com/images/2017/10/19/3.jpg>
I wasn't sure what to set "Preferences > Server Settings" to since I want
the shares to be wide open at first, since I want the "guest" account to
work sans challenge, so I'm still experimenting with the various settings:
<http://wetakepic.com/images/2017/10/19/4.jpg>
But at least I was able to add a share using "File > Add Share":
<http://wetakepic.com/images/2017/10/19/5.jpg>
The main problem is that there aren't any good tutorials for what I'm
trying to accomplish, which is simply to network the entire available
mobile device file system onto the Linux desktop over the LAN Wi-Fi.
joe
Oct 19, 2017, 2:24:27 PM10/19/17
to
"the entire available mobile device file system onto the Linux desktop".
Do you even know what you are trying to achieve?
Snit
Oct 19, 2017, 2:46:20 PM10/19/17
to
On 10/19/17, 11:24 AM, in article osaqko$1jbu$1...@gioia.aioe.org, "joe"
He is trying to find things which can be done on Android but not Linux so he
can push his lie that nothing that can be done on iOS cannot be done on
Android. He fails to see why his "logic" here fails.
The reality is each does things the other does not, AND even on features
they both share each has areas where one does things better than the other.
can push his lie that nothing that can be done on iOS cannot be done on
Android. He fails to see why his "logic" here fails.
The reality is each does things the other does not, AND even on features
they both share each has areas where one does things better than the other.
harry newton
Oct 20, 2017, 12:26:34 AM10/20/17
to
He who is joe said on Thu, 19 Oct 2017 13:24:26 -0500:
> Creating a SMB share on the Linux system does nothing toward getting
> "the entire available mobile device file system onto the Linux desktop".
>
> Do you even know what you are trying to achieve?
Do you even know how to read?
You missed completely that Frank covered this topic one or two days ago
where I replied that I was testing out what functionality exists.
Do you even know how to read?
> Creating a SMB share on the Linux system does nothing toward getting
> "the entire available mobile device file system onto the Linux desktop".
>
> Do you even know what you are trying to achieve?
You missed completely that Frank covered this topic one or two days ago
where I replied that I was testing out what functionality exists.
Do you even know how to read?
harry newton
Oct 20, 2017, 12:31:11 AM10/20/17
to
He who is Snit said on Thu, 19 Oct 2017 11:46:10 -0700:
> He is trying to find things which can be done on Android but not Linux so he
> can push his lie that nothing that can be done on iOS cannot be done on
> Android. He fails to see why his "logic" here fails.
>
> The reality is each does things the other does not, AND even on features
> they both share each has areas where one does things better than the other.
Every single thing you write only proves that you're an utter moron.
Witness this idiotic video you posited that *proved* (heh heh) that iOS has
functionality that you simply made up (it never had it even though you
trolled that video for *weeks* to all who would listen).
<https://groups.google.com/d/msg/comp.mobile.ipad/-T7FEXIdU9Q/Dhy-LFH3AwAJ>
Please write something *intelligent* when you iOS apologists (Snit, nospam,
& Jolly Roger) finally figure out the difference between a megabit and a
decibel when you next fabricate non existent iOS networking functionality.
> He is trying to find things which can be done on Android but not Linux so he
> can push his lie that nothing that can be done on iOS cannot be done on
> Android. He fails to see why his "logic" here fails.
>
> The reality is each does things the other does not, AND even on features
> they both share each has areas where one does things better than the other.
Witness this idiotic video you posited that *proved* (heh heh) that iOS has
functionality that you simply made up (it never had it even though you
trolled that video for *weeks* to all who would listen).
<https://groups.google.com/d/msg/comp.mobile.ipad/-T7FEXIdU9Q/Dhy-LFH3AwAJ>
Please write something *intelligent* when you iOS apologists (Snit, nospam,
& Jolly Roger) finally figure out the difference between a megabit and a
decibel when you next fabricate non existent iOS networking functionality.
harry newton
Oct 20, 2017, 12:34:41 AM10/20/17
to
He who is harry newton said on Fri, 20 Oct 2017 04:31:10 +0000 (UTC):
> Please write something *intelligent* when you iOS apologists (Snit, nospam,
> & Jolly Roger) finally figure out the difference between a megabit and a
> decibel when you next fabricate non existent iOS networking functionality.
What's hilarious is that the iOS apologists Jolly Roger, nospam and Snit
trolled that video of completely fabricated iOS networking functionality
for weeks, never once even *looking* (or comprehending) that their app
merely showed "pretty pictures", which fooled every one of them even to
this day, where only Snit has admitted he simply made it all up.
This is Android: <http://wetakepic.com/images/2017/10/11/2wifianalyzer.jpg>
This is iOS: <http://wetakepic.com/images/2017/10/11/wifi_sweetspots.jpg>
I only speak fact.
> Please write something *intelligent* when you iOS apologists (Snit, nospam,
> & Jolly Roger) finally figure out the difference between a megabit and a
> decibel when you next fabricate non existent iOS networking functionality.
trolled that video of completely fabricated iOS networking functionality
for weeks, never once even *looking* (or comprehending) that their app
merely showed "pretty pictures", which fooled every one of them even to
this day, where only Snit has admitted he simply made it all up.
This is Android: <http://wetakepic.com/images/2017/10/11/2wifianalyzer.jpg>
This is iOS: <http://wetakepic.com/images/2017/10/11/wifi_sweetspots.jpg>
I only speak fact.
Snit
Oct 20, 2017, 2:12:08 AM10/20/17
to
On 10/19/17, 9:31 PM, in article osbu6d$1ev6$1...@gioia.aioe.org, "harry
Have you figured out the difference between:
* Record screen AND voice AND device sounds without jail breaking.
Also record desktop screen and sound with the time coordinated.
And:
* Recording the screen.
I bet not. When asked you run. EVERY. SINGLE. TIME.
* Record screen AND voice AND device sounds without jail breaking.
Also record desktop screen and sound with the time coordinated.
And:
* Recording the screen.
I bet not. When asked you run. EVERY. SINGLE. TIME.
Carlos E.R.
Oct 20, 2017, 10:00:13 AM10/20/17
to
--
Cheers, Carlos.
harry newton
Oct 20, 2017, 11:48:56 AM10/20/17
to
He who is Snit said on Thu, 19 Oct 2017 23:12:02 -0700:
> Have you figured out the difference between:
>
> * Record screen AND voice AND device sounds without jail breaking.
> Also record desktop screen and sound with the time coordinated.
>
> And:
>
> * Recording the screen.
>
> I bet not. When asked you run. EVERY. SINGLE. TIME.
Snit,
I'm going to let you know that every time you cut and paste that, I just
laugh because you're making a fool of yourself just as you made a total
fool of yourself, Jolly Roger, and nospam when you completely fabricated
iOS functionality trolling that video for *weeks* simply because you're
utterly *desperate* to find something ... anything ... that you can do on
iOS that isn't already done on Android.
You iOS apologists are so utterly *clueless* that you can't even imagine
that Android records the audio along with the video.
I realize you're *desperate* for something (anything!) that iOS can do that
Android can't, but recording audio along with video is never going to be
where you find it.
The fact you keep trolling that cut-and-paste idiocy just makes you look
like the utter fool you are - since you can't even *comprehend* that
Android records everything (just as iOS does).
I never said Android had an edge on recording audio and video over iOS.
You keep trolling this completely fabricated cut-and-paste.
And then you call *me* a troll.
This is the *only* time I will respond, unless I need to make an utter fool
out of you, nospam, and Jolly Roger again, as I did with your idiotic video
proving the three of you don't know the difference between a decibel and a
megabit.
--
iOS apogists are so dumb that they can't fathom Android can record audio!
> Have you figured out the difference between:
>
> * Record screen AND voice AND device sounds without jail breaking.
> Also record desktop screen and sound with the time coordinated.
>
> And:
>
> * Recording the screen.
>
> I bet not. When asked you run. EVERY. SINGLE. TIME.
I'm going to let you know that every time you cut and paste that, I just
laugh because you're making a fool of yourself just as you made a total
fool of yourself, Jolly Roger, and nospam when you completely fabricated
iOS functionality trolling that video for *weeks* simply because you're
utterly *desperate* to find something ... anything ... that you can do on
iOS that isn't already done on Android.
You iOS apologists are so utterly *clueless* that you can't even imagine
that Android records the audio along with the video.
I realize you're *desperate* for something (anything!) that iOS can do that
Android can't, but recording audio along with video is never going to be
where you find it.
The fact you keep trolling that cut-and-paste idiocy just makes you look
like the utter fool you are - since you can't even *comprehend* that
Android records everything (just as iOS does).
I never said Android had an edge on recording audio and video over iOS.
You keep trolling this completely fabricated cut-and-paste.
And then you call *me* a troll.
This is the *only* time I will respond, unless I need to make an utter fool
out of you, nospam, and Jolly Roger again, as I did with your idiotic video
proving the three of you don't know the difference between a decibel and a
megabit.
--
iOS apogists are so dumb that they can't fathom Android can record audio!
harry newton
Oct 20, 2017, 11:53:34 AM10/20/17
to
He who is Carlos E.R. said on Fri, 20 Oct 2017 15:57:45 +0200:
> This is OFFTOPIC.
Carlos,
Be realistic.
Notice how Snit keeps trolling that cut-and-paste claiming that Android
can't record audio with video (for heaven's sake)?
He's so desperate to claim Apple functionality that he pasted that so many
times and I didn't respond but then when I tell him to cut the crap, you
chastise me.
Why don't you tell Snit, nospam, and Jolly Roger to cut the crap?
Not one of them even *comprehends* the question - and certainly not a
single post by any of them was on topic.
Jesus. Tell *them* to cut the crap.
> This is OFFTOPIC.
Carlos,
Be realistic.
Notice how Snit keeps trolling that cut-and-paste claiming that Android
can't record audio with video (for heaven's sake)?
He's so desperate to claim Apple functionality that he pasted that so many
times and I didn't respond but then when I tell him to cut the crap, you
chastise me.
Why don't you tell Snit, nospam, and Jolly Roger to cut the crap?
Not one of them even *comprehends* the question - and certainly not a
single post by any of them was on topic.
Jesus. Tell *them* to cut the crap.
Jolly Roger
Oct 20, 2017, 11:59:55 AM10/20/17
to
On 2017-10-20, harry newton <ha...@is.invalid> wrote:
>
> The fact you keep trolling that cut-and-paste idiocy just makes you look
> like the utter fool you are
Nym-shifting Apple-hating moron troll is crying because someone is
>
> The fact you keep trolling that cut-and-paste idiocy just makes you look
> like the utter fool you are
playing his own idiotic cut-and-paste game. Pure comedy! : D
--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.
JR
Snit
Oct 20, 2017, 2:12:58 PM10/20/17
to
On 10/20/17, 8:48 AM, in article osd5t5$1jmg$1...@gioia.aioe.org, "harry
A simple "no" would have done. No, you have NOT shown you understand the
difference. Fair enough. I hope some day you do.
Best wishes!
difference. Fair enough. I hope some day you do.
Best wishes!
Snit
Oct 20, 2017, 2:32:06 PM10/20/17
to
On 10/20/17, 8:53 AM, in article osd65r$1k8l$1...@gioia.aioe.org, "harry
concepts.
> He's so desperate to claim Apple functionality that he pasted that so many
> times and I didn't respond but then when I tell him to cut the crap, you
> chastise me.
>
> Why don't you tell Snit, nospam, and Jolly Roger to cut the crap?
> Not one of them even *comprehends* the question - and certainly not a
> single post by any of them was on topic.
>
> Jesus. Tell *them* to cut the crap.
newton" <ha...@is.invalid> wrote:
> He who is Carlos E.R. said on Fri, 20 Oct 2017 15:57:45 +0200:
>
>> This is OFFTOPIC.
>
> Carlos,
> Be realistic.
>
> Notice how Snit keeps trolling that cut-and-paste claiming that Android
> can't record audio with video (for heaven's sake)?
A claim I never made, of course. But you STILL cannot understand basic
> He who is Carlos E.R. said on Fri, 20 Oct 2017 15:57:45 +0200:
>
>> This is OFFTOPIC.
>
> Carlos,
> Be realistic.
>
> Notice how Snit keeps trolling that cut-and-paste claiming that Android
> can't record audio with video (for heaven's sake)?
concepts.
> He's so desperate to claim Apple functionality that he pasted that so many
> times and I didn't respond but then when I tell him to cut the crap, you
> chastise me.
>
> Why don't you tell Snit, nospam, and Jolly Roger to cut the crap?
> Not one of them even *comprehends* the question - and certainly not a
> single post by any of them was on topic.
>
> Jesus. Tell *them* to cut the crap.
harry newton
Oct 20, 2017, 8:16:06 PM10/20/17
to
He who is J.O. Aho said on Fri, 20 Oct 2017 18:11:25 +0200:
> So what's wrong with setting up a ftp server on your devices and then
> use ftp mounting option in the file manager you use?
I was always able to easily connect all the mobile devices over the WiFi
LAN to Linux & Windows using the native file explorers on Linux (aka
Nautilus) and Windows (aka Windows file explorer):
<http://wetakepic.com/images/2017/10/20/nautilus_ftp.jpg>
In fact, that's how I've been transferring all the mobile-device
screenshots in this thread.
<http://wetakepic.com/images/2017/10/20/android_connect.jpg>
The reason for asking the question was to see if we could find a *better*
way to mount mobile devices over the WiFi LAN in any typical household than
FTP that worked the same for all the consumer platforms:
1. Linux, Windows, MacOS
2. Android, iOS
I *already* had that FTP-server suggestion working perfectly and always had
FTP mounting working well, as evidenced by the original post.
<http://wetakepic.com/images/2017/10/20/nautilus_ftp.jpg>
For example, here's how to mount the entire Android file system using
Nautilus on Ubuntu 16.04LTS:
Nautilus: Connect to server > ftp://192.168.1.10:3721
And here's the Android & Windows hosts file on Windows:
<http://wetakepic.com/images/2017/10/10/hosts8407d.jpg>
And it even works, sort of, for iOS, which doesn't really play nice in the
real world with Linux over Wi-Fi (so we always do iOS last as it's the
least capable of all common consumer platforms).
In the end, it seems that we tested three methods, each of which has
different capabilities:
A. FTP server on the mobile device (works for all platforms)
B. SMB server on the desktop (works differently for all platforms)
C. KDE-Connect (works differently for all platforms)
Note:
On Android, I tested a plethora of *other* desktop/mobile connections:
<http://wetakepic.com/images/2017/10/20/android_connect.jpg>
Each of which works differently in some respects.
> I guess it can be a
> bit difficult to determine the ip-number if not permanently assigned to
> devices.
We have a long thread on that topic where it's not a problem in a practical
sense, since there are permanent solutions and the IP address is relatively
static in a typical household anyway.
The permanent solution is just to set up the router to give a static IP
address to each mobile device, where there are plenty of other solutions
that actually work even though they would seem to be sub optimal by way of
comparison.
For example, Android can *request* a certain IP address based on SSID,
which happens to work just fine in practice, even though clashes are
theoretically possible.
Likewise, doing nothing works just fine also, in a typical household with
the same devices going on and off the network, as the lease seems to be
good enough for all practical purposes.
Even if the FTP IP address did change, it's easily enough sniffed out on
Linux and on the router by MAC address, so, again, the IP address, in
practice, is the least of the issues.
> So what's wrong with setting up a ftp server on your devices and then
> use ftp mounting option in the file manager you use?
I was always able to easily connect all the mobile devices over the WiFi
LAN to Linux & Windows using the native file explorers on Linux (aka
Nautilus) and Windows (aka Windows file explorer):
<http://wetakepic.com/images/2017/10/20/nautilus_ftp.jpg>
In fact, that's how I've been transferring all the mobile-device
screenshots in this thread.
<http://wetakepic.com/images/2017/10/20/android_connect.jpg>
The reason for asking the question was to see if we could find a *better*
way to mount mobile devices over the WiFi LAN in any typical household than
FTP that worked the same for all the consumer platforms:
1. Linux, Windows, MacOS
2. Android, iOS
I *already* had that FTP-server suggestion working perfectly and always had
FTP mounting working well, as evidenced by the original post.
<http://wetakepic.com/images/2017/10/20/nautilus_ftp.jpg>
For example, here's how to mount the entire Android file system using
Nautilus on Ubuntu 16.04LTS:
Nautilus: Connect to server > ftp://192.168.1.10:3721
And here's the Android & Windows hosts file on Windows:
<http://wetakepic.com/images/2017/10/10/hosts8407d.jpg>
And it even works, sort of, for iOS, which doesn't really play nice in the
real world with Linux over Wi-Fi (so we always do iOS last as it's the
least capable of all common consumer platforms).
In the end, it seems that we tested three methods, each of which has
different capabilities:
A. FTP server on the mobile device (works for all platforms)
B. SMB server on the desktop (works differently for all platforms)
C. KDE-Connect (works differently for all platforms)
Note:
On Android, I tested a plethora of *other* desktop/mobile connections:
<http://wetakepic.com/images/2017/10/20/android_connect.jpg>
Each of which works differently in some respects.
> I guess it can be a
> bit difficult to determine the ip-number if not permanently assigned to
> devices.
We have a long thread on that topic where it's not a problem in a practical
sense, since there are permanent solutions and the IP address is relatively
static in a typical household anyway.
The permanent solution is just to set up the router to give a static IP
address to each mobile device, where there are plenty of other solutions
that actually work even though they would seem to be sub optimal by way of
comparison.
For example, Android can *request* a certain IP address based on SSID,
which happens to work just fine in practice, even though clashes are
theoretically possible.
Likewise, doing nothing works just fine also, in a typical household with
the same devices going on and off the network, as the lease seems to be
good enough for all practical purposes.
Even if the FTP IP address did change, it's easily enough sniffed out on
Linux and on the router by MAC address, so, again, the IP address, in
practice, is the least of the issues.
0 new messages