Where are the documents?

Logged In: YES
user_id=757205

Well first of all this isn't a Linux distribution, second of
all, have you tried looking at the project homepage? (Hint:
Theres a link at the top of this page or there is also this:
http://www.colinux.org\)). It includes link to a Wiki which
full documents everything you should need to get a coLinux
install working.

This page
(http://wiki.colinux.org/cgi-bin/GettingStartedLong) should
tell you what you need to know.

Sam

Logged In: YES
user_id=37021

I posted some notes about this either on this list or the
xen list. it turns out it's a relatively simple albeit
tedious process to make distribution independent disk
images. You need to start with qemu. These instructions
also sent him that colinux does not have the ability to work
with a partitioned disk image.

boot your distribution into a QEMU disk image.
Use a 2 partition layout (root and swap)
make your root partition the first partition.
make your swap partition as small as possible. If you can
eliminate it, all for the better.

This will create a baseline image for you. Don't worry
about networking not working and do not install or at least
disable X11.

Exit qemu

run fdisk -lu on the baseline image. You should get
something like:

esj@rufus:~$ fdisk -lu ubuntu-server.img
You must set cylinders.
You can do this from the extra functions menu.

Disk ubuntu-server.img: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders, total 0 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks
Id System
ubuntu-server.img1 * 63 9976364 4988151
83 Linux
ubuntu-server.img2 9976365 10474379 249007+
5 Extended
ubuntu-server.img5 9976428 10474379 248976
82 Linux swap / Solaris

then calculating the byte offsets, extract the root image.
it's important to get the skip offset correct otherwise the
disk image will not be usable. It's okay to make the
partition length a little long so use the ending sector
information to calculate the length. If you make the
partition a little short, you may get mysterious failures
somewhere down the road.

for this example, the copy command would look like:
dd skip=32256c count=812899328c if=ubuntu-server.img
of=ubuntu-server-root.img

copy of the root image to your colinux machine and you
should be all set to fix all of the shortcomings like
networking and additional disk space.

In theory you should be able to use the baseline image and
qemu for all of these operations but only if you can get the
networking working very easily is it worth doing it that
way. I frequently find it easier to run qemu on a Linux
machine, do the extraction there and copy the disk image to
Windows.