On 20140304_160239, Raffaele Morelli wrote: > 2014-03-04 15:45 GMT+01:00 Steve Litt of Troubleshooters.Com < > litt...@gmail.com>: > > > On Tue, 4 Mar 2014 09:05:41 +0100 > > Raffaele Morelli <raffaele.more...@gmail.com> wrote: > > > > > > > > Lately I would add > > > > > > :0B > > > * .*(systemd) > > > $GARBAGE > > > > > > :0 > > > * ^Subject.*(systemd) > > > $GARBAGE > > > > I can't do that, because I really need to know about that stuff. When > > Jessie becomes stable, I'm going to try to work with systemd. But if > > that becomes problematic, I'll need a plan B. A lot of today's traffic > > was very informative stuff about system startup. > > > > IMHO you won't need a plan B, it's just another system service manager, > that said you can try systemd before Jessie release, it's in debian > Wheezy... > > /r
I switched to systemd under Wheezy a couple of weeks ago. I had a small problem convincing aptitude to stop switching back to the old way any time that I wanted to install packages from security.debian.org. After fixing that I have noticed no difference from the old way, whose name I have already forgotten. My hardware has a built in, intended, delay before start of boot, so I don't percieve that boot is faster. Maybe it is. I just can't see it in my particular set up. I am much more worried now about the world going nuclear before systemd gets a chance to prove its usefulness. Peace to all, I hope -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140304171544.gb9...@big.lan.gnu