On Fri, Nov 19, 1999 at 08:01:29AM -0500, rpjday wrote:
> On Fri, 19 Nov 1999, Butler, Mike wrote:
>
> >
> > Hi Adam,
> > I believe the steps are:
> > cd /usr/src/linux
> > make mrproper (cleans up any old compile configs, doing this after
> > make menuconfig will wipe your kernel config - probably what's causing you
> > the trouble)
> > make menuconfig or make xconfig
> > make dep
> > make clean
> > make bzImage (or bzdisk to put it on floppy to try it first - I always
> > do this)
> > cd /lib/modules
> > mv 2.2.13-20 2.2.13-20.old (back up the old stuff)
> > cd /usr/src/linux
> > make modules
> > make modules_install
> > cp /boot/vmlinuz-2.2.12-20 /boot/vmlinuz-2.2.12-20.old
> > cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.2.13-20 (if
> > you did make bzImage earlier)
> > /sbin/lilo
> > reboot
>
> according to a kernel rebuilding article in the premiere issue
> of "maximum linux." it is also necessary to run "depmod -a" in the
> new modules directory, which will create a new file modules.dep.
> is this actually necessary?
This is run at each boot from rc.sysinit anyway. So typically, no.
Maybe other distros don't do this though, dunno.
--
Hal B
[EMAIL PROTECTED]
--
Linux helps those who help themselves
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
