Re: [Xen-devel] [PATCH RESEND v1 2/8] tools: move scripts from etc to libexec

[Ian Jackson <ian.jackson@xxxxxxxxxx>]

Olaf Hering writes ("Re: [PATCH RESEND v1 2/8] tools: move scripts from etc to 
libexec"):
> Am Tue, 24 Sep 2019 15:17:43 +0100
> schrieb Ian Jackson <ian.jackson@xxxxxxxxxx>:
> > 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.

Editing files in /usr is not really a good idea.  They will be
overwritten by eg security updates.

> 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='.

As I say I have on occasion wanted to edit these to work around bugs
or do strange things.  I don't think taking a copy of the script and
editing that is a better idea than treating the script as a
configuration file.

> 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.

The scripts are not "tied to the tools version".  They are shipped
with the tools, sure, but we have maintained the interface.  There are
even out-of-tree scripts.  (I think iscsi has one, for example.)

They are in /etc for the same reason as boot scripts, dhclient hooks,
and so on, are in /etc.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel