Re: A module bug in 2.2.1?

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Dustin Marquess: "Re: VESA fb"
• Previous message: Serguei Koubouchine: "The strange behaviour of gdth driver"

You don't know beforehand where the module itself will end up, so you'll
have to do relocation anyway. If so, you can go the whole way just as
easily.

> - Why the hell do we store the modules in the file system instead of a
> special purose database (read: single file)

Read up on initrd / ram disk / ROMfs. Voila, you have a single file but you
still can access the things like they're in a file system.

Anyway, you haven't said why anybody would want to have all the modules in
a single file in the first place.

> I could continue but who cares anyway...
>
The current system works, and (for me at least) it works rather well.
So what exactly is your problem?

-- 
Matthias Urlichs  |  noris network GmbH   |   smurf@noris.de  |  ICQ: 20193661
The quote was selected randomly. Really.    |      http://www.noris.de/~smurf/
-- 
PENGUINICITY!!

-
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/






 Next message: Dustin Marquess: "Re: VESA fb"
 Previous message: Serguei Koubouchine: "The strange behaviour of gdth driver"