I download http://jaist.dl.sourceforge.net/sourceforge/colinux/Gentoo-colinux-i686-2007-03-03.7z
(107.7MB), Extract to c:\gentoo, Test running c:\gentoo\gentoo.bat,
and found that there is FATAL: Could not open '/System.map': No such
file or directory [ !! ].
coLinux installer is
I think it is a kernel-building-related. Is the problem is realy
FALTAL ? How can I fix it ?
The same problem occured with Gentoo 2007.0 stage3 i686 too when I
try to setup my own rootfs.
Below are readme.txt of downloaded rootfs
To get started, run gentoo.bat. This assumes that you've installed
coLinux in C:\Program Files\coLinux (the default) and extracted this
folder into C: (so that the files are in C:\gentoo). If you haven't,
you'll need to edit gentoo.conf and gentoo.bat.
The password for root is root.
eth0 is configured to work as slirp device.
eth1 is optional, if you have a TAP-win32 adapter with IP address
192.168.200.1 and no gateway address.
This is a basic install of Gentoo 2006.1, brought up to date with an
emerge --sync && emerge world on 2007-02-23 (+syslog-ng, vixie-cron,
dhcpcd, screen). It's setup to run on i686 with NPTL.
You'll probably need to change the following:
* The amount of memory allocated to Gentoo (gentoo.conf)
* Timezone (/etc/localtime)
* Portage and rsync mirrors (/etc/make.conf)
* TAP Network (gentoo.conf, /etc/conf.d/net)
--Chris Forno, 2007-02-25
--Henry N., 2007-03-03
From: Henry Nestler <Henry.Ne@Arcor.de> - 2007-06-01 17:53:05
Wisut Hantanong wrote:
> I download http://jaist.dl.sourceforge.net/sourceforge/colinux/Gentoo-colinux-i686-2007-03-03.7z
> (107.7MB), Extract to c:\gentoo, Test running c:\gentoo\gentoo.bat,
> and found that there is FATAL: Could not open '/System.map': No such
> file or directory [ !! ].
> I think it is a kernel-building-related. Is the problem is realy
> FALTAL ? How can I fix it ?
It'n non fatal. Some debugging tools would not work.
Colinux don't ships the kernel symbol file.
You can fix it by hand. Copy the kernel file 'vmlinux' to a directory
under colinux and run this: "nm vmlinux > System.map", than copy this
file into your /boot directory.
Typicaly coLinux no have and no need a boot directoy. So I don't know
why you have such strong message. Under my systems this is only a
"warning" and not a "fatal".