On Mon, 2009-11-23 at 18:19 +0100, Felix Zielcke wrote:
>
> This is due to a change inside the multiboot code.
> Previous versions and also GRUB Legacy passed the filename as first
> parameter to the multiboot image and to all modules.
> Now it doestn't do this any more.
This seems like a pretty major (and gratuitous) change in behaviour. Is
there anyway for an OS to determine whether the command line starts with
the image filename or not? If not then how are OS's expected to cope
with being booted by either Grub-legacy or Grub2?
> Unfortunately both behaviours conform to the multboot specification.
That may be so, but given that existing OSs (written to conform to the
old behaviour) expect things to be one way, what is the rationale for
changing it?
Ian.
--
Ian Campbell
Trust everybody, but cut the cards.
-- Finlay Peter Dunne, "Mr. Dooley's Philosophy"
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
