Date: Sun, 23 Feb 2014 09:33:05 +0100 From: Andreas Nilsson <andrnils@gmail.com> To: Scot Hetzel <swhetzel@gmail.com> Cc: =?ISO-8859-1?Q?Bruno_Lauz=E9?= <brunolauze@msn.com>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: libinit idea Message-ID: <CAPS9%2BSubCSfBc4NYsZfJCQ_7ce%2BcCDjFT-BTL6x=ynYuYD%2BwVA@mail.gmail.com> In-Reply-To: <CACdU%2Bf9KVc7EKcVAN2vtyO7UvC%2BDM=iMsiQBmRzmA%2BcU1ZL=gA@mail.gmail.com> References: <BLU179-W28221A0539478FDDF45ADDC6840@phx.gbl> <CACdU%2Bf9KVc7EKcVAN2vtyO7UvC%2BDM=iMsiQBmRzmA%2BcU1ZL=gA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 23, 2014 at 8:46 AM, Scot Hetzel <swhetzel@gmail.com> wrote: > On Sat, Feb 22, 2014 at 5:54 PM, Bruno Lauz=E9 <brunolauze@msn.com> wrote= : > > https://github.com/brunolauze/libnit > > > > I know there's really big debate about init system but here's my > tentative to propose a new model to replace rc. > > > > Let's call it libinit but the name as no significance for now. > > > > I started coding a library with the following architecture. > > > > the main idea is to rewrite rc in C language. > To me this seems like much work for no real gain. And it would make it that much harder to debug a misbehaving "script", in more than one way: * c is a lot longer than sh, ie sh expresses the logic that much more clearly. * to actually see the new "script" would require to have the source code installed, something far from everybody has. > > > > a utility called system would act a little bit like service command doe= s. > > > > a folder would contains libraries instead of scripts inside > [target]/etc/rc.d > > so we can add as many librairies a user desire and interlink the order > of each piece among all like in rc. > > > libraries don't belong in [target]/etc/rc.d, they would have to be in > {/usr,}/lib{exec,}/rc.d or ${PREFIX}/lib{exec,}/rc.d > > Imho, the replacement to init and rc-scripts I sometimes think about woul= d be to import SMF from opensolaris/illumos. There one can at least get the commands run and config used without looking at the source code. Best regards Andreas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPS9%2BSubCSfBc4NYsZfJCQ_7ce%2BcCDjFT-BTL6x=ynYuYD%2BwVA>