[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] Command-line format clarification
From: |
Vladimir 'φ-coder/phcoder' Serbinenko |
Subject: |
[PATCH] Command-line format clarification |
Date: |
Thu, 14 Jan 2010 16:38:02 +0100 |
User-agent: |
Mozilla-Thunderbird 2.0.0.22 (X11/20091109) |
There is some amount of confusion regarding command line format. I
propose following clarification:
=== modified file 'doc/multiboot.texi'
--- doc/multiboot.texi 2010-01-12 16:49:46 +0000
+++ doc/multiboot.texi 2010-01-14 15:36:23 +0000
@@ -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
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
signature.asc
Description: OpenPGP digital signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [PATCH] Command-line format clarification,
Vladimir 'φ-coder/phcoder' Serbinenko <=