But I do not understand why I need to run 'make rpm' (I don't need to transfer the kernel rpm package or install on any other Mandriva systems).I have always used 'make install', which installs all the necessary files, including updating the grub menu and creating the initrd image.The Master boot record of /dev/sda has been updated.Reading boot sector from /dev/sdb Warning: /dev/sdb is not on the first disk /boot/boot.0810 exists - no boot sector backup copy made.The "vanilla" kernel is the kernel officially released by Linus, or by a member of the community appointed by Linus (e.g. X are officially maintained and released by Marcelo Tosatti).The distribution's kernel is normally a "vanilla" kernel, with many patches on top of it that either did not get accepted to the "vanilla" kernel, or that the distribution's maker back-ported from newer kernels.During installation security updates are configured for your system and pending updates downloaded and applied, unless you specifically opt out of this or the system was not connected to the Internet.
See The Debian Security Team, Section 7.1 for more information on how the Debian security team works.I ran Xorg configuration utility xorgconfig to set the new card up.Slackware 12.0 ships with a generic nv driver for nvidia cards, but it does not support graphics acceleration and/or direct rendering. Fortunately, nvidia provides a Linux binary driver for your video card that will do direct rendering and 3D acceleration just fine, although the driver is closed-source. Assuming that you're running Slackware 12.0 and using huge generic kernel 184.108.40.206 or newer or the smp version of it, you are going to face some problems compiling the nvidia driver against that kernel.You can check if it's really using your new kernel by running uname -r This should display something like 220.127.116.11-default If the system doesn't start, restart it, and when you come to the LILO boot loader menu, select your old kernel and start the system: You can now try again to compile a working kernel.Don't forget to remove the stanza of the not-working kernel from Interesting and well-written how-to article.Please note that configuration can disrupt diagnostic from our technicians, thank you activate only if you understand what you are doing (the messages from init will only be displayed on the serial port, it will no longer be displayed on the screen).Please note that configuration can disrupt diagnostic from our technicians, thank you activate only if you understand what you are doing (the messages from init will only be displayed on the serial port, it will no longer be displayed on the screen).# lilo -v LILO version 22.7, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2005 John Coffman Released 12-Apr-2005 and compiled at on May 10 2006 Using BIOS device code 0x80 for RAID boot blocks Reading boot sector from /dev/md1 Using MENU secondary loader Calling map_insert_data Boot image: /boot/bz Image-18.104.22.168-xxxx-grs-ipv6-32 Added linux * Reading boot sector from /dev/sda /boot/boot.0800 exists - no boot sector backup copy made.The nvidia installer utility compiles the binary driver to suit your kernel.In Slackware 12.0 the support for Riva framebuffer is enabled by default in the huge-22.214.171.124 and huge-126.96.36.199-smp kernels and it is a problem for the nvidia installer utility.Once the system is installed you can still do more to secure the system; some of the steps described in this chapter can be taken.Of course this really depends on your setup but for physical access prevention you should read Change the BIOS (again), Section 4.3, Set a LILO or GRUB password, Section 4.4, Remove root prompt on the kernel, Section 4.6, Restricting console login access, Section 4.7, and Restricting system reboots through the console, Section 4.8.