From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] support/misc/Vagrantfile: bump to ubuntu 16.04
Date: Tue, 18 Oct 2016 14:10:39 +0200 [thread overview]
Message-ID: <CA+TH9V=YO9o5MPJ5PiTs+Lm-bOtrpcPD-fYMs0hyYzF54p5Ymw@mail.gmail.com> (raw)
In-Reply-To: <3fc3c742-0be1-d297-49af-8d442fc2b567@mind.be>
Dear Arnout,
2016-10-18 14:03 GMT+02:00 Arnout Vandecappelle <arnout@mind.be>:
>
>
> On 18-10-16 12:00, Angelo Compagnucci wrote:
> > Dear Thomas,
> >
> > 2016-10-18 11:46 GMT+02:00 Thomas Petazzoni <thomas.petazzoni@free-
> electrons.com
> > <mailto:thomas.petazzoni@free-electrons.com>>:
> >
> > Hello,
> >
> > On Mon, 17 Oct 2016 23:53:02 +0200, Angelo Compagnucci wrote:
> >
> > > + sudo apt-get purge -q -y snapd lxcfs lxd
> ubuntu-core-launcher snap-confine
> >
> > Why are you doing this step?
> >
> >
> > Ubuntu 16.04 introduced a number of services releated to the ops world
> and they
> > are not strictly releated to our use case. So I'm removing them to free
> some
> > space on disk and gain a bit of cpu cycles.
>
> I'm completely on board with doing that. Although it's really only snapd
> that
> takes space (25MB). There may even be more cruft that can be removed, but
> people
> can contribute if they want to :-).
>
> BTW, how are you going to gain CPU cycles this way?
>
They runs several background services (like snapd, lxcfs) that potentially
could use cpu to do thier unnecessary (for us) duties.
Sincerely, Angelo
>
> >
> >
> > Thanks,
> >
> > Thomas
> > --
> > Thomas Petazzoni, CTO, Free Electrons
> > Embedded Linux and Kernel engineering
> > http://free-electrons.com
> >
> >
> >
> >
> > --
> > Profile: http://it.linkedin.com/in/compagnucciangelo
> >
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> >
>
> --
> Arnout Vandecappelle arnout at mind be
> Senior Embedded Software Architect +32-16-286500
> Essensium/Mind http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
>
--
Profile: http://it.linkedin.com/in/compagnucciangelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20161018/9743b1d1/attachment.html>
next prev parent reply other threads:[~2016-10-18 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 21:53 [Buildroot] [PATCH v2] support/misc/Vagrantfile: bump to ubuntu 16.04 Angelo Compagnucci
2016-10-18 9:46 ` Thomas Petazzoni
2016-10-18 10:00 ` Angelo Compagnucci
2016-10-18 12:03 ` Arnout Vandecappelle
2016-10-18 12:10 ` Angelo Compagnucci [this message]
2016-10-18 11:58 ` Arnout Vandecappelle
2016-10-19 21:01 ` Thomas Petazzoni
2016-10-22 12:00 ` Peter Korsgaard
2016-10-25 8:04 ` Angelo Compagnucci
2016-10-25 8:45 ` Peter Korsgaard
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='CA+TH9V=YO9o5MPJ5PiTs+Lm-bOtrpcPD-fYMs0hyYzF54p5Ymw@mail.gmail.com' \
--to=angelo.compagnucci@gmail.com \
--cc=buildroot@busybox.net \
/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.