User: Password:
Subscribe / Log in / New account

Computer privacy

Computer privacy

Posted Jan 3, 2013 22:25 UTC (Thu) by shmerl (guest, #65921)
In reply to: Computer privacy by cjwatson
Parent article: Canonical to demonstrate Ubuntu on phones

Did you try Mer SDK and OBS?

(Log in to post comments)

Computer privacy

Posted Jan 4, 2013 0:01 UTC (Fri) by cjwatson (subscriber, #7322) [Link]

No. Life is too short.

Computer privacy

Posted Jan 4, 2013 15:49 UTC (Fri) by niner (subscriber, #26151) [Link]

Life is too short to try tools that save considerable time?

Computer privacy

Posted Jan 5, 2013 11:05 UTC (Sat) by cjwatson (subscriber, #7322) [Link]

As far as I can tell, the Mer SDK only builds for RPM-based systems. I'm unlikely ever to recoup the time spent in converting my phone from Maemo to Meego or one of its descendants.

Computer privacy

Posted Jan 4, 2013 0:02 UTC (Fri) by cjwatson (subscriber, #7322) [Link]

And incidentally I'm not interested in running (and especially not in developing) anything non-Debian-based.

Computer privacy

Posted Jan 4, 2013 1:22 UTC (Fri) by shmerl (guest, #65921) [Link]

Up to you of course. I personally use Debian on the desktop as well, and would prefer something Debian based for the mobile as well. However Debian as a project is rather slow to advance much in the mobile sphere. Mer on the other hand moves fast and is optimized for mobile, being well ahead of others, so I see nothing wrong with using it. Learning different tools like RPM vs DEB or some architectural differences and etc. isn't a scary or unworthy effort.

Computer privacy

Posted Jan 4, 2013 6:50 UTC (Fri) by pabs (subscriber, #43278) [Link]

It isn't particularly hard to put Debian on a random mobile device:

Unfortunately due to Linux mainline not supporting random mobile devices, Debian can't either. You can help get Debian on your mobile device by becoming a kernel developer and helping fix, rewrite and send upstream all the Android drivers from random kernel forks. Likewise for bootloaders. We could also use some help packaging the various mobile GUIs and applications:

Looks like Fedora and other distributions are discovering the kernel stuff too:

Computer privacy

Posted Jan 4, 2013 18:00 UTC (Fri) by shmerl (guest, #65921) [Link]

Yes, that's understandable, but that's exactly where Mer has an advantage. They explicitly separated the hardware adaptation bits from the rest of the system. I.e. hw adaptation is pluggable, and the rest of the core distribution stays the same (within the same arch like ARMv7, MIPS and etc.). Since putting all kind of wild mobile kernels differences in the mainline doesn't sound like a practically rapid approach, Mer just doesn't dictate it, and hw adaptations are up to the vendors to provide. It allows moving fast and be flexible with it.

Computer privacy

Posted Jan 9, 2013 16:31 UTC (Wed) by pabs (subscriber, #43278) [Link]

I never understood what Mer people were on about with that. Does "explicitly separated the hardware adaptation bits" mean that they just don't include kernels for most devices? If so that sounds exactly like what Debian is forced to do. If not, could you explain what you mean? Sounds like they will be facing the same kind of bugs in crappy, blobby, non-mainline kernels that I did with Debian or that CyanogenMod do. Trusting hardware vendors doesn't sound like a good plan in the slightest.

Computer privacy

Posted Jan 12, 2013 12:40 UTC (Sat) by juliank (subscriber, #45896) [Link]

They just package up the kernel and other libraries for each target separately, not much more. So basically each device has its own kernel + userspace libraries.

That's still better than Android though, where the complete system is built for a specific target and no sharing happens at all (not even userspace components).

Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds