From: Aaron S. <as...@in...> - 2004-05-19 02:49:02
|
I got knoppix 3.3 to work with coLinux. I had to make a few changes, = most notably: 1) The kernel supplied with coLinux does not include the 'cloop.o' = driver necessary to mount the knoppix filesystem. Similarly, the stock = knoppix kernel does not support any of the coLinux drivers. So we must = then use an uncompressed filesystem. In this case, I created a 3GB ext3 = filesystem and then performed a 'cp -a' from the /KNOPPIX filesystem to = the new filesystem while knoppix was running. If we rebuild the kernel = to include both the coLinux patches and include the cloop.o kernel = driver, then modifing the initrd that comes with knoppix is sufficient. 2) Created a link to /dev/hda1 to /dev/cobd0 so the knoppix discover = stuff would stumble on the correct root filesystem. I of course created = a real cobd0. 3) Created a modified xinit so that it would bring up vncserver. I also = then created an icon on my windows desktop that starts up TightVNC's = vncviewer to connect to the knoppix virtual machine. Notes: Keyboard, Video, mouse work awesome. (Full screen VNC works just as = good as standalone knoppix) The image works great in both 'bridged' and 'tap' network modes. The = only problem I found is that if you are running 'bridged' mode and a = DHCP server is not running, then knoppix does not get an IP address. = Because of this you cannot then VNC to vncserver if you are running in = bridged and there is no DHCP server. (In this case, it is better to run = in bridged mode). There was a few other changes. I'll post the full details later when I = get time. |