Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Startup files numbering policy
Date: Wed, 22 May 2013 09:33:04 +0200	[thread overview]
Message-ID: <20130522093304.3b74f29e@skate> (raw)
In-Reply-To: <1386188598.1025471.1369174120221.JavaMail.root@advansee.com>

Dear Beno?t Th?baudeau,

On Wed, 22 May 2013 00:08:40 +0200 (CEST), Beno?t Th?baudeau wrote:

> Maybe. This is what I had done. I mostly wanted to know if you would add a
> mechanism for that, which you answered. E.g., PTXdist has a config option with a
> default value giving the file name to use for each startup script.

I'm not sure we want to have a config option for each and every init
script. Especially since with systemd, you have a unit file rather than
an init script, so we would have to handle this as well.

I think having a default sane numbering is good enough, since we allow
the users to customize whatever they want using post-build scripts.

Note that I'm not saying the current numbering is perfect, it could be
clarified, with a bit documentation saying "from number X to Y, it's
basic services that are not network dependent", "from Y to Z, it's this
type of services, etc.". I'm just talking about the general approach of
just having a default numbering, and leaving the rest of the
customization to post-build scripts.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-05-22  7:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1882993282.1023650.1369164262752.JavaMail.root@advansee.com>
2013-05-21 19:31 ` [Buildroot] Startup files numbering policy Benoît Thébaudeau
2013-05-21 20:17   ` Thomas Petazzoni
2013-05-21 21:10     ` Benoît Thébaudeau
2013-05-21 21:24       ` Thomas Petazzoni
2013-05-21 22:08         ` Benoît Thébaudeau
2013-05-22  7:33           ` Thomas Petazzoni [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=20130522093304.3b74f29e@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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