Re: [systemd-devel] Ordering for early initialization services

2013-03-25 Thread Umut Tezduyar
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 lenn...@poettering.netwrote: On Fri, 08.03.13 14:12, Umut Tezduyar (u...@tezduyar.com) wrote: Hi, What would be the advantage of

Re: [systemd-devel] Ordering for early initialization services

2013-03-22 Thread Lennart Poettering
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

Re: [systemd-devel] Ordering for early initialization services

2013-03-19 Thread Umut Tezduyar
Hi, I would like to bring my discussion back. Any help? Thanks On Fri, Mar 8, 2013 at 2:12 PM, 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? I

Re: [systemd-devel] Ordering for early initialization services

2013-03-08 Thread Reindl Harald
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

Re: [systemd-devel] Ordering for early initialization services

2013-03-08 Thread Umut Tezduyar
Maybe bandwith wasn't the best example :) But my question is still valid. On Fri, Mar 8, 2013 at 2:18 PM, Reindl Harald h.rei...@thelounge.netwrote: Am 08.03.2013 14:12, schrieb Umut Tezduyar: To summarize, where are users encouraged to place their early boot up initialization services