Re: [coLinux-users] does alias name makes any sense?

[Henry N. <hen...@ar...>]

  樊朋 wrote:
> In the source code,i saw "alias=<path to image file>" | :cobdX
> and the following example:"hda1=rootfs.img #(cobdX automaticly from 
> first free)" . If cobd0 is free,then hda1 is the same with cobd0. Does 
> alias name make any sense ? I'm a new-bie.@@.
>
> I have modified the "cobd.c" to support the vmdk file,but I haven't 
> resolve the "alias" problem, and do not support "async".Very 
> depressed. .@@.

cobd.c is not the right place for decoding vmdk files.
cobd are images without partition informations. A cobd image contains 
only a singe partition. That's why a cobd0 can be aliased as hda1, and 
cobd can use as hda2. But never you can use hda with partition tools ala 
"fdisk".

VMDK is an image file over the whole disk, that starts with partition 
informations in the first sector (512 bytes).
A block device with whole disk images under coLinux is the scsi driver.

And last: Reading or writing VMDK is sometimes not linear. So, decoding 
the file positions should not do inside Linux kernel. This is more a 
work for the host side, to have less OS-switches between Linux and Windows.

-- 
Henry N.