From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] rc.d script
Date: Mon, 22 Jul 2013 12:37:35 +0200 [thread overview]
Message-ID: <09bbd22f9849aa4c3dec5372e8c69ed2@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <5DDDC2AE1D40D045B973C3CAA4D4CCC74F2D13@HISCMAIL01.HeiLab.loc>
Am 2013-07-22 12:19, schrieb Henrik.Kraft@heidolph.de:
> as I have created scripts in /etc/rc.d for automatic start of
> programms (and settings) these are not executed on startup. I can't
> use systemd mechanism because if I use it our GUI application has no
> input from the touch panel. With (manual) start via /etc/rc.d script
> this works well.
>
> What used to be done to have those scripts executed on startup?
This very much depends on your startup method. In ptxdist menuconfig you
gi "Root Filesystem" ---> "init" ---> "init method".
We use busybox init which uses init scripts put to /etc/init.d/ and
where you have symbolic links in rc.d pointing to the scripts in
/etc/init.d -- At system boot if you have the default /etc/inittab the
script /etc/init.d/rcS is executed which calls `run-parts -a start
/etc/rc.d` by default. "run-parts" is part of busybox itself. That's how
it goes with busybox init. I hope this contains some hints for you where
to look.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-07-22 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 10:19 Henrik.Kraft
2013-07-22 10:25 ` Josef Holzmayr
2013-07-22 10:37 ` Henrik.Kraft
2013-07-22 10:37 ` Alexander Dahl [this message]
2013-07-22 10:57 ` Jürgen Beisert
2013-07-22 11:08 ` Henrik.Kraft
2013-07-22 12:05 ` Henrik.Kraft
2013-07-22 14:03 ` Jürgen Beisert
2013-07-22 15:44 ` Henrik.Kraft
2013-07-22 13:25 Henrik.Kraft
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=09bbd22f9849aa4c3dec5372e8c69ed2@idefix.lespocky.dyndns.org \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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