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.
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.