From: "Adrian Bunk" <bunk@stusta.de>
To: csimmonds <chris@2net.co.uk>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] Distro upgrade strategies
Date: Sun, 21 Jun 2020 10:11:50 +0300 [thread overview]
Message-ID: <20200621071150.GC6921@localhost> (raw)
In-Reply-To: <4f66cf05-c142-188c-0661-8e446c81c67f@2net.co.uk>
On Fri, Jun 19, 2020 at 03:35:33PM +0100, csimmonds wrote:
> I would like to add that this is a design decision. Package updates, be
> they based on rpm, deb, or ipk, are not atomic. Which means that if you
> power off during an update the system will usually not boot afterwards.
This is not true, package manager like dpkg are trying very very hard to
make things atomic where they have to be and allow recovery from any
kind of interruption.
I do not recall anyone ever describing such a problem with Debian
(or Ubuntu) in over 20 years as Debian user/administrator/developer.
>...
> OpenEmbedded/Yocto
> Project expect the update will be done by programming a new root
> filesystem image.
>...
Note that what you write would imply that package management must not
ever be used on OpenEmbedded/Yocto devices.
If there is any potential problem, it would equally apply to the
situation where you are upgrading just one package for a security
update.
> HTH,
> Chris
cu
Adrian
next prev parent reply other threads:[~2020-06-21 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 12:16 Distro upgrade strategies hboddington
2020-06-19 14:05 ` [yocto] " Alexander Kanavin
2020-06-19 14:35 ` csimmonds
2020-06-19 14:38 ` Alexander Kanavin
2020-06-21 7:11 ` Adrian Bunk [this message]
2020-06-21 12:09 ` Stefano Babic
2020-06-21 13:46 ` Adrian Bunk
2020-06-21 14:04 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200621071150.GC6921@localhost \
--to=bunk@stusta.de \
--cc=chris@2net.co.uk \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.