[openbeos] Re: Larger Disk for VMWare Image

Urias McCullough wrote:


What you *can* do is take another VMDK, partition it with whatever
tool you desire to whatever size you desire, and mount it as a second
"disk" in the VMX file. You can then use the Haiku DriveSetup to
initialize it as BFS and use it to store "extra" stuff on. You can
then mount it as a second disk any time you get a new Haiku VMDK from
haiku-files.org or wherever. You could maybe even copy the contents of
the Haiku vmdk to the newly created one in an attempt to create a
single larger Haiku boot partition.
I tried mounting the bigger disk and copying files over, but I couldn't make it bootable (and I am not sure that symlinks etc were retained). As for storing extras on that disk kinda makes it hard, since all of the dev environment assumes that its all on the primary disk ? I would love to be able to have all my development stuff (including build-tools, headers etc) on the non-boot drive, but somehow I imagine this isn't possible ? 


Also, you can always build your own vmware images if you're using
Linux or another supported build environment and set the desired size
to whatever you wish as it's built.

Yeah, but I wanted to avoid the build-it-yourself step.

Other related posts: