Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Warning: /boot/System.map



I always did so until I booted a previous kernel with the newer System.map
and it work perfectly without errors.  Perhaps I just got lucky there.  Any
ideas?

Brian Conway
dogbert at clue4all.net

Those who do not understand Unix are condemned to reinvent it, poorly.
                -- Henry Spencer


----- Original Message -----
From: <TWG3 at world.std.com>
To: Subba Rao <subb3 at ibm.net>; Brian Conway <dogbert at clue4all.net>
Cc: <discuss at Blu.Org>
Sent: Monday, August 23, 1999 10:38 AM
Subject: Re: Warning: /boot/System.map


> I prefer to have the /boot/System.map be a link to /boot/system.map-2.xxxx
> where 2.xxx is the version of the kernel you have currently running.  Also
take your old system.map and nameit to system.map/2.xxxold.  that way if the
new version creates any problems, you can revert back easily by changing the
target of the links.
>
> this is also preferred for /boot/vmlinuz(x) to be a link to
/boot/vmlinuz-2xxx
>
> Tom Guilderson
> TWG3 at world.std.com
>


-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org