Ismael Luceno wrote:
Some modules are more widely used than others. While this doesn't mean
we will support ones more than others, it would be nice to separate
build-by-default modules from others.
This separation would allow to differentiate well-tested modules and
serve as a hint to developers about which modules need some love :).
The following modules are the candidates:
* dbus_event
* fmon
* history
* idleprobe
* initctl
* interactive
* ngcs
* nge
* reload
* sysreq
The modules could be moved to extras/, or other directory...
I would like to hear other opinions before taking any decision :).
Nice idea. I personally have a list of modules that I include in every
config (I used (yet) initng only on embedded devices):
libalso.so libcritical.so libngc4.so libsimplelauncher.so
libbashlaunch.so libdaemon_clean.so libprovide.so libstcmd.so
libchdir.so libdaemon.so libreload.so libstdout.so
libchroot.so libenvparser.so librlparser.so libsuid.so
libconflict.so libiparser.so librunlevel.so libunneeded.so
libcpout.so liblast.so libservice.so
I think that's a minimal configuration;)
Also it will be cool if you remove some ugly colouring (i don't mean
all, i mean only excess) from cpout plugin & ngc, and also adapt cpout
to narrower screens (mine is 29 character wide).
--
WBR, Peter Zotov
--
_______________________________________________
Initng mailing list
[email protected]
http://jw.dyndns.org/mailman/listinfo/initng
