On 01/11/2015 20:57, Pierre Labastie wrote: > On 01/11/2015 12:24, EyesIs Mine wrote: >
>>> - There is presently no way to know which bootscript to reinstall when the >>> bootscript tarball is modified. Having a file of installed bootscripts could >>> help (or maybe use the listing of "/etc/init.d"). >> >> systemd says hi. Also, this would mean overwriting modified bootscripts, >> which would be bad. Maybe a solution could be worked with sha256sums or >> something along those lines. >> > > Sorry about systemd... Actually, I have to check, but it seems the current > tool is unable to install systemd units, is it? Maybe the first task would be > to make the tool compatible with systemd. Thanks for the heads up. Managing > new versions of the scripts/units is tougher, and I might come to that later. > I checked, and indeed the tool is able to install systemd units, thanks to the systemd devs, who kept the same id's as the sysv book for the systemd-unit page. I've tried to think about how to install new versions, specially respective to modified bootscripts/units, and I am not sure I want to pursue... Pierre -- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
