Re: Multiple kernel boot in linuxboot.cfg
Timothy Fontaine <[email protected]>
| Newsgroups | gmane.linux.ports.xbox.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 23 Sep 2004 21:22:22 +0100, David Pye <[email protected]> wrote: > Well, after discussing this one with ShALLaX, (mr Gentoox) and a few other > #xbox-linux denizens, (I haven't managed to grab Mr Xebian yet), here's > another idea. > > Adopt grub's syntax a bit more closely, and have a new config file for the new > cromwell parser e.g. linux.cfg or whatever. > > If it exists, new cromwell will parse it. If it DOESNT exist, the existing > parser code will seek out linuxboot.cfg and parse it as presently. > > That way, distributors can ship both linuxboot.cfg and linux.cfg (name subject > to discussion!), thus allowing new and old cromwells to work (and new > cromwells to take advantage of multiple boot options). This also keeps > xbeboot in the game, until someone steps up to change its parser to support > the new format. > > Eventually, one hopes, when the old cromwells are phased out, we can remove > the linuxboot.cfg, and the old parser code, MAYBE. > > Opinions? :) > > David I think by far this will save everyone lots of hassle. There is already a large portion of grub code present in cromwell so it just "makes sense" that the parser and file format should match. The benefits of this: 1) The file format is straight forward 2) There is plenty of material already google'able 3) You can always just say man grub/ man menu.lst if they need info on adding kernels et al 4) Some kernel packages available from distributions directly modify the menu.lst to add new kernels (especially nice if distros start to ship xbox compatible kernels) The Cons: 1) Someone has to port it and the initial difference may not be as straightforward as desired 2) You may have to keep another tree in sync with grub in case of changes So the question becomes a larger one: What is the future of xbox-linux? If the goal is merely to morph into a state that vendors find you easy to mold into their respective distributions, then I would certainly choose grub. If the goal is to be simple for everyone to code and maintain a firmware replacement then create a new file format and parser. tjfontaine ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php