I just don’t want to recommend generally to people to work at the bare-metal level. I also think there’s an issue of having a graphical front end and being able to use reliable third-party software that’s automated. We have some number of readers for whom it wouldn’t be a big deal, but it’s the kind of thing that could spiral out of control to provide the documentation for, and it’s really more of a Unix-style solution.īack To My Mac (not Find My Mac, which is opaque to users) has a lot of tunneling and reliability issues that I believe have led people in the past trying to build remote-connection and other services that determined this address to halt development on those products! I remember some AppleTalk bridges, for instance! No offense to any TidBITS reader, but that’s really beyond the scope of the publication.
Since we’re talking about “rolling your own”, what about really doing it by hand? I would assume FindMyMac must allow doing this some way or another…
Any easy way to exploit FindMyMac so that you could use some kind of generic hostname that would automatically get forwarded to the current IP of your remote Mac? Something like the_name_I_gave_my_Mac.some_generic_Apple_Īnd assuming that’s not possible, what about exploiting FindMyMac to at least get the current IP of that remote Mac? There used to to be the free OpenDNS with its DNS forwarding daemon, but of course that went all commercial so there’s no more free option there. If we assume this box has a fixed IP it’s easy. Is there anything special you’d need to consider if you’d decide to just use rsync to do your own “networked version” of TimeMachine? Since we’re talking about “rolling your own”, what about really doing it by hand? What about a situation where you have off-site ssh access to some box with lots of storage and halfway decent bandwaidth.
0 kommentar(er)
