diff options
| -rw-r--r-- | doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_7_a3de897d9d056fcb6821f3b03485ede5._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_7_a3de897d9d056fcb6821f3b03485ede5._comment b/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_7_a3de897d9d056fcb6821f3b03485ede5._comment new file mode 100644 index 00000000..7c0995ff --- /dev/null +++ b/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_7_a3de897d9d056fcb6821f3b03485ede5._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2017-08-23T21:07:41Z" + content=""" +The vmdk text file is so small that I did think about just having propellor +generate it by itself. I don't know how stable/documented it is however. + +I suppose that if you're distributing a vmdk image to others, you would not +want to use the text file format, since that hard-codes the path to the +.img file. So, perhaps there should be separate properties for vmdk text +files that point at disk images and self-contained vmdk images. +"""]] |