| 1 |
First copy the new kernel to /boot (make sure /boot is mounted) with a new |
| 2 |
name like test or something |
| 3 |
|
| 4 |
Then copy this part to the end of lilo.conf. |
| 5 |
|
| 6 |
> image = /boot/bzImage |
| 7 |
> root = /dev/hda7 |
| 8 |
> label = Gentoo |
| 9 |
> read-only # read-only for checking |
| 10 |
|
| 11 |
and change these: |
| 12 |
|
| 13 |
image=name of your new kernel (say Test) |
| 14 |
label=Test |
| 15 |
|
| 16 |
Then save and exit. Run lilo - t and it will tell you if everything is okay. |
| 17 |
If not fix it, then when all is well run lilo. Then reboot and you can test |
| 18 |
your new kernel. |
| 19 |
|
| 20 |
Also man lilo and man lilo.conf will help. |
| 21 |
|
| 22 |
|
| 23 |
On Sunday February 26 2006 18:51, Pete wrote: |
| 24 |
> Someone has given me a system to configure their printer on it. |
| 25 |
> |
| 26 |
> yababa root # uname -a |
| 27 |
> The boot menu says it is LILO, so I went to /etc/lilo.conf |
| 28 |
> |
| 29 |
> This is how it looks |
| 30 |
> |
| 31 |
> ---------------- |
| 32 |
> # $Header: /home/cvsroot/gentoo-x86/sys-apps/lilo/files/lilo.conf,v 1.3 |
| 33 |
> 2002/09/30 00:55:18 woodchip Exp $ |
| 34 |
> # Author: Ultanium |
| 35 |
> # Linux bootable partition config begins |
| 36 |
> image = /boot/bzImage |
| 37 |
> root = /dev/hda7 |
| 38 |
> label = Gentoo |
| 39 |
> read-only # read-only for checking |
| 40 |
> image = /boot/bzImage.OLD |
| 41 |
> root = /dev/hda7 |
| 42 |
> label = Gentoo_Old |
| 43 |
> read-only # read-only for checking |
| 44 |
> image = /boot/bzImageAR |
| 45 |
> root = /dev/hda7 |
| 46 |
> label = Gentoo_new |
| 47 |
> read-only # read-only for checking |
| 48 |
> # |
| 49 |
> # Linux bootable partition config ends |
| 50 |
> |
| 51 |
> ---------------- |
| 52 |
> |
| 53 |
> I added the section |
| 54 |
> ----------- |
| 55 |
> image = /boot/bzImageAR |
| 56 |
> root = /dev/hda7 |
| 57 |
> label = Gentoo_new |
| 58 |
> read-only # read-only for checking |
| 59 |
> ----------- |
| 60 |
> |
| 61 |
> This is what I don't understand |
| 62 |
> |
| 63 |
> ------------------ |
| 64 |
> |
| 65 |
> yababa root # ls -l /boot/ |
| 66 |
> total 1272 |
| 67 |
> -rw-r--r-- 1 root root 483904 Feb 26 04:56 |
| 68 |
> System.map-2.4.19r10AR lrwxrwxrwx 1 root root 1 Jan 12 |
| 69 |
> 2003 boot -> . |
| 70 |
> -rw-r--r-- 1 root root 814688 Feb 26 04:40 bzImageAR |
| 71 |
> yababa root # |
| 72 |
> |
| 73 |
> --------------------- |
| 74 |
> |
| 75 |
> boot points to itself. Before I copied the System.map-2.4.19r10AR and |
| 76 |
> bzImageAR, there was nothing in there. |
| 77 |
> |
| 78 |
> How does the system boot? ? ? |
| 79 |
> |
| 80 |
> Of course if I run /sbin/lilo, the system complains |
| 81 |
> yababa root # /sbin/lilo |
| 82 |
> Fatal: open /boot/bzImage: No such file or directory |
| 83 |
> yababa root # |
| 84 |
> |
| 85 |
> |
| 86 |
> Any pointers will be greatly appreciated ! |
| 87 |
> Regards |
| 88 |
> Pete |
| 89 |
|
| 90 |
-- |
| 91 |
|
| 92 |
Brett I. Holcomb |
| 93 |
-- |
| 94 |
gentoo-user@g.o mailing list |
Archives