On Mon, 08 May 2000, you wrote:
> You're new kernel is /vmlinuz . Lilo.conf points to /boot/vmlinuz . Create
> a new kernel a million times and it still will execute the old kernel. I
> can't imagine why L.M. delivers it this way!
They don't deliver it that way(?) I compiled 2.2.15-1mdk this
morning from the cooker source and headers rpm's. As MUO
instructs, I edited the Makefile ie, 'EXTRAVERSION = -Tom', and
_as instructed_, uncommented this line 'INSTALL_PATH=/boot'.
After I finished with 'make xconfig', I ran 'make dep && make
clean && make bzImage && make install && make modules && make
modules_install' (as instructed) and was all set to boot to the
_new_ kernel courtesy of L.M.
I don't remember, it was either at the end of 'make install' or
'make modules_install' that lilo was edited and re-run for me.
Nothing to do but re-boot. Well, I did add the 'old' section
(below) and ran '/sbin/lilo' again before I re-booted, but the
label 'linux' was already pointing to the newly compiled kernel &
modules.
|
image=/boot/vmlinuz
label=linux
root=/dev/hdb6
append=""
read-only
image=/boot/vmlinuz-2.2.14-15mdk
label=old
root=/dev/hdb6
append=""
read-only
--
.. Tom Brinkman [EMAIL PROTECTED]
Either:
>
> 1) cp -a /vmlinuz /boot/vmlinuz
> 2) change /etc/lilo.conf to image=/vmlinuz
> or better
> 3) edit /usr/src/linux/Makefile and change INSTALL_PATH= to
> INSTALL_PATH=/boot
> then make bzlilo
>
>
> Hope this helps,
> Bill
>
> P.S. You can skip the make bzImage step when you build a new kernel. And
> after make bzlilo, don't forget:
> make modules
> make modules_install
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Joanne Treurniet
> Sent: Monday, May 08, 2000 10:44 AM
> To: [EMAIL PROTECTED]
> Subject: [expert] mdksecure kernel and SMP
>
>
> Hi all,
>
> I'm new to the list and loath to call myself an expert, but I think I need
> experts to answer my question and there's no "sort-of-expert" category.
>
> I've just installed Mandrake Linux 7.0-2 with paranoid security level and
> using the mandrake secure kernel. I wound up with 2 kernels in lilo.conf,
> linux (vmlinuz-secure) and linux-up (vmlinuz).
>
> I found while trying to install some software meant for uni-processor
> machines (OSS) that the secure kernel defaults to SMP on. So I did the ol'
> xconfig; make dep; make bzImage; make bzlilo with the SMP option off,
> rebooted and it was still SMP.
>
> I gather from the above that the secure kernel comes precompiled only, with
> SMP on and no source, so you cannot make any changes. Is there a patch to
> the un-secured kernel to deal with the buffer-overflow attacks, so that I
> can configure the kernel to my system? Any advice would be appreciated.
>
> Thanks,
> Joanne
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
