From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1CtbZh-0001kV-A4
	for qemu-devel@nongnu.org; Tue, 25 Jan 2005 20:02:26 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1CtbZa-0001h0-VY
	for qemu-devel@nongnu.org; Tue, 25 Jan 2005 20:02:19 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1CtbZa-0001dT-MQ
	for qemu-devel@nongnu.org; Tue, 25 Jan 2005 20:02:18 -0500
Received: from [38.113.3.71] (helo=smtp-out.hotpop.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1CtbED-00051L-9H
	for qemu-devel@nongnu.org; Tue, 25 Jan 2005 19:40:13 -0500
Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103])
	by smtp-out.hotpop.com (Postfix) with SMTP id 99CDB1359E61
	for <qemu-devel@nongnu.org>; Wed, 26 Jan 2005 00:39:29 +0000 (UTC)
Date: Tue, 25 Jan 2005 19:38:24 -0500
From: "Jim C. Brown" <jbrown106@phreaker.net>
Subject: Re: [Qemu-devel] Boot Sequence
Message-ID: <20050126003824.GA11510@jbrown.mylinuxbox.org>
References: <45768.64.244.234.131.1106690166.squirrel@64.244.234.131>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <45768.64.244.234.131.1106690166.squirrel@64.244.234.131>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: linuxtwidler@gmail.com, qemu-devel@nongnu.org

On Tue, Jan 25, 2005 at 03:56:06PM -0600, Lee wrote:
> 
> Hi All,
> 
> 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
> ...
> 
> 

What would be the point? It shouldn't be difficult to do, but I don't see how
it would be useful ... you'd still need to specify the boot device itself via
the command line as well. The only real use I can see is thru the monitor (I'm
thinking system_reset here).

> 
> -- 
> Lee
> linuxtwidler@gmail.com
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.