nection, it's not very
handy.
Of course there is also an orthogonal way of doing this consisting in
adding a boot menu to the BIOS. Implementing both ways would of course
be nice, but the monitor solution would have my preference :)
Regards,
Gildas
2007/12/3, Dan Kenigsberg <[EMAIL PROTECTED]>:
> On Mon, Dec 03, 2007 at 01:34:16PM +0000, Gildas wrote:
> > Hi,
> >
> > I don't know whether this is an easy one or not and if it will apply
> > to all archs, but I'd like to see an option in the monitor
2007/12/3, Daniel P. Berrange <[EMAIL PROTECTED]>:
> On Mon, Dec 03, 2007 at 01:34:16PM +0000, Gildas wrote:
> > Hi,
> >
> > I don't know whether this is an easy one or not and if it will apply
> > to all archs, but I'd like to see an option in the mon
Boot disk hinting
W No BIOS provided EDD information for multi-disk OS installs
The kit is available from http://www.linuxfirmwarekit.org/download.php.
Cheers,
Gildas
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/lis
Creating a temp file maybe?
Cheers,
Gildas
2007/4/12, Francois Visconte <[EMAIL PROTECTED]>:
Hello,
I'm currently developing an OS deployment tool similar to G4U (ghost for
unix).
This is a very basic tool
- boot an initrd
- configure network
- ssh deployment-server &q
quote the automation part of the "James White Manifesto"[1], a
document that is gaining a lot of traction in the sysadmin/devops community:
"The provided API must have all functionality that the application provides.
The provided API must be tailored to more than one language and
't be a single company project ;)
My humble 2 cents as an operations person,
Gildas
--
[1] firewalling is also important on internal networks if you work in a
large environment, and having a single port makes it easier to
understand what is going on when diagnosing issues.
[2] You also nee
