Re: Standard configuration files

"Patrick W. Barnes" <[email protected]> Sat, 10 Jun 2006 22:28:19 -0500
Newsgroups gmane.linux.redhat.fedora.configuration
Message-ID <[email protected]>
--===============0512848205==
Content-Type: multipart/signed; boundary="nextPart1910517.YHrCSHryML";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1910517.YHrCSHryML
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 08 June 2006 19:02, "Pedro Bezunartea L=C3=B3pez"=20
<[email protected]> wrote:
> Hi!
>
> I've been working with Linux for a few years now and one of the things I
> like most about it is the possibility of configuring everything by
> modifying readable text files. This is good but if you need to configure
> several services you may ask yoursel: why are all the configuration files
> for all the services so different? couldn't we come out with a standard
> file format that all services, devices, etc would use? What do you think?
> Here some ideas to begin with:
> 1. It'd have to be based in XML-dtd. Two important reasons, first it's a
> widely used standard, and second it's readable enough... and I can think =
of
> another one: it can describe very complex models.
> 2. There are already some services that use this kind of configuration
> files: tomcat... there's a place to start.
>
> Any suggestions are welcomed,
>

=46irst, this thread is off-topic for this list:

http://fedoraproject.org/wiki/PostIsOffTopic

I'm going to guess you don't have a whole lot of experience developing=20
configuration systems in software applications.  When developing an=20
application, a lot of consideration must go into the configuration system t=
o=20
be used.  The developer will generally make a selection based upon their=20
needs, knowledge and available tools.  Sometimes, an XML solution might be=
=20
the wise choice, but there are also cases where nothing more than a flat-fi=
le=20
with "name=3Dvalue" pairs is necessary, cases where a more powerful databas=
e is=20
needed, and cases where some other structured format or scripting language=
=20
might be needed.  The number of factors that must be considered is=20
astronomical.  Making a choice for the wrong reasons can have catastrophic=
=20
consequences.  There is no one right way, and there won't be in the=20
foreseeable future.

=2D-=20
Patrick "The N-Man" Barnes
[email protected]

http://www.n-man.com/

LinkedIn:
http://www.linkedin.com/in/nman64

Have I been helpful?  Rate my assistance!
http://rate.affero.net/nman64/
=2D-=20


--nextPart1910517.YHrCSHryML
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQBEi43bdBoB7CmUB9gRAhs4AJ4n6P2XFbC6smDSiXnVC63YeXpd1QCdEkIS
37Nmd0PYaV9nEFq344zg5L4=
=z+PN
-----END PGP SIGNATURE-----

--nextPart1910517.YHrCSHryML--


--===============0512848205==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Fedora-config-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-config-list
--===============0512848205==--