On Sat, 17 Jun 2000, Keith Owens wrote:
>>> It's somewhat unfortunate that this is in /boot, since it isn't a file
>>> requiring for booting. /boot is often a very small filesystem.
>>Agreed. /boot is used in most of the programs that use the map file tho and not
>>too many of the programs look in the /lib/modules dir.
><aol>Me Too</aol>. The amount of crud that gets stuck in /boot by
>distributions is horrendous. /boot should contain boot loader stuff
>only, i.e. second stage loaders, kernels and disk maps for the kernel
>blocks. System.map and .config should go in /lib/modules/`uname -r`,
>even on systems that have no modules. No need for a separate directory
>like /lib/kernel, it would be just one more place to clean up.
I don't understand you people. You start off with "it doesn't belong
in /boot as it has nothing to do with boot-up." But with your very next
breath, you suggest placing it in /lib/modules where it _clearly_ does not
belong -- it's not a module; it's not used by modules or with module loading
(unless you have a "HACKER TOOL" modutils); and gerenally has NOTHING AT ALL
to do with modules.
It at least has SOME validity for being in /boot as that's where the kernel
is. It needs to be placed somewhere and along side the kernel it references
is the best place I can think of.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:16 EST