From: Pascal de Bruijn <p.debruijn@unilogic.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/linux-tools: add support for Hyper-V tools
Date: Fri, 6 Dec 2019 15:20:59 +0100 [thread overview]
Message-ID: <3683881315-31837@mail.unilogic.nl> (raw)
In-Reply-To: <20191206151712.4a3ea674@windsurf>
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Simon Rowe <simon.rowe@eu.citrix.com>
Cc: Simon Rowe <simon.rowe@citrix.com>, <buildroot@buildroot.org>, Yann E. MORIN <yann.morin.1998@free.fr>, Pascal de Bruijn <p.debruijn@unilogic.nl>
Sent: 12/6/2019 3:17 PM
Subject: Re: [Buildroot] [PATCH 1/1] package/linux-tools: add support for Hyper-V tools
Hello,
+Pascal in Cc.
On Fri, 6 Dec 2019 13:33:50 +0000
Simon Rowe <simon.rowe@eu.citrix.com> wrote:
> What's the probability of that, someone else just sent a patch 15
> minutes ago while I was testing this one,
Pascal: the approach of Simon is to have a single option to
build/install all tools. Do we really need one option per tool like you
implemented? In which use cases would only a subset of the tools be
needed? What is the installed size of each tool?
The size of each tool is very limited, so that's at best a secondary concern.
But for example the fcopy service basically gives the virtualization host provider direct access to the guest filesystem., which is not something everybody may want to actively facilitate.
Having these different services nicely separated out, is specifically one of the nice things opposed to VMware's openvmtools/vmtoolsd.
Regards,
Pascal de Bruijn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191206/6d69a562/attachment.html>
prev parent reply other threads:[~2019-12-06 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 13:31 [Buildroot] [PATCH 1/1] package/linux-tools: add support for Hyper-V tools Simon Rowe
2019-12-06 13:33 ` Simon Rowe
2019-12-06 14:17 ` Thomas Petazzoni
2019-12-06 14:20 ` Pascal de Bruijn [this message]
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=3683881315-31837@mail.unilogic.nl \
--to=p.debruijn@unilogic.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox