On 16/06/15 12:27, Arnt Gulbrandsen wrote:
Come to think of it... If you read init.d anyway, why not read it at
boot time if a new directive is set, e.g. apply-lsb-instructions=true?
Arnt
Thanks a lot Arnt,
Please do not assume that I am a hardcore programmer or a hardcore
UNIX/Linux admin. I just started all of these at almost the same time
when Devuan was born. I would not be so determined to do all of these if
systemd did not ruin my PC and Linux ecosystem in general.
So I am not really sure what you meant by "reading the new directives at
boot time". Which directive would that be, where is it located and which
package provides that?
I would imagine that there is no need for epoch to do anything else at
boot time, a part from doing the normal init process. However, its
epoch.conf needs to be automatically updated with the parameters of the
daemons/services when their packages are being installed or removed.
This is the job of the separate program or script outside epoch but
provided by epoch package.
Perhaps, there would be other functions that need to be added into epoch
package later on. I think (or I hope) I got enough for the base line to
start reading (a lot of things and trying) and develop Debian build
scripts for epoch. But I am open to any feedbacks on what I am doing.
Cheers,
Anto
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
