From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Todd Deshane <todd.deshane@xen.org>, xen-devel@lists.xensource.com
Subject: RE: xen-unstable on OL6 (RHEL6 clone) problems
Date: Thu, 10 Feb 2011 10:07:32 -0800 (PST) [thread overview]
Message-ID: <4ea38fee-43ad-4e43-968b-a4d0de080628@default> (raw)
In-Reply-To: <1297326630.28185.1178.camel@zakaz.uk.xensource.com>
> > I have to ask... this is progress?
>
> Yes. We consider integrating with the distro's standard configuration
> mechanisms/utilities/tools in a way which is consistent with each
> distro's own documentation, instead of Xen rolling its own and blowing
> away any network configuration the system administrator has performed,
> to be progress.
Hi Ian --
While I agree with your good intentions, I think what happened is
that you broke something that was working fine for some subset of
users/developers (RH/Fedora0-based) in order to unbreak something
for another subset (Debian-based).
In the Xen upstream development community, that may be a fine
tradeoff because of the high sysadmin knowledge and the high
percentage of developers using a "bleeding edge" distro.
I suspect that it will be much more of a problem for a released
Xen where a much higher percentage of people installing Xen
are less savvy and prefer stable distros.
> > <flame on>
> > Um, never mind, waste of breath
> > <flame off>
>
> If you have constructive comments to make, as opposed to vague
> allusions
> to not liking some change or other and snide comments, we would be
> happy
> to hear them.
My comment (and even if you consider it snide or non-constructive,
I'd appreciate it if you would seriously consider it):
I think we need to make every effort to make Xen as drop-dead
easy to install and use as possible for as many developers and
users as possible, NOT a series of test questions on the
renew-my-alpha-geek-merit-badge exam.
Thanks,
Dan
next prev parent reply other threads:[~2011-02-10 18:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 22:26 xen-unstable on OL6 (RHEL6 clone) problems Dan Magenheimer
2011-02-09 23:13 ` Todd Deshane
2011-02-09 23:49 ` Dan Magenheimer
2011-02-10 0:22 ` Dan Magenheimer
2011-02-10 1:38 ` Todd Deshane
2011-02-10 1:54 ` Fajar A. Nugraha
2011-02-10 2:15 ` Todd Deshane
2011-02-10 2:38 ` Dan Magenheimer
2011-02-10 3:18 ` Todd Deshane
2011-02-10 8:29 ` Ian Campbell
2011-02-10 12:53 ` Ian Jackson
2011-02-10 17:48 ` Dan Magenheimer
2011-02-10 17:56 ` Stefano Stabellini
2011-02-11 3:09 ` Todd Deshane
2011-02-11 7:49 ` Ian Campbell
2011-02-11 11:44 ` Stefano Stabellini
2011-02-11 11:57 ` Ian Campbell
2011-02-11 12:08 ` Stefano Stabellini
2011-02-11 17:30 ` Dan Magenheimer
2011-02-11 17:50 ` Todd Deshane
2011-02-12 16:03 ` John Haxby
2011-02-11 16:53 ` John Haxby
2011-02-11 19:17 ` Pasi Kärkkäinen
2011-02-11 11:42 ` Stefano Stabellini
2011-02-10 8:32 ` Ian Campbell
2011-02-10 15:19 ` Todd Deshane
2011-02-10 8:30 ` Ian Campbell
2011-02-10 18:07 ` Dan Magenheimer [this message]
2011-02-10 19:25 ` Ian Jackson
2011-02-10 19:45 ` Dan Magenheimer
2011-02-11 15:30 ` George Dunlap
2011-02-11 7:48 ` Ian Campbell
2011-02-10 7:18 ` Pasi Kärkkäinen
2011-02-10 17:55 ` Dan Magenheimer
2011-02-10 18:00 ` Pasi Kärkkäinen
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=4ea38fee-43ad-4e43-968b-a4d0de080628@default \
--to=dan.magenheimer@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=todd.deshane@xen.org \
--cc=xen-devel@lists.xensource.com \
/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.