Re: advice for 2.4 to 2.6 migration
- From: Rainer Weikusat <rweikusat@xxxxxxxxxxx>
- Date: Thu, 24 Apr 2008 11:08:14 +0200
"Bill Cunningham" <nospam@xxxxxxxxx> writes:
I am running a 2.4 kernel with modutils. If I understand correctly there
has been a big change in modules with the 2.6 kernel. How would be the best
way to install the utilities for the 2.6 kernel ?
Insofar this hasn't changed since I did it: Download the source for
the 2.6 module-init-tools, compile and install them. Quoting the
modprobe manpage:
BACKWARDS COMPATIBILITY
This version of modprobe is for kernels 2.5.48 and above. If
it detects a kernel with support for old-style modules (for
which much of the work was done in userspace), it will attempt
to run modprobe.modutils in its place, so it is completely
transparent to the user.
The 'install' target of the Makefile will rename the 2.4 module tools
automatically.
NB: It is usually a bad idea to update parts of an installation
managed by some kind of package manager (rpm, dpkg) manually.
I have thought about compiling the 2.6 kernel and loading it with
the --noinitrd option
Do yourself a favor and don't use initrd, except if you really need a
single kernel capable of booting computers using different disk
subsystems (SCSI, IDE, SATA, ...) or different root filesystem-types.
There is no point in compiling something which is always needed as a
module: It's just more complicated, increases the boot time somewhat
and is somewhat slower.
.
- References:
- advice for 2.4 to 2.6 migration
- From: Bill Cunningham
- advice for 2.4 to 2.6 migration
- Prev by Date: Re: setrlimit() extension suggestion
- Next by Date: Multi-core CPUs & our present Fault Finding capability
- Previous by thread: Re: advice for 2.4 to 2.6 migration
- Next by thread: Multi-core CPUs & our present Fault Finding capability
- Index(es):
Relevant Pages
|
