From: Olaf Hering <olaf@aepfle.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Vasilis Liaskovitis <vliaskovitis@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v1] tools/hotplug: convert proc-xen.mount to proc-xen.service
Date: Thu, 26 Oct 2017 17:59:40 +0200 [thread overview]
Message-ID: <20171026155940.GG4555@aepfle.de> (raw)
In-Reply-To: <cde0e85d-2d1b-d0f8-fee4-b7f2efeb4090@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 590 bytes --]
On Thu, Oct 26, Andrew Cooper wrote:
> Can't all information be obtained from /sys/hypervisor? If not, how
> hard would it be to make happen?
Likely not that hard. Not sure why that was not added in the first place.
> What happens to all the software which currently has a dependency on
> proc-xen.mount ?
All software gets converted by this change.
> Independently, how does this interact with having a xenfs entries in
> /etc/fstab, which might plausibly still exist for compatibility with
> other init systems?
mount(1) will continue to consider them.
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-26 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 15:25 [PATCH v1] tools/hotplug: convert proc-xen.mount to proc-xen.service Olaf Hering
2017-10-26 15:45 ` Andrew Cooper
2017-10-26 15:59 ` Olaf Hering [this message]
2017-10-26 16:14 ` Andrew Cooper
2017-10-26 17:05 ` Olaf Hering
2017-11-08 16:24 ` Olaf Hering
2017-11-08 17:28 ` Wei Liu
2017-11-08 17:38 ` Olaf Hering
2017-11-09 10:48 ` Ian Jackson
2017-10-30 10:08 ` Wei Liu
2017-10-27 13:58 ` Wei Liu
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=20171026155940.GG4555@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=vliaskovitis@suse.com \
--cc=wei.liu2@citrix.com \
--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.