On Wed, Nov 24, 1999 at 11:02:01AM +1100, Herbert Xu wrote:
> Nils Rennebarth <nils@ipe.uni-stuttgart.de> wrote:
> > -the CONFIG_SYSCTL option
> > the later one increases the kernel by >8k. Is this really necessary?
> Definitely.
Even for the installation?
Sooner or later I think we need to abandon the concept of one kernel for
installation and the running system. The killer argument for this had been
to avoid "Debian won't boot after installation" type of problems. I'm
beginning to doubt the validity of this argument. Known reasons for a system
that boots with one kernelconfiguration but not another (I only talk of
kernels compiled from identical sources of course) are:
1) bootloader problems
2) root filesystem can't be mounted because:
2.1) filesystem type not supported by new kernel
2.2) block device not supported by new kernel
3) hardware probing upsets other devices up to hang the system
4) apm problems
5) processor type unsupported
1) is independent of the kernel, only zImage vs bzImage is an issue, and if
both kernels are of the same type it won't matter
2) and 3) won't apply if the two kernels only differ in non hardware
specific options as:
process accounting, quota, ipc, sysctl, networking options, verbose
SCSI error reporting, SCSI logging, Magic SysRq key
I left out everything that could be modularized.
4) and 5) should be that same for install and runtime kernel.
Did I leave out something important?
Nils
--
Plug-and-Play is really nice, unfortunately it only works 50% of the time.
To be specific the "Plug" almost always works. --unknown source
Attachment:
pgpNcYpoVNF9e.pgp
Description: PGP signature