Avoiding fragmentation with a rolling release

[Mario Limonciello]

On Thu, Feb 28, 2013 at 6:07 PM, Loïc Minier <loic.minier at ubuntu.com> wrote:

> On Thu, Feb 28, 2013, Mario Limonciello wrote:
> > What about a rolling static base instead?  Do a unionfs (or similar) on
> top
> > of it.  Deliver an encompassing image from month to month.  Turn off apt
> as
> > a mechanism to deliver updates.  But allow it to be turned back on.  Even
> > if you don't install anything on top of it, then every month a new static
> > base comes up and updates it.  If you decide to do daily updates on top,
> > some of them might be in next month's new static base already, so that
> > would need to be handled gracefully.
> >
> > Similar approaches are applied to Chrome OS and Android successfully.
>
> I'm not sure how you'd deliver security updates between monthlies
> though?
>
>
The way I was seeing it, you turn off APT updates from the regular archive,
but leave them in place for the security archive.  In between monthlies you
fetch security updates from that archive.  When the next monthly comes
around as part of applying that update, you remove the deltas that were put
in place from the interim security updates.


>
> However these ideas would definitely make sense for e.g. deploying a
> firmware upgrade on a phone or tablet!  On this topic, I would think we
> would want to revisit how we manage various types of data: how does one
> "reset to factory settings"?  How would one deploy an update from a
> local file or OTA?
>
> Plus we'd want these updates to be as small as possible; typically
> deltas.  Would be a good win over downloading hundreds of megs of .debs
> from one version to the next.
>
> --
> Loïc Minier
>



-- 
Mario Limonciello
superm1 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20130228/952a094f/attachment.html>