public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?
Date: Mon, 26 Aug 2013 13:03:34 +0700	[thread overview]
Message-ID: <CAA2qdGXoJ=Acv3u=87JgsSf=V1m8wsyWRNP-bCfTM0QkfhDL2w@mail.gmail.com> (raw)
In-Reply-To: <CAG2nJkM38XbN9Qp45prOz_pwzFw44u3NJgG1rLC38nT04Kkx6A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]

On Aug 26, 2013 8:41 AM, "Mark David Dumlao" <madumlao@gmail.com> wrote:
>
> On Sun, Aug 25, 2013 at 12:54 PM,  <meino.cramer@gmx.de> wrote:
> > Hi Mark, hi William,
> >
> > the script ds3231 in /etc/init.d is -- according to rc-update --
> > set as folows:
> >
> >                ds3231 | boot
>
> Long and short of it, here's the boot order:
> sysinit -> boot -> (single) -> default
>
> rc(8) tells me that sysinit is for bringing up system specific stuff
> such as /dev, /proc, /sys. So it's appropriate for a special device
> file such as yours, with the caveat that you want it up AFTER any
> dependencies such as sysfs.
>
> Now how to do that is to make your script openrc compliant, so...
>
> >
> > There is no corresponding file in /etc/conf.d since the script
> > onlu consist of two commands (see previous posting). There is no
> > initramfs.
>
> Since openrc is running your script, it will check /etc/conf.d/same-name
> for any script with environment variables. Or you can put it in the init
> script itself. Mind you, I don't know where to find documentation on
> how openrc implements this, unlike, say, some controversial init system
> on this list...
>

Just to add some info:

To the best of my knowledge, scripts in init.d will source the relevant
file in conf.d. So, whether or not an initscript requires a conf.d file
totally depends on the initscript in question.

Rgds,
--

[-- Attachment #2: Type: text/html, Size: 1885 bytes --]

  reply	other threads:[~2013-08-26  6:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-25  4:04 [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how? meino.cramer
2013-08-25  4:18 ` Mark David Dumlao
2013-08-25  4:28   ` William Kenworthy
2013-08-25  4:54     ` meino.cramer
2013-08-26  1:40       ` Mark David Dumlao
2013-08-26  6:03         ` Pandu Poluan [this message]
2013-08-25  9:02 ` Paul Colquhoun
2013-08-25 10:35   ` meino.cramer
2013-08-25 11:41     ` Mick
2013-08-25 12:50       ` meino.cramer
2013-08-25 13:15         ` William Kenworthy
2013-08-25 15:24           ` meino.cramer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA2qdGXoJ=Acv3u=87JgsSf=V1m8wsyWRNP-bCfTM0QkfhDL2w@mail.gmail.com' \
    --to=pandu@poluan.info \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox