* overwriting module params given on kernel command line?
@ 2012-01-22 9:24 Michael Tokarev
0 siblings, 0 replies; only message in thread
From: Michael Tokarev @ 2012-01-22 9:24 UTC (permalink / raw)
To: Linux-kernel
Hello.
I noticed that recent kernels does not allow overwriting
module parameters given on kernel command line anymore.
One particular example of this is ipv6.disable. I usually
boot kernel with ipv6.disable=1, because all these systems
does not have ipv6 connectivity anyway and v6 isn't needed.
But I remember that in earlier versions it was possible to
specify this parameter in modprobe line:
rmmod ipv6; modprobe ipv6 disable=0
and v6 were enabled after this reload (rmmod is possible
while it is disabled). It works in, at least, 2.6.32
kernels.
But now, in 3.0, the modprobe command line parameter appears
to be ignored and the one specified on _kernel_ command
line takes precedence.
To me, it does not look right, I'd expect modprobe command
line to be "stronger" than kernel command line.
So, am I right that kernel command line has more "weight"
here, and if yes, why?
Thanks,
/mjt
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-01-22 9:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-01-22 9:24 overwriting module params given on kernel command line? Michael Tokarev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®