Skip to contentSkip to conversation

Command-line format clarification

PATCH New Vladimir 'φ-coder/phcoder' Serbinenko 1 participant 1 message Jan 14, 2010

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Command-line format clarification

There is some amount of confusion regarding command line format. I propose following clarification:
=== modified file 'doc/multiboot.texi'

multiboot.texi 2010-01-14 15:36:23 +0000 renamed from multiboot.texi 2010-01-12 16:49:46 +0000 +4 -1
@@ -707,7 +707,11 @@
 If bit 2 of the @samp{flags} longword is set, the @samp{cmdline} field
 is valid, and contains the physical address of the command line to
 be passed to the kernel. The command line is a normal C-style
-zero-terminated string.
+zero-terminated string. The exact format of command line is left to
+OS developpers. General-purpose boot loaders should allow user a complete
+control on command line independently of other factors like image name.
+Boot loaders with specific payload in mind may completely or partially

generate
+it algorithmically.

If bit 3 of the @samp{flags} is set, then the @samp{mods} fields indicate to the kernel what boot modules were loaded along with the

Signature · 2 lines
Regards
Vladimir 'φ-coder/phcoder' Serbinenko