From: Sarah T. <sar...@ya...> - 2004-12-21 18:06:21
|
Android 808 wrote: > Not a problem. > > I have Colinux installed in C:\CoLinux and have created a folder called > "Distributions" within it to host all of the XML and filesystem files > for each distrobution I have installed. > > In Distributions I have put a copy of initrd.gz from C:\CoLinux and have > uncompressed it. The uncompressed file should be called initrd, and > will have no file extension. This folder contains sub-directories for > each of the distributions, just to keep the files easier to manage. > Hopefully the XML file below should clear up any queries about this. > Note that I have included initrd as cobd8. I give filesystems the > .linux extension for quicker searching. > > <?xml version="1.0" encoding="UTF-8"?> > <colinux> > > <block_device index="0" > path="\DosDevices\C:\CoLinux\Distributions\Gentoo 2004.3\Gentoo > 2004.3.linux" enabled="true"/> > <block_device index="1" path="\DosDevices\C:\CoLinux\swap_512MB" > enabled="true"/> > > <block_device index="6" path="\Device\Floppy0" enabled="true"/> > <block_device index="7" path="\Device\CdRom0" enabled="true"/> > > <block_device index="8" > path="\DosDevices\C:\CoLinux\Distributions\initrd" enabled="true"/> > > <bootparams>root=/dev/cobd0</bootparams> > > <image path="vmlinux"/> > > <memory size="108"/> > > <network index="0" type="tap" /> > > </colinux> > > I then start CoLinux with the following command and login as root: > > C:\CoLinux\colinux-daemon.exe -c "Distributions\Gentoo 2004.3.xml" -t nt > > Once this is done you need to create somewhere to mount the initrd image > and then mount it: > > mkdir /mnt/initrd > mount /dev/cobd/8 /mnt/initrd > > I have used /cobd/8 here rather than just cobd8 because Gentoo uses this > in the latest releases. On other distros it may be this or cobd8. Now > cd to this location and run ls just to make sure its mounted and to see > what it actually contains: > > cd /mnt/initrd > ls > > You will notice that the initrd is actually a small filesystem in > itself. I think the original idea was that you could set the initrd > file in the XML config and it would automatically install the modules, > but it never works for me. Run the following to get the modules onto > root directory of the main filesystem and change to this directory. > > cd lib/modules > cp vmlinux-modules.tar.gz / > cd / > > All we need to do now is uncompress the modules as the files in the > archive contain the full path required to install them to the correct > place. > > tar -xzvf vmlinux-modules.tar.gz > > If that last line do work, blame Linux Format and replace it with: > > gunzip vmlinux-modules.tar.gz > tar -xvf vmlinux-modules.tar > > Now restart Colinux to see if has worked. If so, remove the > vmlinux-modules file with: > > cd / > rm vmlinux-modules.tar.gz OR rm vmlinux-modules.tar If you had to > use the second method. > > > I hope this helps. If not, e-mail me and I'll see what I can do. I've > got Gentoo 2004.3, Fedora Core 3, Slackware 10, Debian Sarge and > possibly an LFS6 available if you want one with the modules installed. > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ Hi, I did as you suggested but it seems that my /dev/cobd is only up to /dev/cobd3. Do I have to create a new block device(s)? How? Thanks |