Menu
▾
▴
colinux-users
|
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. |
|
From: Robert C. <rw...@al...> - 2004-05-19 04:16:02
|
On Tuesday, May 18, 2004, at 21:51 US/Central, Aaron Spangler wrote: > I got knoppix 3.3 to work with coLinux.=A0 I had to make a few = changes,=20 > most notably: > ...=A0 > There was a few other changes.=A0 I'll post the full details later = when=20 > I get time. This is fantastic. Yes, please post the full details for others to=20 reproduce. Regards, - Robert |
|
From: wind li <wi...@su...> - 2004-05-19 04:31:20
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Aaron Spangler wrote: <blockquote cite="mid001001c43d4c$22a787f0$6501a8c0@w2000" type="cite"> <meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type"> <meta content="MSHTML 5.00.3813.800" name="GENERATOR"> <style></style> <div><font face="Arial" size="2">I got knoppix 3.3 to work with coLinux. I had to make a few changes, most notably:</font></div> <div> </div> <div><font face="Arial" size="2">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.</font></div> </blockquote> <div>I have much interesting in this. How can we do it ?<br> <br> Thanks<br> Wind<br> </div> <br> <pre class="moz-signature" cols="72"> </pre> </body> </html> |
|
From: Aaron S. <as...@in...> - 2004-05-19 13:58:05
|
I got knoppix to run on top of Win2K using coLinux (mentioned in an
earlier thread). It took a little work.
Currently it requires 2.5 GB of disk space on windows, and a spare
partition on a second computer to get it running
Here is a rough sketch of how to do it for those interested:
1) On a second computer, boot knoppix off of the cd
2) create a 2.5 GB partition, and mkfs it (I chose ext3) and mount it up
as /mnt/newdisk
3) 'cp -a /KOPPIX/* /mnt/newdisk'
3.1) replace /mnt/newdisk/etc/init.d/xsession with
#!/bin/sh
. /etc/sysconfig/knoppix
if [ ! -d /home/knoppix ]; then
mkdir /home/knoppix
chown knoppix:knoppix /home/knoppix
fi
echo "startdke" > /home/knoppix/.xinitrc
# clean up any old lock files
rm -f /home/knoppix/.vnc/*.pid
rm -f /tmp/.X0-lock
rm -fr /tmp/.X11-unix
# start up kde
su - -c "vncserver -geometry 1024x768 -depth 16 :0" knoppix
3.2) create an /mnt/newdisk/etc/fstab
/dev/cobd0 / ext3 defaults 1 1
none /proc proc defaults 0 0
3.3) create some missing devices
mknod /mnt/newdisk/dev/cobd0 b 117 0
mknod /mnt/newdisk/dev/cobd1 b 117 1
mknod /mnt/newdisk/dev/cobd2 b 117 2
mknod /mnt/newdisk/dev/cobd3 b 117 3
mknod /mnt/newdisk/dev/cobd4 b 117 4
mknod /mnt/newdisk/dev/cobd5 b 117 5
mknod /mnt/newdisk/dev/cobd6 b 117 6
mknod /mnt/newdisk/dev/cobd7 b 117 7
3.4) and then unmount /mnt/newdisk
4) On the target computer, install coLinux 0.6.0 and netcat and vncviewer
5) using netcat (nc) on knoppix and netcat on the target computer (win2k),
copy the raw filesystem over as a single 2.5 GB file.
6) modify your default.colinux.xml to look like this, adjusting your path
& ethernet card name as necessary
<?xml version="1.0" encoding="UTF-8"?>
<colinux>
<block_device index="0" path="\DosDevices\c:\colinux\knoppix_ext3"
enabled="true"></block_device>
<bootparams>root=/dev/cobd0 lang=us BOOT_IMAGE=knoppix</bootparams>
<image path="vmlinux"></image>
<memory size="128"></memory>
<network index="0" type="bridged" name="3Com 10/100 Mini PCI Ethernet
Adapter"></network>
</colinux>
7) start up colinux-daemon.exe
8) knoppix will come up and start. It mounts up the root filesystem and
also DHCP's an IP address (make sure you have a DHCP server nearby)
9) After a minute or two, fire up 'vncviewer' with the IP address of
knoppix. (you might have to do an 'ifconfig -a' on the console to
determine the ip). It runs really nice in full screen mode
Notes:
*) If you don't want to use the 'bridged' network, you can make knoppix
only talk with windows, the network line should read as below. Also then
hard code your IP address in windows on the 'tap' ethernet as 192.168.0.1
and hardcode knoppix as 192.168.0.40. Make sure you kill or disable
'pump' in knoppix so that it does not keep trying to dhcp.
<network index="0" type="tap" name="TAP"></network>
*) If we rebuild the coLinux kernel and include the 'cloop.o' driver then
in theory you can point your first block device to a modified ramdisk
(like the boot.img that comes on knoppix) and then point your second block
device to \DosDevices\D:\knoppix\KNOPPIX. This allows you to save 2.5GB
of disk space. Then you can use the knoppix method of persistant home
directories and configuration files. (I have not tried this, please let
me know your experience if you do) Also, once a modified kernel has been
built, the first several steps including the second computer are skipped.
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X