LKCD from SGI

Hi.

I tried to find some information on whether the Linux Kernel Crash Dumps patches are going into 2.4 (or 2.5). Has there been any decision?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

LKCD won't go into 2.4 (or 2.5) until I finish writing the direct disk open/write functions that avoid going through the standard IDE and SCSI drivers. I'm working on it.

As far as work for 2.4 goes, we've got a version on SourceForge that works well (for i386 and 95% for ia64).

As soon as the drivers are done, we'll hopefully get acceptance.

--Matt

P.S. Any way we can standardize 'make install' in the kernel? It's
disturbing to have different install mechanisms per platform ... I can make the changes for a few platforms.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

[Matt D. Robinson]

2.5 material, already on the todo list.

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

What is the thought on this. There is an issue with different boot loaders needing rather dramatically different formats...

Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

2.5 kernel build wish list[1] has a couple of entries for standardising the install targets. My thinking (and I know that some people disagree with this) is that the standard targets of a linux compile are only

* vmlinux
* System.map
* modules in the kernel tree (not installed yet)
* any other bits and pieces that are required to compile external modules against this config.

The install phases are many and varied, depending on whether you are installing on this machine, on another machine, does your boot loader understand ELF, do you have to do the [b]zImage fiddling first, are you doing a network boot from ROM, a network boot over tftp etc.

In current kernels the install phases are mixed in with the compile phase which makes it difficult to handle different install targets. 2.5 will have a default make target which does the compile phase but does nothing that is install related, i.e. default is no [b]zImage, no modules_install etc. There will be separate install targets for any combination that is required and for which people can be bothered writing the make scripts.

[1] ftp://ftp.<country>.kernel.org/pub/linux/kernel/projects/kbuild/makefile-wishlist-2.5-...

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

Could the default target install names int the std kernel be changed to System.map -> System.map-$(KERNELRELEASE)
vmlinuz -> vmlinuz-$(KERNELRELEASE)
and then symlink to that ?

I think everyone that has a stable2.2, a devel 2.2 and a test24 is using that method, so as many distros...

Juan Antonio Magallon Lacarta                                 #> cd /pub
mailto:[email protected]                                     #> more beer

Linux 2.2.18-pre23-vm #3 SMP Wed Nov 22 22:33:53 CET 2000 i686 unknown

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

We could do a lot of things in the install targets. But none of them are going to be done before kernel 2.5. We are in code freeze (is this freeze number 4 or 5?). Changing the install method just before a new kernel branch is released will not be popular with the distributors.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

The /sbin/installkernel hooks allow you to do this (and other stuff) very easily:

# make install

does it all for you on Red Hat. I've attached their /sbin/installkernel in case you want to see how its done.

Matthew.

#! /bin/sh

#

# /sbin/installkernel  - written by [email protected]
#

INSTALL_PATH=/boot

KERNEL_VERSION=$1
BOOTIMAGE=$2
MAPFILE=$3

if [ -f $INSTALL_PATH/vmlinuz-$KERNEL_VERSION ]; then

      mv $INSTALL_PATH/vmlinuz-$KERNEL_VERSION \
              $INSTALL_PATH/vmlinuz.old;

fi

if [ -f $INSTALL_PATH/System.map-$KERNEL_VERSION ]; then

      mv $INSTALL_PATH/System.map-$KERNEL_VERSION \
              $INSTALL_PATH/System.map.old; 

fi

cat $BOOTIMAGE > $INSTALL_PATH/vmlinuz-$KERNEL_VERSION cp $MAPFILE $INSTALL_PATH/System.map-$KERNEL_VERSION

ln -fs vmlinuz-$KERNEL_VERSION $INSTALL_PATH/vmlinuz ln -fs System.map-$KERNEL_VERSION $INSTALL_PATH/System.map

if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi

Yes, I know. I thought you were talking about '2.5 kernel build wish list'.

Juan Antonio Magallon Lacarta                                 #> cd /pub
mailto:[email protected]                                     #> more beer

Linux 2.2.18-pre23-vm #3 SMP Wed Nov 22 22:33:53 CET 2000 i686 unknown

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/