it should be mentioned that in the latest fog kernels pauses have been added that require interaction when in debug mode. this allows you to read the messages that come up during the process.

I’ll see about getting the descriptions edited, but I’d rather not make a schema change to alter text. While I’ve done so in the past, it’s really seems like overkill to keep adding to schema versions simply to edit a typo or change some text.

That said, there are class variables that I could work with to get the same effect without altering the schema.

I think someone moved the post from the Bug section to the Features request section, before that was done, yes this was posted here.

Hello Tom

thanks your “wondering” (and your work on/at fog) 🙂

Your are right: It’s hard to get rid off GPT. But that’s by intension, but
I’m lucky currently not to have to handle GPT-
I think i will use fog to deploy an “embedded” OS.
So the disks delivered are empty (i think all “00”), uses MBR.
But don’t (usually) have a BIOS compatible console.
So there is problem with the debug-option 🙂
No keyboard, No screen.
Deploying via fog would have been so elegant.

If i could give help i would like to help to find the reason while that big fog script fails to detect that the disk is empty.
I see it is looking on /proc/partition and asks sfdisk. All say: There is a “/dev/sda” (but no /dev/sda1)
I used a dd | hexdump to see that the first 32MB are really empty(=zero(0)).

A new feature request thread (i’ll place there):
Would it make sense the setup a syslogd so the fog-script could sent persistent log file entries the fog-server.
IIRC this are only some line of configuration in /etc and installing

[quote=“Junkhacker, post: 34699, member: 21583”]is there a reason you quoted yourself without adding anything new?[/quote]
No, a quote was not my intention, sorry.
sorry this BB is new to. I’ll try to find the button to turn that useless quoting off.