RE: [expert] mdksecure kernel and SMP
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
RE: [expert] mdksecure kernel and SMP
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! 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
Re: [expert] mdksecure kernel and SMP
Joanne Treurniet wrote: > > 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 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. You need to update lilo.conf. You will need to copy BzImage, and System.map to /boot. This is how its done.. First delete the modules for the kernel you are compiling, located in /lib/modules/ make dep && make bzImage && make modules && make modules_install cp arch/i386/boot/bzImage /boot/vmlinuz-2.2.14 (or other vesion) cp System.map /boot/System.map-2.2.14 next you need to edit, /etc/lilo.conf and either make a new label entry for it, or simple copy over the existing SMP kernel so you don't have to. After this is done, do /sbin/lilo then reboot.. if you need more detailed information, look in /usr/doc/mandrake/en/index.html and then select the user guide and goto Chapter 11 titled "Compiling and installing new kernels" hope this helps..
Re: [expert] mdksecure kernel and SMP
On Mon, 8 May 2000, Joanne Treurniet wrote: > 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. Did you install the kernel? As in, copy System.map and bzImage to /boot and update the symlinks? And update lilo? If not, well, just compiling a kernel and rebooting will not get you running on your new kernel. > 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. I suppose you might poke around linux-mandrake.com or your /usr/doc directory for information on which patches they applied to make their "secure" kernel. If you don't find something, e-mail some developers directly. I know their addresses are available on the Mandrake web site. -Matt Stegman <[EMAIL PROTECTED]>
[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