From: Magnus Damm <magnus.damm@gmail.com>
To: linuxtwidler@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Boot Sequence
Date: Tue, 25 Jan 2005 23:24:30 +0100 [thread overview]
Message-ID: <aec7e5c3050125142426836b19@mail.gmail.com> (raw)
In-Reply-To: <45768.64.244.234.131.1106690166.squirrel@64.244.234.131>
Hello,
On Tue, 25 Jan 2005 15:56:06 -0600 (CST), Lee <linuxtwidler@gmail.com> wrote:
> Just wanted to through to the developers another great idea for qemu.
>
> it is the ability to list a boot-device sequence.
>
> I have in my mind something like this:
>
> -boot a,c,d
> -boot d,c
> ...
This is already present in the bochs bios, just have a look at version
1.121 of rombios.c and start hacking...
http://cvs.sourceforge.net/viewcvs.py/bochs/bochs/bios/#dirlist
/ magnus
next prev parent reply other threads:[~2005-01-25 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 21:56 [Qemu-devel] Boot Sequence Lee
2005-01-25 22:24 ` Magnus Damm [this message]
2005-01-26 0:38 ` Jim C. Brown
2005-01-26 0:55 ` Mike Swanson
2005-01-26 1:34 ` Jim C. Brown
2005-01-26 10:13 ` Magnus Damm
2005-01-26 1:03 ` Johannes Schindelin
2005-01-26 6:17 ` Lee
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=aec7e5c3050125142426836b19@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=linuxtwidler@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).