So you can install and run nginx, redis, Atom.io, postgres etc. on this?
I'm in favour of this arrangement, since I think it's the only way to get updates to work reliably, and I think that's essential. Android and iOS also do it this way, for example. But don't expect a traditional Linux-based desktop but on a tablet, since that's not what you'll get.
On the other hand, if you package up nginx, redis, Atom.io, postgres etc. via Ubuntu's app store, then sure.
Isn't there a nice way to have it both ways, i.e. automate all changes in a script, and roll it after each image update? Assuming most things that may need to be hacked away don't see breaking changes after each update?
How is Maemo unreliable in that respect? I was disappointed to find Touch doesn't work like it does.
> But don't expect a traditional Linux-based desktop but on a tablet, since that's not what you'll get.
I thought the whole point was that you can switch. That's what Canonical says, and what's demonstrated in some videos floating around.
My understanding is that apps will indeed seamlessly switch between the two modes - but only where they have specifically been adapted to do so. Apps not adapted will not run. Or am I mistaken?
Then how is it Google can update my chromebook while I keep running ubuntu with 100% of linux features? I've done this for a year with no hiccup and no linux upgrades.
You could do this on an Ubuntu phone or tablet I suppose, by for example running a secondary "traditional" Ubuntu system inside a container in a read-write directory on the read-only system. I don't know if this will be possible from day one, but it's certainly possible technically if someone implements it (like how someone has implemented Crouton). I doubt you'll see the same level of integration (for example with the tablet UI seamlessly moving over to your desktop) if you do it this way, however.
Well, that's what I've been told - we'll see once they ship.
It would be nice to program in the park by just bringing the tablet and a keyboard. On the other hand the latency alone might distract me enough to just give up.
Plus imagine the cases where you don't have wifi (train commute, metro, lousy coffee shop etc.)
It's probably closed-source, but I use JuiceSSH and it is great. The Pro version has a cloud backup that makes SSH migration a breeze.
I've heard juicessh is great, but I'm not going to use a closed-source app, especially to manage my ssh-keys. I have my own migration method (svn repo), that works great on laptops, it just sucks on android's shells.
You may also need a busybox installer app to get things working.
I also want to be able to configure my tablet from within my shell, and that means I'd have to be outside of the chroot.