>>"mi" == mi <[EMAIL PROTECTED]> writes:
> Since i started compiling different 'flavours' of the same
> kernel-version, i also use symlinks. In my case:
Generally, one uses the --append-to-version option for
make-kpkg to differentiate the images.
> in /boot:
> 'kernel' pointing to a subdirectory '/boot/kernel-x' where x is a digit
> 'vmlinuz' pointing to /boot/kernel/vmlinuz-2.4.18
> 'System.map' poinitng to /boot/kernel/vmlinuz-2.4.18
> ( well this might be not necessary but else there's an ugly log)
> and in /lib/modules:
> '2.4.18' pointing to '2.4.18-x'
Oww. This looks complicaed, and I am not sure what it buys
one, as opposed to appending to the version.
> So, what i have to do for make-kpkg is:
> pre install:
> unlink '2.4.18' to protect the actual modules, and
> post install:
> move the new 2.4.18 to 2.4.18-(x+1) and create a new symlink
> move config-2.4.18, the kernel an System.map into
> a newly created subdir kernel-(x+1), and adjust the symlink 'kernel'.
> Or better, with a little script that also checks anything is alright and
> fiddles out what's to be done, change kernels with a single command 'kernel
> -5'.
> For the boot-menu, there are two more symlinks 'kernel-recovery' and
> '2.4.18-recovery'.
All this would be done for the latest 2 kernel images
automatically (and grub would show you all the images), with no
complicated machinations pre and post install.
manoj
--
The difference between us is not very far, cruising for burgers in
daddy's new car.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
