On 02/12/2013 01:05 AM, Matt Burgess wrote: > On Tue, 2013-02-12 at 00:27 +0100, Armin K. wrote: > >> Still no one replied about the patch :( > > OK, I guess I just don't quite get it :-) > > I see that it allows one to configure whether or not stuff is logged > to /run/var/bootlog. I think the comments in your original email mean > that: > > 1) Logging to /run/var/bootlog is pointless in the LFS-systemd branch > because systemd logs everything to the journal. In which case, this new > setting should be set to 0 by default (probably via a sed in whichever > section ends up installing init-functions in that branch) > > 2) Logging to /run/var/bootlog is useful in LFS trunk/sysvinit, > therefore it should be set to 1 by default (i.e. in init-functions as > supplied by lfs-bootscripts). > > So, in short, I'm not sure that the patch is necessary, assuming I've > understood the rationale correctly. We'll be supplying init-functions > outside of the main lfs-bootscripts package in the systemd branch, I > think, and therefore can rip the logging out of that file at that point, > I think. For the copy of init-functions in lfs-bootscripts, I don't > know why anyone would not want stuff logged, unless they want the added > debugging headaches when things go wrong :-) > > Thanks for any clarification :=) > > Matt. > >
Well, I am trying to keep LFS and LFS Systemd as close as possible - that's all. In that case, we would just need to change ENABLE_LOG=0 in init-functioins for systemd branch. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
