From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] bbinit default order
Date: Sat, 24 Mar 2012 10:27:25 +0100 [thread overview]
Message-ID: <20120324092725.GB24724@pengutronix.de> (raw)
In-Reply-To: <1b945cf0160b9c7530eb808b6712612d@idefix.lespocky.dyndns.org>
On Wed, Mar 21, 2012 at 01:24:47PM +0100, Alexander Dahl wrote:
> I'm currently experimenting with systemd. While switching between
> busybox init and systemd I got some default values for the symlinks
> created in /etc/rc.d in my ptxconfig. With the defaults I got some
> conflicts, e.g. there's S26networking and S16dropbear which leads to
> dropbear not starting because network is not ready. I would like to have
> this fixed, but I'm not sure how to reorder these. In my project with
> just a few packages I could do this by my own. For fixing the default
> values shipped with ptxdist according to grep this would be 48 packages.
> Is there any ressource for these numbers or did each package author make
> them up by herself?
There are no real rules here. It's probably copy-paste in most cases. If
you want to clean this up, I suggest you pick on number N (e.g. 20) for all
network providing services (networking, connman, ...) and move those that
need it to N+10 or something like that. Same thing for any other obvious
dependencies. Although I didn't see any besides keeping udev etc. at the
beginning.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-03-24 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 12:24 Alexander Dahl
2012-03-24 9:27 ` Michael Olbrich [this message]
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=20120324092725.GB24724@pengutronix.de \
--to=m.olbrich@pengutronix.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