A few days ago CentOS 5.3 was finally released. Just like what I have done with the previous version, I created a coLinux environment. This installation is a base system performed using the previously described manual method. Updated instructions are included in the published archive.
For now you can find the files here:
colinux-centos53.exe [VIPeers] [dropbox] (98mb)
It is configured to use DHCP on the network connections eth0 (slirp) and eth1 (bridged). The user account is 'root' without a password. After login, you should change the password. During startup you will see some complaints about the kernel modules. To solve this you can install my kernel modules RPM or use the tarball provided by coLinux.
Archive
- December 2009 (1)
- November 2009 (3)
- October 2009 (1)
- September 2009 (2)
- August 2009 (2)
- July 2009 (1)
- May 2009 (1)
- April 2009 (1)
- March 2009 (4)
- February 2009 (1)
- January 2009 (1)
- December 2008 (1)
- November 2008 (4)
- August 2008 (1)
- May 2008 (2)
- April 2008 (1)
- February 2008 (1)
- January 2008 (1)
- September 2007 (1)
- August 2007 (5)
- July 2007 (9)
- June 2007 (2)
- May 2007 (2)
- April 2007 (5)
Followers
10 comments:
Forgot to configure the network to start as enabled. Login and perform the following command:
cat > /etc/sysconfig/network << END
NETWORKING=yes
HOSTNAME=localhost.localdomain
END
Sorry for missing this on release.
I tried to install this (I use E:\coLinux for the coLinux path), but it wouldn't install.
I changed the paths in all of the files (install.bat and .txt as well as run.bat and .txt). What else should I try to do?
Ok, fixed that issue by changing ram to be used from 512 to 256. Now it is complaining about not having the install_initrd.gz file.
@Arthur. You only need to use the install.cmd if you want to reinstall the system as the system is already installed. It was included as reference (to be used with the instructions as described in the instructions.txt).
You would only need to alter the run.txt to include the path you use for the coLinux application. When you would use the run.bat, the environment would start.
Hi, gbrand!
Tested this out of the box instllation, and all behaves as written down here in this blog!
Olso the aditional network configuration.
cat > /etc/sysconfig/network << END
NETWORKING=yes
HOSTNAME=localhost.localdomain
END
Hi Gerard,
I have followed the instructions by installing coLinux to the default location (program files\coLinux) and installed this Centos image into the same directory. I run the run.bat and everything starts up as expected and i can log in. The problem is that both winscp and putty refuse to connect to the virtual image.
I did the extra steps to start the networking and centos is picking up an ip address in the correct range (192.168.0.x) via dhcp on eth1. I can ping the windows box from centos and can ping the centos ip from windows and i can even telnet to centos port 22 (and confirmed sshd is running on centos), yet winscp simply won't connect to the ip address.
I'm using winscp 4.2.1 and putty 0.60 and i have tried coLinux 0.74 stable as well as a dev build of 0.80 (20090520).
I usually use vmware and centos 4 but i'm looking at colinux as an alternative so i may have made a newbie mistake somewhere, i just can't quite work out where.
Any ideas would be greatly appreciated.
Great job on the images by the way, it saved me a load of hassle!
Regards
Following up on my last comment i have figured out why SSH connections fail even though pinging works after a dig around the coLinux wiki. It is a known problem with certain network cards and pcap networking.
http://colinux.wikia.com/wiki/Network#WinPcap
Towards the bottom under Notes it mentions disabling "Checksum Offload" for Broadcom NICs and this was the cause.
I went into Control panel->Network connections and brought up the properties of my "Local area connection". I hit the Configure button next to the adapter name and disabled and Checksum Offload on the Advanced tab.
Hope that helps!
I installed centos to an alterntive location but was able to boot with the 1of6 iso after adjusting the paths. I have two questions/issues:
- I use wifi so changed the eth1 as this:
eth1=pcap-bridge,"Wireless Network Connection",,
The "Wireless Network Connection" adapter is the right name, but eth1 fails to acquire an ip. I have mac address filter on wifi, so added the mac id of eth1 to the router filter but it didn't still work after a reboot. What else could be going wrong here? I don't have any firewall (windows firewall service is disabled).
- The other issue is probably a generic question on coLinux. I was expecting to go through an install step, but was surprised to see it come right up. Does this mean, it is running in some sort of live OS from the CD iso? On the other hand, my changes to the filesystem seem to persist, so are they getting layered on top of the ISO?
@Irha
Wifi can cause issues. I have never been able to really use it, so instead I advice you to try a wired connection. The people in the coLinux could provide you with better support related to this topic: http://sourceforge.net/projects/colinux/support
coLinux would use the harddisc image (*system.img) on bootup. I am not sure what you were seeing. But it could be the debian installer or the centos installer. If you have used the images I provided, you would start an installed CentOS 5.3 system. This would of course persist any changes you made, since it is like having a virtual machine running.
Post a Comment