[klibc] arch.cmd file and init args

Aaron Griffin aaronmgriffin at gmail.com
Tue Jun 6 17:41:42 PDT 2006

On 6/6/06, Jim Cromie <jim.cromie at gmail.com> wrote:
> Aaron Griffin wrote:
> > I don't really understand the necessity of the /arch.cmd file to be
> > parsed before /proc/cmdline.  It seems simpler to just parse the
> > program args first before /proc/cmdline.  The whole point, as far as I
> > see, is to composite kernel params based on scripts and/or the
> > bootloader params.  It makes sense to say "arg1=a" should override
> > (come before) any other arg1, but I see no need to ever need "arg1=a"
> > to come after other arg1 instances.
> Why not ?  wouldnt it make sense to preserve the override capability of
> cmdline,
> instead of assuming you get it all right the 1st time ?
I'm not sure what you mean.  My rationale is that, if you want an
override arg, pass it as a param to kinit, if not, don't pass it at
all.  I don't see the need to spit this information to a file.

> override allows sub-arch variations, eventually evolving to the right
> arch.cmd
> content for each given platform.
I don't know what you mean by this - can you elaborate?

More information about the klibc mailing list