Re: [PATCH 0/8] Suspend block api (version 8)

Igor Stoppa
2010-05-28T13:30:03Z

ext Theodore Tso wrote:

>
>
> Well, yes, if the company strategy is to have a walled garden ala the Apple iPhone App store, life is much simpler.

No, the strategy is to try to merge commercial and community needs.

We do support signed repositories.

The community has control on the public one.

Members are encouraged to help by alpha/beta testing apps that are under
development.
They even organize testing marathons.

> But if the requirements mean that apps don't need preapproval, the requirements on the platform get harder.

That's a wrong way to put it. By installing something on your phone you
_do_ approve it.

> I think the take-home here is we have a requirement that the platform behave well even without someone screening the applications for the "default SW repository".

What it meant is totally different. Regardless how much effort you put
into twisting it.
It means that different repositories provide different level of trust.

As Debian user, I don't blame anybody other than myself is something
I've pulled from unstable or experimental breaks my system.
Debian by default doesn't ship with either unstable or experimental enabled.

And using suspend blockers doesn't really solve the problem of who to
trust to take the block and who not.

Or we'll have to have suspend-blockers-blockers and so on ...

Like it or not, QoS and resource management - in some form - are needed
to allow trusted application to provide valuable feedback, while
filtering requests from untrusted applications.

You might want to add dynamic profiling and try to use some heuristic to
have the system doing runtime evaluation of good vs bad applications,
but still some discrimination mechanism will be required.

igor