Re: Persistent module storage - modutils design

["H. Peter Anvin" <hpa@zytor.com>]

Followup to:  <20001109045247.BE39A8120@halfway.linuxcare.com.au>
By author:    Rusty Russell <rusty@linuxcare.com.au>
In newsgroup: linux.dev.kernel
> 
> > Modules are loaded before non-root file systems are mounted, damn!
> 
> modules.conf already breaks FHS lib/ badly enough.  Modules loaded
> before /var is mounted won't get persistant data.  Too bad; they
> have to do something sane when it doesn't exist anyway.
> 

Last I checked modules.conf was in /etc, not in /lib.

> 
> > Looks like persistent data has to be stored in /lib/modules/persist (no
> > <version>, see earlier mail).
> 
> You need versions: binary data is too prone to change (proven kernel
> history).  It's the kernel installer's duty to know which ones can be
> safely linked/copied to the new version.
> 
> Otherwise every data change requires a new symbol name: and this will
> happen all the time.
> 

Remember that we cannot rely on ANY form of persistent storage to be
available in the beginning; / may very well be readonly (on a ROM,
say.)  Since that means that we can't rely on writable storage being
available until at least one other filesystem has been mounted, it
might as well be the standard for variable data, i.e. /var.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/