Hello,
On Thu, Jul 27, 2000 at 08:15:18PM -0400, Johan Kullstam wrote:
> i think keeping the whole kernel, system.map and modules in one dir
> tree would be better. the current system strikes me as a gratuitous
> spreading of stuff all over creation. why isn't everything to do with
> a kernel installation kept in one place?
>
> 1) stick the image, map ( initial ramdisks &c) into
> /boot/$(uname -r)
> 2) put modules in /boot/$(uname -r)/modules instead of
> /lib/modules/$(uname -r)
>
> so for 2.2.17pre13 you'd have
>
> /boot/2.2.17pre13/bzImage
> /boot/2.2.17pre13/System.map
> /boot/2.2.17pre13/modules/....
I've been using exactly this layout for years.
Moreover, sometimes I keep a lot of kernels of the same version with some
differences in the code, so I give the directories self-speaking names (not
just $(uname -r)) and never have chances to use wrong modules or System.map.
My $0.02
Andrey V.
Savochkin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 31 2000 - 21:00:26 EST