-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
On Saturday 27 October 2007, Ismael Luceno <[EMAIL PROTECTED]> wrote:
> Well, the problem here is that it's very expensive to stat/read a lot of
> small files in contrast to read only one file once, and it doesn't
> helps with compatibility...
Yes, it's true that it will slow down initng more than reading one big file.
However the file system solution just naturally provides us with a
hierarchy. This is very useful, just imagine nic configuration (I remember
the /etc/net project that accomplished a fairly complex configuration for a
large number of nics).
And, second, it just keeps syntax errors away.
I experimented with some config file formats. What "won" was the block-like
format we use in the ifiles, like
nic eth0 = {
config-style = static;
ip-address = 192.168.2.4;
ip-prefix = 24;
}
nic eth1 = {
config-style = dhcp;
}
> A better solution IMO, is to have a static script to config-file
> mapping [...]
What do you mean by this? Sorry, I don't understand.
What also came to my mind was some sort of meta-configuration. For example
with the net configuration, a little program could be used by the admin to
set up the ip configuration, and then it just generates an ifile from it.
Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFHP1Y8fkUtd7QNU/sRAnrgAJ9FZm19O9WM3SkcCJtcYrxwo4yGMwCeNV5X
njIEpEtNpSZlEPZo3z8RAWA=
=gcEn
-----END PGP SIGNATURE-----
--
_______________________________________________
Initng mailing list
[email protected]
http://jw.dyndns.org/mailman/listinfo/initng
