Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-12 Thread Armin K.
On 02/12/2013 10:24 PM, Matt Burgess wrote: > On Tue, 2013-02-12 at 22:20 +0100, Armin K. wrote: > >> Hm, am I missing something or D-Bus isn't there? It's required iirc ... >> You can't run systemd without it. > > Err, whoops :-) I told you I hadn't run a build yet, and there's the > proof! If y

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-12 Thread Matt Burgess
On Tue, 2013-02-12 at 22:20 +0100, Armin K. wrote: > Hm, am I missing something or D-Bus isn't there? It's required iirc ... > You can't run systemd without it. Err, whoops :-) I told you I hadn't run a build yet, and there's the proof! If you give me an hour or so, I'll add it in. Regards,

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-12 Thread Armin K.
On 02/12/2013 10:06 PM, Matt Burgess wrote: > On Tue, 2013-02-12 at 17:20 +0100, Armin K. wrote: > >> Alright, no problem. I'll do the polishing thing then. > > Lovely, thanks, that branch is all yours now :-) If there's anything > you want a hand with, feel free to shout! > > Regards, > > Matt. >

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-12 Thread Matt Burgess
On Tue, 2013-02-12 at 17:20 +0100, Armin K. wrote: > Alright, no problem. I'll do the polishing thing then. Lovely, thanks, that branch is all yours now :-) If there's anything you want a hand with, feel free to shout! Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FA

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-12 Thread Armin K.
On 02/12/2013 11:26 AM, Matthew Burgess wrote: > On Tue, 12 Feb 2013 01:48:28 +0100, "Armin K." wrote: > >> Also, I just merged expat into systemd branch, but there is no commit >> message. I am subscribed to lfs-book. What am I doing wrong? > > Bruce already covered the commit message issue. I'v

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-12 Thread Matthew Burgess
On Tue, 12 Feb 2013 01:48:28 +0100, "Armin K." wrote: > Also, I just merged expat into systemd branch, but there is no commit > message. I am subscribed to lfs-book. What am I doing wrong? Bruce already covered the commit message issue. I've actually got all of systemd and its dependencies in m

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-11 Thread Bruce Dubbs
Armin K. wrote: > Also, I just merged expat into systemd branch, but there is no commit > message. I am subscribed to lfs-book. What am I doing wrong? I doubt you are doing anything wrong. The changes are in svn, but I don't see any message in mailman (lfs-book) about invalid posters. However,

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-11 Thread Armin K.
On 02/12/2013 01:46 AM, Armin K. wrote: > On 02/12/2013 01:42 AM, Matt Burgess wrote: >> On Tue, 2013-02-12 at 01:10 +0100, Armin K. wrote: >> >>> 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

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-11 Thread Armin K.
On 02/12/2013 01:42 AM, Matt Burgess wrote: > On Tue, 2013-02-12 at 01:10 +0100, Armin K. wrote: > >> 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. > > OK then, at

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-11 Thread Matt Burgess
On Tue, 2013-02-12 at 01:10 +0100, Armin K. wrote: > 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. OK then, at least I understood it correctly :-) The patch is

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-11 Thread Armin K.
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 co

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-11 Thread Matt Burgess
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

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-11 Thread Armin K.
On 02/12/2013 12:15 AM, Matt Burgess wrote: > On Mon, 2013-02-11 at 23:50 +0100, Armin K. wrote: >> On 02/11/2013 01:22 AM, Armin K. wrote: >>> Not useful for systemd since it logs anything to journal. Still enable >>> it by default on LFS. >>> >>> I guess we would want to use this for lfs/systemd

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-11 Thread Matt Burgess
On Mon, 2013-02-11 at 23:50 +0100, Armin K. wrote: > On 02/11/2013 01:22 AM, Armin K. wrote: > > Not useful for systemd since it logs anything to journal. Still enable > > it by default on LFS. > > > > I guess we would want to use this for lfs/systemd branch, but we need > > some kind of new bootsc

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-11 Thread Armin K.
On 02/11/2013 01:22 AM, Armin K. wrote: > Not useful for systemd since it logs anything to journal. Still enable > it by default on LFS. > > I guess we would want to use this for lfs/systemd branch, but we need > some kind of new bootscripts package which will include init-functions > (needed by al

Re: [lfs-dev] Allow override for logging to /run/var/bootlog

2013-02-11 Thread Matt Burgess
On Mon, 2013-02-11 at 01:22 +0100, Armin K. wrote: > Matt, since you removed Sysvinit package from LFS Systemd branch, I > wonder if we should add it back, but only make it install few utils. All > distros that use Systemd still ship package as "systemd-utils" which > contains the following uti