[klibc] arch.cmd file and init args

Jim Cromie jim.cromie at gmail.com
Tue Jun 6 16:51:27 PDT 2006

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 
instead of assuming you get it all right the 1st time ?

override allows sub-arch variations, eventually evolving to the right 
content for each given platform.

More information about the klibc mailing list