I concur with Amos' sentiment. Certainly our group has to handle a
number of different systems that we have to use, each potentially being
differently configured (i.e. some may have root=/dev/hda3 in FW, some
may not). If you're in a cluster scenario where you're network booting
there's a lot of value to having as much boot behavior as possible
defined inside the boot image itself.
--
Michal Ostrowski <mostrows@xxxxxxxxxxxxxx>
On Tue, 2006-09-19 at 14:25 -0400, Amos Waterland wrote:
> On Mon, Sep 18, 2006 at 09:51:05AM -0500, Hollis Blanchard wrote:
> > I'm happy to accommodate netbooting large clusters, but I'm asking you
> > to simplify this situation, not make it more complex.
>
> In order to scale to large clusters, one must have flexible and
> policy-free software. Right now Xen has a certain policy hard-coded
> in it: namely, that the firmware-supplied bootargs always take
> precedence over the builtin bootargs with no option to change. This
> patch is three lines of code, makes Xen more flexible, removes a
> hard-coded policy, and solves a real-world problem. Seen in that light,
> I hope you will reconsider your objection.
>
>
> _______________________________________________
> Xen-ppc-devel mailing list
> Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ppc-devel
>
_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel
|
Home