From: Olaf Hering <olaf@aepfle.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xen.org, M A Young <m.a.young@durham.ac.uk>
Subject: Re: [PATCH 0/4 v2] tools/hotplug: systemd changes for 4.5
Date: Thu, 11 Dec 2014 20:20:59 +0100 [thread overview]
Message-ID: <20141211192058.GA5709@aepfle.de> (raw)
In-Reply-To: <20141211191527.GB18992@laptop.dumpdata.com>
On Thu, Dec 11, Konrad Rzeszutek Wilk wrote:
> I wonder if we can detect the context during build-time (an autoconf function
> that checks whether the build is done for Fedora?)
> But what if the version of Fedora is different and the object is called
> something else?
Exactly. The build host is not the host where the code runs. It just
happens to be the same in your case.
This and the fact that xenstored cant (appearently) be launched via a
wrapper script makes we wonder how to deal with SELinux...
Olaf
next prev parent reply other threads:[~2014-12-11 19:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 10:18 [PATCH 0/4 v2] tools/hotplug: systemd changes for 4.5 Olaf Hering
2014-12-08 10:18 ` [PATCH 1/4] tools/hotplug: remove SELinux options from var-lib-xenstored.mount Olaf Hering
2014-12-08 10:18 ` [PATCH 2/4] tools/hotplug: remove XENSTORED_ROOTDIR from service file Olaf Hering
2014-12-08 10:18 ` [PATCH 3/4] tools/hotplug: remove EnvironmentFile from xen-qemu-dom0-disk-backend.service Olaf Hering
2014-12-08 10:18 ` [PATCH 4/4] tools/hotplug: use xencommons as EnvironmentFile Olaf Hering
2014-12-10 20:42 ` [PATCH 0/4 v2] tools/hotplug: systemd changes for 4.5 Konrad Rzeszutek Wilk
2014-12-11 8:43 ` Olaf Hering
2014-12-11 12:00 ` M A Young
2014-12-11 12:04 ` Olaf Hering
2014-12-11 12:05 ` Olaf Hering
2014-12-11 12:29 ` M A Young
2014-12-11 19:15 ` Konrad Rzeszutek Wilk
2014-12-11 19:20 ` Olaf Hering [this message]
2014-12-12 0:21 ` Konrad Rzeszutek Wilk
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=20141211192058.GA5709@aepfle.de \
--to=olaf@aepfle.de \
--cc=konrad.wilk@oracle.com \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xen.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.