From: "Alexander A. Filippov" <a.filippov@yadro.com>
To: Adriana Kobylak <anoo@linux.ibm.com>
Cc: "Alexander A. Filippov" <a.filippov@yadro.com>,
<openbmc@lists.ozlabs.org>,
openbmc <openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org>
Subject: Re: Packaging and deploying multiple firmware image types in one
Date: Thu, 14 Nov 2019 10:51:31 +0300 [thread overview]
Message-ID: <20191114075131.GA6696@bbwork.lan> (raw)
In-Reply-To: <9ddc3deca00904404c72a49c4f89c8a4@linux.vnet.ibm.com>
On Tue, Nov 12, 2019 at 04:54:22PM -0600, Adriana Kobylak wrote:
>
> Yeah, the purpose is not currently preserved across reboots. I have a change
> here for that:
> https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-bmc-code-mgmt/+/27045
>
On Thu, Nov 14, 2019 at 03:14:41AM +0000, Adriana Kobylak (Code Review) wrote:
> ...
> but let's continue on the mailing list about your thoughts on how you think
> the tarball of tarballs should be handled.
>
Ok, here are my thoughts:
The phosphor-version-software-manager might put all internal tarballs in the
/tmp/images folder during processing the top level tarball. That will lead to
creation of corresponding D-Bus objects. Each of them will have their own
purpose, version, object path and so on.
The root D-Bus object and their folder might be removed after that to reduce a
used file system space.
next prev parent reply other threads:[~2019-11-14 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 19:28 Packaging and deploying multiple firmware image types in one Adriana Kobylak
2019-11-12 7:49 ` Alexander A. Filippov
2019-11-12 21:38 ` Gunnar Mills
2019-11-13 0:54 ` Adriana Kobylak
2019-11-12 22:54 ` Adriana Kobylak
2019-11-13 7:24 ` Alexander A. Filippov
2019-11-14 7:51 ` Alexander A. Filippov [this message]
2019-11-14 22:10 ` Adriana Kobylak
2019-11-15 14:51 ` Adriana Kobylak
2019-11-15 15:46 ` Andrew Geissler
2019-11-19 19:22 ` Adriana Kobylak
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=20191114075131.GA6696@bbwork.lan \
--to=a.filippov@yadro.com \
--cc=anoo@linux.ibm.com \
--cc=openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org \
--cc=openbmc@lists.ozlabs.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.