1 |
> |
2 |
> |
3 |
> If you build/install Android on a device, then it only contains what |
4 |
> you put there, and you can just as easily remove it. If you let |
5 |
> somebody else build/install android on a device and not give you root |
6 |
> access, then it is painful. |
7 |
> |
8 |
> If you build/install Gentoo on a device, then it only contains what |
9 |
> you put there, and you can just as easily remove it. If you let me |
10 |
> build/install Gentoo on your device and not give you root access, then |
11 |
> it is painful. |
12 |
> |
13 |
> If you let me reflash the firmware on your Gentoo system so that it |
14 |
> uses my UEFI keys and firmware update keys and doesn't let you change |
15 |
> them, and I set it up with a bootloader that checks your |
16 |
> kernel+initramfs signatures and decrypts the rest of your hard drive |
17 |
> using a TPM-supplied key and a verified boot path, and an initramfs |
18 |
> that checks the signature on your /usr and mounts everything else |
19 |
> noexec, then you're going to have some serious headaches. And yes, |
20 |
> you actually can do all of this with Gentoo, though almost nobody |
21 |
> bothers (ChromeOS is based on Gentoo and does use a variation on this, |
22 |
> with licensed devices having a switch to disable the signature |
23 |
> checks). I'd have to check but I think Linux actually supports (maybe |
24 |
> via a patch) signature verification on execing images, in which case I |
25 |
> can let you mount whatever you want +x and you still won't be able to |
26 |
> run your own stuff. |
27 |
> |
28 |
> Your problem isn't with Android the OS. Your problem is with the |
29 |
> experience your phone vendor is giving you. All that lockdown stuff |
30 |
> that you seem to hate is 100% supported by the Linux kernel - you're |
31 |
> just not turning it on with a typical distro install. |
32 |
> |
33 |
> > |
34 |
> >> FOSS developers seem to mostly be stuck in X11-land - it scratches |
35 |
> >> their itch which tends to be on the desktop. While touch screen is |
36 |
> >> "just another input device" the fact is that you need to design your |
37 |
> >> entire application UI around it. ... |
38 |
> > |
39 |
> > why do you thinks some foss user interfaces can not be created for this |
40 |
> > situation? |
41 |
> > |
42 |
> |
43 |
> I'm not saying that they cannot be created. I'm simply pointing out |
44 |
> that nobody is bothering to do so. Anybody can write a web-based MUA |
45 |
> comparable to Gmail or a web-based replacement to Google Docs, and |
46 |
> release it as FOSS. However, it takes a lot of work and for various |
47 |
> reasons most seem content to use an X11-based version of each. In the |
48 |
> case of LibreOffice I think the origins are actually in software that |
49 |
> was intended to be sold commercially, but failed (which is probably |
50 |
> why they've been trying to cleanup the code for years). |
51 |
> |
52 |
> For a mobile OS your life is made even more difficult by Android, |
53 |
> since many who would tend to write a competing OS probably consider it |
54 |
> good enough. |
55 |
> |
56 |
> I'm really not interested in yet another android so much as more open |
57 |
> hardware to run android on. Vendors are getting better about allowing |
58 |
> unlocking, but driver support/etc is still a mess. |
59 |
> |
60 |
> Oh, and I don't like the general move of APIs into Google Play |
61 |
> Services. That really needs to be split into two applications. One |
62 |
> would provide APIs for stuff actually related to Google (like Google |
63 |
> authentication, buying stuff on the Play Store, Google Wallet, and so |
64 |
> on), and that could be closed. The other would provide all the stuff |
65 |
> like WebView APIs where rapid updates are desirable, and it should be |
66 |
> FOSS. |
67 |
> |
68 |
> |
69 |
|
70 |
I know what you mean. This is all more or less true, but what can we do in |
71 |
this situation? |
72 |
I will try to move toward whatever promotes openness, and please do not |
73 |
tell me that ubuntu |
74 |
is not more open that android. In android I cant even have pure native |
75 |
apps! some parts of an application |
76 |
should always be in java. |