i think, we shouldn't form an opinion about who need a service essential for
startup/shutdown.
we should sort the services by there service.
db databases like postgres and mysql
web http-server like thttpd and ruby on rails
mail mail-services like fetchmail and postfix
net nertwork-provided services like iproute2, pump and ip6table
sys udev and sysctl
snd soundprovider like alsa and icecast
fs mountpoints and 9p
mod special on linux for loading modules
x X-only-related services like entrance and xdm
sec security like selinux
conf your idea with a conf-directory is good :)
short names and easy to find services.
by the way: one service per file.
example the hole file of /etc/initng/snd/alsa/mixer.j:
need fs/dev snd/alsa;
env asoundcfg "/etc/asound.state";
start = { ... [ the long script ] ... };
stop alsactl -f "${asoundcfg}" store;
this was the hole file (but without comments), there's no line, which sais,
that it's snd/alsa/mixer.
for wildcards, i've a second idea:
/etc/initng/mod/default.j:
start = modprobe "${NAME}";
that's all.
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)
--
_______________________________________________
Initng mailing list
[email protected]
http://jw.dyndns.org/mailman/listinfo/initng
