Henry was kind enough to resolve the missing modules directory
problem off-line for me after I sent him my /etc/fstab file. The
problem was that:
1) CoLinux parses /etc/fstab to find the root file system.
It does not do any testing (AFAIK) regarding the correctness
of the file, and picks the first root file system mount it finds.
With earlier versions it may have been the last one - this
explains why I did not have this problem with 0.6.2 (unless
something else happened that made it work, I can't remember).
If coLinux doesn't parse the right line, unzipping the modules
archive will fail.
2) I used a /etc/fstab that makes my Linux distro work both
stand-alone (dual-boot) and with coLinux. This requires
that the root file system be mounted differently (/dev/cobd0
or /dev/sda2 in my case - external USB drive). I found that
you can simply define the mount twice, the boot will report
an error for one line or the other depending on how you boot
but will continue and work fine otherwise. So I didn't bother
fixing my /etc/fstab file.
The solution that Henry pointed out to me was to use an alias
in my XML file:
<block_device index="0" path="\Device\Harddisk1\Partition2"
enabled="true" alias="sda2" />
This worked fine after I also removed the /etc/cobd0 line from
The alias keyword is documented in README.txt but not
well enough for most users to understand what it does I think
so I'll try to document it on the Wiki (if I can).
I remember there were some other files that may need to be
changed in order for dual-boot and coLinux operation, namely
/etc/inittab (set the run level to 3 to keep coLinux from starting
X), and /etc/rc.d/rc3.d/S05kudzu (disable kudzu by removing
or renaming it for coLinux). I'm now using it with VNC without
messing with these files, sometimes I have to hit F4 twice to
skip kudzu. I'm only a half-baked Linux user so if anybody
has a more elegant way of dealing with this (shouldn't be too
hard) please let me know and I'll document it as well.
----- Original Message -----
From: "Henry Nestler" <Henry.Ne@...>
To: "Henk" <aling13@...>
Sent: Wednesday, May 17, 2006 11:42 AM
Subject: Re: [coLinux-users] Missing /lib/modules/2.6.11-co-0.6.3
> Henk wrote:
>> I installed CoLinux 0.6.3 on 2 machines, one on my home PC with
>> winXP/SP2 home edition (Fedora FC2 on a separate hard drive), the other
>> one on my work laptop winXP/SP2 professional (Fedora FC3 on an external
>> USB drive). On the latter I see no
>> /lib/modules/2.6.11-co-0.6.3 so modprobe fails. As a result,
>> the boot shows errors and I can't get NFS working.
>> I could of course unzip it manually from vmlinux-modules.tar.gz
>> but has anybody seen this before ? I still have an old directory
>> /lib/modules/2.6.11-co-0.6.2 so with my earlier 0.6.2
>> installation it must have worked fine.
> Do you using initrd.gz from colinux installation?
> That should inject the modules into your root file system.
> If you not use initrd, then coLinux don't install modules.
> Henry Nestler
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> coLinux-users mailing list