Maybe something along the lines of a make target for an alternate machine,
here's what I use (named 'ucs' as the name of where I work, it should
obviously be given a better name if it was in the kernel proper:).
ucs: clean depend zImage modules
@( \
MODLIB=/usr/src/linux/INSTALL/$(VERSION).$(PATCHLEVEL).$(SUBLEVEL); \
rm -rf /usr/src/linux/INSTALL; \
cd modules; \
[... middle part of existing modules_install omitted ...]
rm -f .misc .allmods; \
ln /usr/src/linux/arch/i386/boot/zImage /usr/src/linux/INSTALL/vmlinuz-$
(VERSION).$(PATCHLEVEL).$(SUBLEVEL); \
ln /usr/src/linux/System.map /usr/src/linux/INSTALL/System.map-$(VERSION
).$(PATCHLEVEL).$(SUBLEVEL); \
)
This is based on the modules_install target but is designed to build an entire
directory ready to be tarred in /usr/src/linux/INSTALL, and completely cleans
the tree before building.
To install on another machine, untar the resulting tarball, and then just
cp -ipr 2.x.x /lib/modules
cp *-2.x.x /boot
update /vmlinuz* symlinks, run lilo and reboot.
Building an INSTALL directory also makes archiving kernels with appropriate
System.map and modules much simpler.
David.
-
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.altern.org/andrebalsa/doc/lkml-faq.html