>> The file format will trigger specific parsing efforts. > > Maybe. If someone is interested in expanding their command, (e.g. vim) > they can use EBNF to understand syntax, I hope so. > or directly reuse lib/bootconfig.c which provides a compact parser. :) I see some development challenges according to this design direction. This software component is using programming interfaces from the Linux kernel, isn't it? https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/lib/bootconfig.c?id=c99b17ac03994525092fd66bed14b4a0c82f0b4d#n9 I guess that other approaches should be considered for the desired software reuse in this system configuration area. Is there a need to map key and value combinations directly to files (and directories) for a more convenient data processing by user-space processes? Regards, Markus
