| 1 |
On Aug 26, 2013 8:41 AM, "Mark David Dumlao" <madumlao@×××××.com> wrote: |
| 2 |
> |
| 3 |
> On Sun, Aug 25, 2013 at 12:54 PM, <meino.cramer@×××.de> wrote: |
| 4 |
> > Hi Mark, hi William, |
| 5 |
> > |
| 6 |
> > the script ds3231 in /etc/init.d is -- according to rc-update -- |
| 7 |
> > set as folows: |
| 8 |
> > |
| 9 |
> > ds3231 | boot |
| 10 |
> |
| 11 |
> Long and short of it, here's the boot order: |
| 12 |
> sysinit -> boot -> (single) -> default |
| 13 |
> |
| 14 |
> rc(8) tells me that sysinit is for bringing up system specific stuff |
| 15 |
> such as /dev, /proc, /sys. So it's appropriate for a special device |
| 16 |
> file such as yours, with the caveat that you want it up AFTER any |
| 17 |
> dependencies such as sysfs. |
| 18 |
> |
| 19 |
> Now how to do that is to make your script openrc compliant, so... |
| 20 |
> |
| 21 |
> > |
| 22 |
> > There is no corresponding file in /etc/conf.d since the script |
| 23 |
> > onlu consist of two commands (see previous posting). There is no |
| 24 |
> > initramfs. |
| 25 |
> |
| 26 |
> Since openrc is running your script, it will check /etc/conf.d/same-name |
| 27 |
> for any script with environment variables. Or you can put it in the init |
| 28 |
> script itself. Mind you, I don't know where to find documentation on |
| 29 |
> how openrc implements this, unlike, say, some controversial init system |
| 30 |
> on this list... |
| 31 |
> |
| 32 |
|
| 33 |
Just to add some info: |
| 34 |
|
| 35 |
To the best of my knowledge, scripts in init.d will source the relevant |
| 36 |
file in conf.d. So, whether or not an initscript requires a conf.d file |
| 37 |
totally depends on the initscript in question. |
| 38 |
|
| 39 |
Rgds, |
| 40 |
-- |
Archives