I am trying CoLinux for the first time with the stock Debian 4.0 etch EXT3 file system image, as downloaded by the installer.
When I decompress the 32MB bz2 image, it indeed comes out to the full 1GB image size.
However, when I run colinux - things seem to come up properly - (at least to a CLI). I can login, etc.
But....it seems as though tons of files are missing - there's no Apache, there isn't even *VI*!
a "df" tells me that the disk size is about 1GB, however only about 171MB are in use.
I can't beleve that I would have uncompressed this giant disk image which is mostly empty - nor that a stock distributon wouldn't have tools like "vi" - so I'd conclude that there is something really really wrong.
There are no filesystem mount errors on startup.
The images are made very small to save lot of donwload time. Install more programs is very easy.
1. setup "slirp" as network, see http://colinux.wikia.com/wiki/Network#Slirp
It's default inside Debian 4 image. You needs only to add "eth0=slirp" in the colinux config.
2. use 'apt-cache search ...' to locate the package name
3. use 'apt-get install ...' to install the package
The installed editor is typically nano.
see also: http://colinux.wikia.com/wiki/Getting_Started_with_coLinux_-_Long_manual
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.