On Friday 29 October 2004 09:37, Kenn Humborg wrote:
> > had a look in /etc/sysconfig to get a feel for the type of configuration
> > files used by the "network start/stop". ...and noticed that all files I
> > looked at are ".ini" style (aka "Key=Value"). Few questions arise:
>> They're not ".INI"-style. Windows' .INI files are broken into
> sections delimited by square bracketed names. For example
Yop, my mistake :) that's what I meant: key=val, no groups
>> > 1. Is this the generic case? The only place I remember seeing XML
> > used is the
> > fontconfig (and more recently, D-BUS).
>> I'm not sure if the /etc/sysconfig thing is a redhat-ism. I first
> saw it there.
But besides that, imho most config files in /etc are linear (not xml).
>> > 2. Besides the ability to include such linear files in scripts through ".
> > script", is there any other reason?
>> It's trivial to parse these files in shell scripts, because there is
> absolutely no parsing required. Just feed them to the shell and
> environment variables get set.
I understand the reasoning for shell processing, but I was wondering if there
are some serious security arguments for not using XML as config files for
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!