Getting a structure on the code is always good, more structure, more
easy to work with and more success to initng. :-)


I succeded booting initng with .s files yesterday now so it wont take
long until we kan start using it i hope.

Ismaell, one problem remains, if an service exits in setup section and
there is a service that needs this service failed, it will stay waitng
for deps to start, and not abort on dep_error, witch tends to lockup my
system boot process sometime.

This new script-system is awsome, i see som mutch possibilities that
other init-system just may dreem about that we can implent werry great i
think, i see a sort of beauty in whats comming.

Now when we make scripts mor "intelligent" we can move som logic from
initng, ismaell have allredy removed a lot of code that just was not
needed anymore.

Also the upstart guys will soom feel the suffer of not choosing a
plugin-based init-system, soon they will have to add hald/dbus/whatever
monitors to their init, and that static codebase will just grow bigger.

Sadly, i wont have time to work on initng anymore, i put a lot of effort
helping out in the easter weekend, and i will try help, or at least be
avaible @ #initng-freenode.org as mutch as i can.

This weekend i found a new tool, gobby that is a realtime multi-user
document editor, if a few people are want to write a manual together
while discussing it in realtime, making it just little more fun and fast
to write it together, sience writing the docs are a really boring job.

Keep up the good work everyone, im really glad to se that something is
really happening laely, and also how god you manage without me.

Jimmy Wennlund

tis 2007-04-10 klockan 23:29 -0300 skrev Ismael Luceno:
> I want to make some changes in the way the source files are organized,
> now svn looks like:
> 
> src/core
> src/libinitng
> 
> We should move anything that is only needed for the core from libinitng/
> to core/.
> 
> I also want to rename the functions, functions in core should be named
> something like icore_*, while functions in libinitng will remain as
> initng_*.
> 
> Also, imo, we should organize the code by functionality, for example
> fix_escapes() should be in src/libinitng/string/fix_escapes.c.
> 
> What do you think guys?
> 
> 

-- 
_______________________________________________
Initng mailing list
[email protected]
http://jw.dyndns.org/mailman/listinfo/initng

Reply via email to