On Wed, 03.12.14 12:35, WaLyong Cho (walyong....@samsung.com) wrote: > On 12/03/2014 08:30 AM, Lennart Poettering wrote: > > On Sat, 15.11.14 15:42, WaLyong Cho (walyong....@samsung.com) wrote: > > > > Heya, > > > > The suggested way to run boot chart is by specifying > > init=/usr/lib/systemd/systemd-bootchart on the kernel cmdline. What's > > the rationale behind making this a service? I mean, if it is started > > as service it races against other services and might thus not be able > > track services run in early boot. Can you please elaborate on the > > rationale for this patch? > > > Yes, right. I'm also generate bootchart using kernel command line. But, > in some kind of bootloader, it can be hard to modify the kernel command > line. In our mobile phone, we do not allow to modify kernel command line > to protect from hacking. In this case, this service can be useful even > if some of processes can not be shown. But according to this service > dependency, I think this bootchart service will be activated quite ahead > of boot sequence. > And as you said, this will race against others. That why this should NOT > be enabled as default. But if someone want to get bootchart easily then > he can get bootchart after just enable this. And also I think this can > be useful to newbie. Isn't it?
Well, I hope a newbie into boot profiling reads the man page fist and then uses init= on the kernel cmdline, as suggested there. But anyway, looks useful enough, hence I merged this now, but added a comment to the header suggesting that init= on the kernel cmdline is the preferable way to use this tool. Thanks! Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel