On Mon, 27 Aug 2012 21:27:43 +0200, Thomas Neumann
blacky+...@fluffbunny.de said:
Turn
FAI::execute_command($FAI::commands{$_}{cmd});
into
print '[fake-mode] $FAI::commands{$_}{cmd} . \n;
That way you can see the list of commands and have a visual check on what
Why not use setup-storage without -X which prints all commands without
executin them?
Ah. Yes. Forgot about it since I started rewriting setup-storage so it
doesn't need root-priviledges for a dry-run. (e.g. setup-storage without
'-X' will still happily try to stop md devices and access the raw
Hi guys,
I've been trying to find a bug in one of my setups. It ended up being a
bogus virtual option in disk_config line.
The documentation says:
| virtual
/* do not assume the disk to be a physical device, use with xen *
Since it said do not assume, I just thought it would be
As for the bug, can the documentation be changed to:
| virtual
/* the device is not a physical disk, use with virtual machine hosts */
Objection. This does not apply for other virtual machines like e.g.
VMware. Xen is rather specific in that regard. But I'm tempted to say it
would be
Thomas Lange la...@informatik.uni-koeln.de wrote:
Why not use setup-storage without -X which prints all commands without
executin them?
Okay, I tried running with '-X' now, but there's still a logical bug which
makes it a bit less useful for automated testing[1]. After the commands
have been
Hello everyone
Can you help me out and send me your disk_configs (via private mail)? The more
the better. May it be a trivial one or highly sophisticated. I'd like to build
a nice sample collection which to test setup-storage against. [It doesn't even
matter if the config is supposed to work,
