On Thu, 27 Feb 2020 20:12:17 +0100 Markus Elfring <Markus.Elfring@xxxxxx> wrote: > > +This allows administrators to pass a structured-Key configuration file > > Does capitalisation matter here for the word “Key”? Oops, thanks! that's a typo of key. > > +If you think that kernel/init options becomes too long to write in boot-loader > > +configuration file or want to comment on each options, you can use this > > Can the following wording variant be a bit nicer? > > +… or you want to comment on each option, … OK, since the previous sentence is too long, it is more readable to put the subject there. > > +Also, some subsystem may depend on the boot configuration, and it has own > > +root key. > > Would you like to explain the influence of a key hierarchy any further? Please read the example (boot time tracer) carefully :) > > +The boot configuration syntax allows user to merge partially same word keys > > by brace. For example:: > > “by braces. > For example::”? I think current one is shorter and compact. > > +The file /proc/bootconfig is a user-space interface to the configuration > > “… is an user-…”? Hm, it seems "a user" is correct wording. https://www.quora.com/Which-is-the-correct-usage-a-user-or-an-user > > +Currently the maximum configuration size is 32 KiB and the total number > > +of key-words and values must be under 1024 nodes. > > * How were these constraints chosen? > > * Can such system limits become more configurable? No. > > +(Note: Each key consists of words separated by dot, and value also consists > > +of values separated by comma. Here, each word and each value is generally > > +called a "node".) > > I would prefer the interpretation that nodes contain corresponding attributes. No. Node is a node. It is merely generic. > > How do you think about to add a link to a formal file format description? Oh, nice idea. Please contribute it :) Thank you, -- Masami Hiramatsu <mhiramat@xxxxxxxxxx>
