-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jens Persson escribió: > Oh, come on. Parsing those textfiles takes just a few milliseconds. They > are very small too so no need to switch to a binary format. About how to > sort .i files I guess that could be done in many ways but maybe we could > start with taking a vote on if we should split up system in two directories? > > And on a related note, I asked a while back if there will be stable > versions but it was turned down then. But sooner or later there should > be stable versions, otherwise Initng will always just be seen upon as a > "hacking playground". Odd numbers could be devel versions and equal > could be stable. IE if we start changing the API that should be done in > a 0.7.x devel series, which will eventually end up in a 0.8.x stable > series. And new development will go into 0.9.x and so forth.
We can not guarantee that there will be no api changes. What we need to do is keep bugfixing 0.6.x after 0.6.x+1 release, until it's tested for a couple of weeks. So we will be releasing 0.6.x.y's until 0.6.x+1 is considered stable :). Also, we should standarize the version bumping process. What i propose is: o.o.x minor or no api changes (no breakage). o.x.o api changes that break things (API_VERSION bump). x.o.o core rewrites, and the like. Well, based on this, the current release should be called 0.7.0 :P. > > greets > > Denis Knauf wrote: >> the conf-files we can base on gdbm or like that. faster to use. >> second: our i-files are text-based, it's very slow to parse it. we should >> use >> gdbm or a special binary-format with very fast parsing issues. >> >> i can't code it. i only have many ideas for initng. >> >> Am Donnerstag, 8. Februar 2007 03:44 schrieb Eric MSP Veith: >> >>> I agree with you, the net/ folder perfectly fits into system/, as Unix >>> boxes are network boxes anyway. :-) >>> >>> Once we've tied the system/ folder, we should change the names/pourposes of >>> the services in there as little as possible while only adjusting/tweaking >>> the contents of the files. I.e. people should trust that system/mountfs >>> stays there, is not renamed and it's pourpose stays the same, only the code >>> gets bugfixed and tuned. >>> >>> So we get: >>> >>> daemon/ only for daemons, >>> system/ services essential for system startup and scripts responsible >>> for establishing, maintaining and closing network connections >>> services/ place for services that aren't essential for system bootup, >>> i.e. "the rest", >>> runlevel/ runlevels, >>> config/ initng specific configuration files (for configuring >>> daemons/services, as /etc/sysconfig or /etc/conf.d do) >>> > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFFy7Zb/mxY0+yOXJoRAgfqAJsFgyMpKhJZUe0kkMQVhn6iBmEVqACgz8v5 Owyw3iWKvf/J9hkseXgitLo= =JIsR -----END PGP SIGNATURE----- -- _______________________________________________ Initng mailing list [email protected] http://jw.dyndns.org/mailman/listinfo/initng
