Hi,
My concern was being forward compatible with systemd and you have addressed
my concern.
Thank you.
On Sat, Mar 23, 2013 at 3:55 AM, Lennart Poettering
wrote:
> On Fri, 08.03.13 14:12, Umut Tezduyar (u...@tezduyar.com) wrote:
>
> > Hi,
> >
> > What would be the advantage of placing an early
On Fri, 08.03.13 14:12, Umut Tezduyar (u...@tezduyar.com) wrote:
> Hi,
>
> What would be the advantage of placing an early boot up script in between
> local-fs.target/sysinit.target OR in between
> sysinit.target/basic.target?
That's a very good question. This hopefully gives a bit of an explana
Hi,
I would like to bring my discussion back. Any help?
Thanks
On Fri, Mar 8, 2013 at 2:12 PM, Umut Tezduyar wrote:
> Hi,
>
> What would be the advantage of placing an early boot up script in between
> local-fs.target/sysinit.target OR in between sysinit.target/basic.target?
>
> I cannot deci
Maybe bandwith wasn't the best example :) But my question is still valid.
On Fri, Mar 8, 2013 at 2:18 PM, Reindl Harald wrote:
>
>
> Am 08.03.2013 14:12, schrieb Umut Tezduyar:
> > To summarize, where are users encouraged to place their early boot up
> initialization services (ex: setting up the
Am 08.03.2013 14:12, schrieb Umut Tezduyar:
> To summarize, where are users encouraged to place their early boot up
> initialization services (ex: setting up the
> bandwith on a NIC)?
[root@rh:~]$ systemctl status bandwidth.service
bandwidth.service - Traffic-Shaping
Loaded: loaded (
Hi,
What would be the advantage of placing an early boot up script in between
local-fs.target/sysinit.target OR in between sysinit.target/basic.target?
I cannot decide what should be the ordering for some early initialization
"oneshot" services I have in my embedded system. These services makes s
