[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061108201456.GD21485@lug-owl.de>
Date: Wed, 8 Nov 2006 21:14:56 +0100
From: Jan-Benedict Glaw <jbglaw@...-owl.de>
To: Jesper Juhl <jesper.juhl@...il.com>
Cc: Joakim Tjernlund <joakim.tjernlund@...nsmode.se>,
linux-kernel@...r.kernel.org
Subject: Re: How to compile module params into kernel?
On Wed, 2006-11-08 21:09:04 +0100, Jesper Juhl <jesper.juhl@...il.com> wrote:
> On 08/11/06, Joakim Tjernlund <joakim.tjernlund@...nsmode.se> wrote:
> > > -----Original Message-----
> > > From: Jesper Juhl [mailto:jesper.juhl@...il.com]
> > > On 08/11/06, Joakim Tjernlund <joakim.tjernlund@...nsmode.se> wrote:
> > > > Instead of passing a module param on the cmdline I want to compile that
> > > > into the kernel, but I can't figure out how.
> > > You could edit the module source and hardcode default values.
> > Yes, but I don't want to do that since it makes maintance
> > harder.
> Well, as far as I know, there's no way to specify default module
> options at compile time. The defaults are set in the module source and
> are modifiable at module load time or by setting options on the kernel
> command line at boot tiem. So, if that's no good for you I don't see
> any other way except modifying the source to hardcode new defaults.
However, that could probably be hacked in easily. We use a similar
approach for VAX, since we're not yet regularly booting off a local
harddisk, but commonly via MOP off the network.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@...-owl.de +49-172-7608481
Signature of: Ich hatte in letzter Zeit ein bißchen viel Realitycheck.
the second : Langsam möchte ich mal wieder weiterträumen können.
Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)
Powered by blists - more mailing lists