-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello list,
with many changes coming to InitNG, I'd like to bring something up that
bothered me for some time. It's InitNG's control channel. I once tried to
hack a little program to use /dev/initctl, and found that InitNG actually
does not only pass textual information, but also the complete layout incl
color codes.
I'd like to change that. :-) Some things came to my mind here, and I'd like
to hear your opinions on that.
1 - Simplify the protocol. Keep it the way it is, but mostly simplify it by
removing color codes and "layout". Create an API against it to allow other
programs to just be the client by including an InitNG header file and
linking against a library that provides a stable API for that matter.
2 - Use FUSE or others to create a /proc like file system. Services could be
directories in there, a simple "echo" would trigger actions just like we
know it from /proc and /sys.
My intention is to build a mostly InitNG-agnostic API that doesn't rely on
any internals. Just a clean, stable set of commands and well-defined return
values.
-- Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqIdaMACgkQhS0drJ3goJJb+QCfRBdZBz2G7W6ohsQvcL4F3v0d
7wkAn27X5MFuxTaXUMc9XUF2Ol/OhOHY
=YKKv
-----END PGP SIGNATURE-----
--
_______________________________________________
Initng mailing list
[email protected]
http://jw.dyndns.org/mailman/listinfo/initng
