arch/i386/boot/Makefile improvement propose

Stanislav V. Voronyi (stas@cnti.uanet.kharkov.ua)
Sat, 23 Jan 1999 00:30:48 +0200

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Charles Cazabon: "Re: Random number generator for skiplists"
Previous message: Brian Gerst: "Re: why is vesafb not a module?"

Testing the 2.2.0-preX kernels I found that its very
inconvenient to have only vmlinuz & vmlinuz.old. As for me better
keep several kernels to have possibilities to downgrade & compare
if needed. So I propose to make arch/i386/boot/Makefile target
zlilo as follow:

zlilo: $(CONFIGURE) $(BOOTIMAGE)
if [ -f $(INSTALL_PATH)/vmlinuz ]; then mv $(INSTALL_PATH)/vmlinuz $(INSTALL_PATH)/vmlinuz.old; fi
if [ -f $(INSTALL_PATH)/System.map ]; then mv $(INSTALL_PATH)/System.map $(INSTALL_PATH)/System.old; fi
cat $(BOOTIMAGE) > $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE)
cp $(TOPDIR)/System.map $(INSTALL_PATH)/System.map-$(KERNELRELEASE)
ln -s $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) $(INSTALL_PATH)/vmlinuz
ln -s $(INSTALL_PATH)/System.map-$(KERNELRELEASE) $(INSTALL_PATH)/System.map
if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi

This one completely compatible with original, but allow to keep old kernels
marked which is one. BTW procps utils (ps, top) looks for /boot/System.map-2.2.0-$(KERNELRELEASE)
first, and /boot/System.map as the second.

SY, Stanislav Voronyi.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Charles Cazabon: "Re: Random number generator for skiplists"
Previous message: Brian Gerst: "Re: why is vesafb not a module?"