On Tue, Nov 07, 2000 at 01:55:59PM +, Alan Cox wrote:
> > Note! This _has_ to be in the / filesystem so it works before mounting the
> > rest of the stuff (if ever). This would rule out /var, and leave just
> > /lib/modules/. Makes me quite unhappy...
>
> The /lib filesystem is likely not wr
On 8 Nov 2000 21:09:49 -0800,
"H. Peter Anvin" <[EMAIL PROTECTED]> wrote:
>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 unti
On Thu, 09 Nov 2000 15:52:47 +1100,
Rusty Russell <[EMAIL PROTECTED]> wrote:
>In message <[EMAIL PROTECTED]> you write:
>> Looks like persistent data has to be stored in /lib/modules/persist (no
>> , see earlier mail).
>
>You need versions: binary data is too prone to change (proven kernel
>histo
Followup to: <[EMAIL PROTECTED]>
By author:Rusty Russell <[EMAIL PROTECTED]>
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 pers
In message <[EMAIL PROTECTED]> you write:
> On Tue, 07 Nov 2000 10:30:39 -0300,
> Horst von Brand <[EMAIL PROTECTED]> wrote:
> >Note! This _has_ to be in the / filesystem so it works before mounting the
> >rest of the stuff (if ever). This would rule out /var, and leave just
> >/lib/modules/. Mak
On Tue, 7 Nov 2000 16:30:22 -0600 (CST),
Jesse Pollard <[EMAIL PROTECTED]> wrote:
> From: Keith Owens <[EMAIL PROTECTED]>
>> No need for a separate size field. Note that MODULE_PARM is built at
>> compile time so all persistent data must have a fixed compile time
>> size.
>
>I'll buy that - but
From: Keith Owens <[EMAIL PROTECTED]>
> On Tue, 7 Nov 2000 10:01:02 -0600 (CST),
> Jesse Pollard <[EMAIL PROTECTED]> wrote:
> >Keith Owens <[EMAIL PROTECTED]>:
> >> Enough people have asked for persistent module storage to at least
> >> justify me writing the code. The design is simple.
> >>
On Tue, 7 Nov 2000 10:01:02 -0600 (CST),
Jesse Pollard <[EMAIL PROTECTED]> wrote:
>Keith Owens <[EMAIL PROTECTED]>:
>> Enough people have asked for persistent module storage to at least
>> justify me writing the code. The design is simple.
>>
>> MODULE_PARM(var,type) currently defines type as [
Keith Owens <[EMAIL PROTECTED]>:
> Enough people have asked for persistent module storage to at least
> justify me writing the code. The design is simple.
>
> MODULE_PARM(var,type) currently defines type as [min[-max]]{b,h,i,l,s}.
> For persistent data support, type is now [min[-max]]{b,h,i,l,s}
On Tue, 07 Nov 2000 11:47:57 -0300,
Horst von Brand <[EMAIL PROTECTED]> wrote:
>Keith Owens <[EMAIL PROTECTED]> said:
>> It makes no sense to allow duplicate module names in the same kernel
>> tree. "modprobe foo" - which one gets loaded?
>
>Why the tree then?
Mainly so you can "modprobe -t net
Keith Owens <[EMAIL PROTECTED]> said:
[...]
> It makes no sense to allow duplicate module names in the same kernel
> tree. "modprobe foo" - which one gets loaded?
Why the tree then?
--
Dr. Horst H. von Brand mailto:[EMAIL PROTECTED]
Departamento de Informatica
> Note! This _has_ to be in the / filesystem so it works before mounting the
> rest of the stuff (if ever). This would rule out /var, and leave just
> /lib/modules/. Makes me quite unhappy...
The /lib filesystem is likely not writable so /var is the right default.
Any reason it cant be overridde
On Tue, 07 Nov 2000 10:30:39 -0300,
Horst von Brand <[EMAIL PROTECTED]> wrote:
>> Keith Owens <[EMAIL PROTECTED]> said:
>> > I have not decided where to save the persistent module parameters. It
>> > could be under /lib/modules//persist or it could be under
>> > /var/log or /var/run. I am tendi
On Tue, 07 Nov 2000 09:45:42 -0300,
Horst von Brand <[EMAIL PROTECTED]> wrote:
>Keith Owens <[EMAIL PROTECTED]> said:
>> I have not decided where to save the persistent module parameters. It
>> could be under /lib/modules//persist or it could be under
>> /var/log or /var/run. I am tending towar
Horst von Brand <[EMAIL PROTECTED]> said:
[Yes, I know this is bad taste...]
> Keith Owens <[EMAIL PROTECTED]> said:
>
> [...]
>
> > I have not decided where to save the persistent module parameters. It
> > could be under /lib/modules//persist or it could be under
> > /var/log or /var/run. I
Keith Owens <[EMAIL PROTECTED]> said:
[...]
> I have not decided where to save the persistent module parameters. It
> could be under /lib/modules//persist or it could be under
> /var/log or /var/run. I am tending towards /var/run/module_persist, in
> any case it will be a modules.conf paramete
On Tue, 07 Nov 2000 15:00:11 +1100,
Keith Owens <[EMAIL PROTECTED]> wrote:
>insmod takes parameters from modules.conf, from the saved persistent
>data (see below) and from the command line, in that order. The last
>value for a parameter takes precedence.
Correction: modprobe takes parameters fr
Enough people have asked for persistent module storage to at least
justify me writing the code. The design is simple.
MODULE_PARM(var,type) currently defines type as [min[-max]]{b,h,i,l,s}.
For persistent data support, type is now [min[-max]]{b,h,i,l,s}{p}, the
trailing 'p' for persistent is opt
18 matches
Mail list logo
