On Wed, Sep 11, 2002 at 01:06:32PM +0200, Andrea Dettori wrote:
> I have build the new kernel with kernel-package, but when I installing
> it, I don't see any entrie in /etc/silo.conf
Yes, the .deb created by kernel-package will not write to your
/etc/silo.conf
Here is what my silo.conf looks like:
partition=1
root=/dev/hda1
timeout=100
image=1/vmlinuz.old
label=linux
read-only
image=1/vmlinuz
label=linux19
read-only
Here is what my `/` looks like:
(root@sixtyfour)/$ ls -alth vmlinuz*
lrwxrwxrwx 1 root root 20 Aug 23 00:30 vmlinuz -> /boot/vmlinuz-2.4.19
lrwxrwxrwx 1 root root 20 Aug 22 23:55 vmlinuz.old -> /boot/vmlinuz-2.4.18
> Why?
Debian uses a standard practice on not editing your lilo/silo
stanza'a within your configuration and simply adding symbolic links
from `/` (root) to `/boot` which they call a boot block.
The steps are the old kernel's symlink is `ln -sf` 'd to to vmlinuz.old
and the new kernel is `ln -sf` 'd to vmlinuz. It works out nicely.
> And where is the kernel ( vmlinuz )
(root@sixtyfour)/boot$ ls -alth
total 3.8M
-rw-r--r-- 1 root root 58K Sep 11 15:18 second.b
drwxr-xr-x 21 root root 4.0K Sep 11 15:18 ..
drwxr-xr-x 2 root root 4.0K Aug 23 00:31 .
-rw-r--r-- 1 root root 619K Aug 23 00:19 System.map-2.4.19
-rw-r--r-- 1 root root 1.2M Aug 23 00:19 vmlinuz-2.4.19
-rw-r--r-- 1 root root 11K Aug 22 23:53 config-2.4.19
-rw-r--r-- 1 root root 1.0K Aug 14 20:58 cd.b
-rw-r--r-- 1 root root 1.0K Aug 14 20:58 fd.b
-rw-r--r-- 1 root root 512 Aug 14 20:58 first.b
-rw-r--r-- 1 root root 1.0K Aug 14 20:58 generic.b
-rw-r--r-- 1 root root 784 Aug 14 20:58 ieee32.b
-rw-r--r-- 1 root root 56K Aug 14 20:58 silotftp.b
-rw-r--r-- 1 root root 512 Aug 14 20:58 ultra.b
-rw-r--r-- 1 root root 7.5K May 31 00:57 old.b
-rw-r--r-- 1 root root 449K Apr 11 14:15 System.map-2.4.18
-rw-r--r-- 1 root root 1.3M Apr 11 14:15 vmlinuz-2.4.18
-rw-r--r-- 1 root root 19K Apr 11 12:55 config-2.4.18
--
Regards,
Time
13
\
9 . 3 clockbot.net
/
6
Attachment:
pgpTyu0mFYUn3.pgp
Description: PGP signature