Guillaume Rousse <[EMAIL PROTECTED]> writes:
> Each kernel image in /boot has its own entry in /etc/lilo.conf so you
> can choose at boot time which one to use. But there is also one system
> map for each kernel, produced at compilation, and lilo.conf only allows
> one to be specified... So, what exactly is this file used for, and how
> do i manage simultaneous kernel image availability ?
actually the initscripts should do automatically the link for
System.map file to System.map-$(uname -r) :
/etc/rc.sysinit
# Adjust symlinks as necessary in /boot to keep system services from
# spewing messages about mismatched System maps and so on.
if [ -L /boot/System.map -a -r /boot/System.map-`uname -r` ] ; then
ln -sf System.map-`uname -r` /boot/System.map 2>/dev/null
fi
if [ ! -e /boot/System.map -a -r /boot/System.map-`uname -r` ] ; then
ln -sf System.map-`uname -r` /boot/System.map 2>/dev/null
fi
--
MandrakeSoft Inc http://www.chmouel.org
--Chmouel
