From Bugzilla Helper: User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.2.17-14 i686) Description of problem: The rc.sysinit attempts to modify the /boot/System.map symlink each time it is run. This makes is annoying when one wants to mount /boot as a read-only file system. How reproducible: Always Steps to Reproduce: 1.build a system where /boot in on a separate file system 2.after the system is brought up and installed, change fstab so that /boot is mounted read-only 3.reboot Actual Results: On startup you see a message about attempting to modify a read-only file system. Expected Results: No errors about attempts to write into /boot. Since /boot/System.map is already a symlink to the correct /boot/System.map-XYZZY file, no attempt to reform the symlink should have been made. Additional info: Try this symlink: *** rc.sysinit.init Sun May 6 14:49:19 2001 --- rc.sysinit Sun May 6 14:49:19 2001 *************** *** 627,633 **** # 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 -s -f System.map-`uname -r` /boot/System.map fi if [ ! -e /boot/System.map -a -r /boot/System.map-`uname -r` ] ; then --- 627,634 ---- # 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` -a \ ! ! /boot/System.map -ef /boot/System.map-`uname -r` ] ; then ln -s -f System.map-`uname -r` /boot/System.map fi if [ ! -e /boot/System.map -a -r /boot/System.map-`uname -r` ] ; then
Fixed in 6.01-1.