All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Geissler <geissonator@gmail.com>
To: Ed Tanous <ed@tanous.net>
Cc: Brad Bishop <bradleyb@fuzziesquirrel.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: interest in a minimal image recipe
Date: Mon, 21 Sep 2020 08:21:41 -0500	[thread overview]
Message-ID: <2EADC669-1B01-4D19-8231-77A02C5E74D4@gmail.com> (raw)
In-Reply-To: <CACWQX82_GWxDeiX_7P2A6mYBYp0OWUkfQLEsOhHeCgU676s7Zw@mail.gmail.com>



> On Sep 17, 2020, at 4:02 PM, Ed Tanous <ed@tanous.net> wrote:
> 
> On Thu, Sep 17, 2020 at 1:12 PM Brad Bishop <bradleyb@fuzziesquirrel.com> wrote:
>> 
>> On Tue, Sep 15, 2020 at 04:28:32PM -0400, Brad Bishop wrote:
>>> I have an RFC for an empty image that these users could bbappend and
>>> opt-in to specific image features instead of having to repeatedly
>>> opt-out.
>> 
>> If anyone is curious how I envisioned this would be used I am intending
>> to use it on witherspoon (we are out of space):
>> 
>> https://gerrit.openbmc-project.xyz/36588
> 
> Out of curiosity, has anyone run a space analysis on a recent
> witherspoon image?  It would be interesting to know where the space is
> going, so we can start hammering those subsystems back into shape.
> 
> This is the script I used a while back to come up with relative,
> compressed sizes for all the components in the rootfs.
> https://github.com/openbmc/openbmc-tools/blob/master/edtanous/rootfs_size.py

I added it to our daily build job.

https://jenkins.openbmc.org/job/latest-master/label=docker-builder,target=witherspoon/lastSuccessfulBuild/artifact/openbmc/build/tmp/deploy/images/results.txt

  reply	other threads:[~2020-09-21 13:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 20:28 interest in a minimal image recipe Brad Bishop
2020-09-15 20:58 ` Khetan, Sharad
2020-09-15 21:27   ` Sriram Ramkrishna
2020-09-17 20:10 ` Brad Bishop
2020-09-17 21:02   ` Ed Tanous
2020-09-21 13:21     ` Andrew Geissler [this message]
2020-09-17 20:56 ` Ed Tanous
2020-09-17 22:21   ` Khetan, Sharad
2020-09-21 15:05     ` Ed Tanous
2020-09-21 15:05       ` Ed Tanous
2020-09-22  2:03       ` Khetan, Sharad
2020-09-22  2:03         ` Khetan, Sharad
2020-09-22 16:54         ` Nancy Yuen
2020-09-21 12:55   ` Brad Bishop
2020-09-21 15:53     ` Ed Tanous
2020-09-21 17:52       ` Brad Bishop
2020-09-21 18:25         ` Ed Tanous
2020-09-21 19:08           ` Brad Bishop
2020-09-22 20:40         ` Vijay Khemka
2020-09-23 19:46           ` Ed Tanous
2020-09-23 19:49             ` Vijay Khemka
2020-09-21 18:20       ` Brad Bishop
2020-09-21 18:49         ` Ed Tanous
2020-09-21 19:01           ` Brad Bishop
2020-09-22 19:52       ` Vijay Khemka
2020-09-23 17:50 ` Brad Bishop

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=2EADC669-1B01-4D19-8231-77A02C5E74D4@gmail.com \
    --to=geissonator@gmail.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=ed@tanous.net \
    --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.