From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <ian.jackson@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Wei Liu <wl@xen.org>
Subject: Re: [Xen-devel] [PATCH RESEND v1 2/8] tools: move scripts from etc to libexec
Date: Tue, 24 Sep 2019 17:19:10 +0200 [thread overview]
Message-ID: <20190924171910.5ff75b9a.olaf@aepfle.de> (raw)
In-Reply-To: <23946.9607.887344.235099@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1056 bytes --]
Am Tue, 24 Sep 2019 15:17:43 +0100
schrieb Ian Jackson <ian.jackson@citrix.com>:
> I think the ability of the admin to edit these scripts is important and I have used it myself in the past.
Since they are scripts, they can be edited in any location. To me it is not clear what the case would be to diverge from the vendor provided variant.
IMO these are part of the Xen tools, there is nothing to configure in these scripts. If for whatever reason the local admin must run his own variant, at least for disk= and vif= the location can be changed with 'script='.
I'm sure they are in /etc because in the early days of Xen there was a hope the local admin would do all the work to connect backends and frontends in a way he likes. I think this is not true since more than a decade, the scripts are always tied to the tools version. The API is now mature since a while, there are very few changes in the past years.
A configure knob could be added to set XEN_SCRIPT_DIR at build time, if there is really a usecase for such knob.
Olaf
[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-09-24 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 14:03 [Xen-devel] [RESEND v1 0/8] tools, doc and stubdom fixes Olaf Hering
2019-09-24 14:03 ` [Xen-devel] [PATCH RESEND v1 1/8] stubdom/vtpm: include stdio.h for declaration of printf Olaf Hering
2019-09-27 21:27 ` Daniel De Graaf
2019-09-24 14:03 ` [Xen-devel] [PATCH RESEND v1 2/8] tools: move scripts from etc to libexec Olaf Hering
2019-09-24 14:09 ` Ian Jackson
2019-09-24 14:15 ` Olaf Hering
2019-09-24 14:17 ` Ian Jackson
2019-09-24 15:19 ` Olaf Hering [this message]
2019-09-30 16:49 ` Ian Jackson
2019-09-30 16:43 ` Olaf Hering
2019-09-24 14:03 ` [Xen-devel] [PATCH RESEND v1 3/8] Use XEN_SCRIPT_DIR to refer to /etc/xen/scripts Olaf Hering
2019-09-24 14:03 ` [Xen-devel] [PATCH RESEND v1 4/8] Remove tools/examples/README.incompatibilities Olaf Hering
2019-09-24 14:03 ` [Xen-devel] [PATCH RESEND v1 5/8] tools: remove empty xl.conf Olaf Hering
2019-09-24 14:03 ` [Xen-devel] [PATCH RESEND v1 6/8] Remove tools/examples/cpupool Olaf Hering
2019-09-24 14:03 ` [Xen-devel] [PATCH RESEND v1 7/8] docs: substitute XEN_CONFIG_DIR in xl.conf.5 Olaf Hering
2019-09-24 14:03 ` [Xen-devel] [PATCH v1 8/8] docs: remove stale create example from xl.1 Olaf Hering
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=20190924171910.5ff75b9a.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=ian.jackson@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.