This is a discussion on multiple 2.4.x kernels - seperate module directories? within the Linux Operating System forums, part of the Unix Operating Systems category; --> Out of interest, is there an accepted way of having multiple kernels of the same version on a system ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Out of interest, is there an accepted way of having multiple kernels of the same version on a system with non-shared module directories? By default modules reside under /lib/modules/xxx where xxx is the kernel version - there's no obvious way I've seen of tying it to a particular installed kernel of that version... (say by suffixing the module directory with a user-supplied tag that's also embedded in the kernel at build time) I assume the problem will have been addressed in 2.6.x kernels... :-) cheers Jules |
| |||
| On 2005-04-22, Jules <julesrichardsonuk@remove.this.yahoo.co.uk> wrote: > Out of interest, is there an accepted way of having multiple kernels of > the same version on a system with non-shared module directories? Change the path where each kernel looks for his modules, but what's the point in doing so? Davide -- Never meddle in the affairs of NT. It is slow to boot and quick to crash. --Stephen Harris on alt.sysadmin.recovery |
| |||
| Jules writes: > Out of interest, is there an accepted way of having multiple kernels of > the same version on a system with non-shared module directories? > By default modules reside under /lib/modules/xxx where xxx is the kernel > version - there's no obvious way I've seen of tying it to a particular > installed kernel of that version... Why don't you want to give your different kernels different version numbers? -- John Hasler john@dhh.gt.org Dancing Horse Hill Elmwood, WI USA |
| |||
| Hello Jules (<julesrichardsonuk@remove.this.yahoo.co.uk>) wrote: > Out of interest, is there an accepted way of having multiple kernels > of the same version on a system with non-shared module directories? > > By default modules reside under /lib/modules/xxx where xxx is the > kernel version - there's no obvious way I've seen of tying it to a > particular installed kernel of that version... (say by suffixing the > module directory with a user-supplied tag that's also embedded in the > kernel at build time) Edit the Makefile in the Kernel source directory and change the EXTRAVERSION for each kernel you build. best regards Andreas Janssen -- Andreas Janssen <andreas.janssen@bigfoot.com> PGP-Key-ID: 0xDC801674 ICQ #17079270 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps-sarge.html |
| ||||
| Jules <julesrichardsonuk@remove.this.yahoo.co.uk> wrote: > Out of interest, is there an accepted way of having multiple kernels of > the same version on a system with non-shared module directories? Sure - give them different EXTRAVERSION names and (thus) different module directories. You can't rely on modules compiled differently to work with each other and differently cmpiled kernels (of the same version). But they might. If you wnat to take that chance, set EXTRAVERSION the same for all of them, and they will share. Peter |