Date: Mon, 10 Dec 2012 19:04:11 +0100 (CET) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Aryeh Friedman <aryeh.friedman@gmail.com> Cc: FreeBSD Mailing List <freebsd-hackers@freebsd.org> Subject: Re: using FreeBSD to create a completely new OS Message-ID: <alpine.BSF.2.00.1212101904100.13453@wojtek.tensor.gdynia.pl> In-Reply-To: <CAGBxaX=y9yLBymKX8Psmer0sPFWCgAFy3gs%2BtgU7waQt2g6hKA@mail.gmail.com> References: <CAGBxaX=y9yLBymKX8Psmer0sPFWCgAFy3gs%2BtgU7waQt2g6hKA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> suitable starting place)... what I mean is I want to start with the > MBR (boot0) and go on from there... I only have one *REAL* machine to > work with which means I need to work with something like > emulators/virtualbox-ose... I also want to do as many automated tests > as possible (for example seeing if the installer copied the MBR [and > later other stuff] correctly to the virtual HDD).... for this reason I > have a few questions on vb (or perhaps QEMU if not possible in vb): > > 1. Can it be scripted? for such usage i would recommend qemu. Virtualbox is for production use with common OSes, and is very ineffective in batch usage and inflexible, but fast. qemu is slow but you can have anything. including precise definition of your virtual hardware > such (that way I can check the "physical" drive and not by indirect > query)? just use "raw" format.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1212101904100.13453>