WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] add a way to disable xen's udev script.

On Thu, 2011-06-09 at 11:07 +0100, Vincent Hanquez wrote:
> On 06/09/2011 10:23 AM, Ian Campbell wrote:
> > Feel free to suggest patches which implement any better scheme you have.
> >    
> 
> I did already.
> 
> My solution involves going to step 2 directly, keeping a simple way for 
> compat toolstacks to still work dynamically in parallel with new more 
> modern toolstack that doesn't use those udev script.

No it does not go straight to any (completely undefined) step 2 and it
in no way allows toolstacks to dynamically work in parallel -- it allows
your current pet project to unilaterally disable functionality in other
existing toolstacks because that is convenient to you, without any
consideration for the bigger picture or actual _real_ interop with other
toolstacks or usecases.

Furthermore I object to your characterisation of some toolstacks as
"compat" and the one you are currently interested in as "new"/"modern".
xl uses these udev scripts and is in no way a "compat" toolstack. You
cannot simply deny the existence of other toolstacks, ignore their
requirements and justify breaking their functionality by branding them
legacy.

Please step back and see that there is a bigger picture and other
considerations than whatever you are currently working on and the
quickest most expedient way to solve your issue at the expense of
everything else.

>  And eventually 
> reach step 3 that will remove the udev scripts altogether (which render 
> fancy tweaks in those udev scripts (step 1) absolutely moot)

So what is your proposal for removing the need for udev (i.e. what is
the so-called "step 3")? Unless you have specific concrete suggestions
then we cannot build consensus around any move away from the udev
scripts and all this talk is just hot air.

And, to be frank, unless you have an plan to back it up with patches
sooner rather than later (eventually is a long time) we are most likely
going to be using the udev script for the foreseeable future, since you
seem to be the only one who feels strongly about it. (I don't know
perhaps your suggested approach will be so compelling that it will spur
someone else to implement it, fingers crossed).

Unless there is active movement towards "step 3" (whatever that is)
fixing the udev scripts to allow interop between toolstacks with other
udev scripts (or none at all) is hardly moot.

> Unfortunately you really want to go to step 1, before step 2 which 
> involves doing lots of unnecessary work. I don't have any interest in 
> that as stated above.

You aren't obliged to do any more work than you want. However it does
not follow that we must take your original patch.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel