All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3085] New: Init scripts are not compatible with sysVinit (when busybox is not chosen)
Date: Fri, 14 Jan 2011 15:57:23 +0000 (UTC)	[thread overview]
Message-ID: <bug-3085-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=3085

           Summary: Init scripts are not compatible with sysVinit (when
                    busybox is not chosen)
           Product: buildroot
           Version: 2009.11
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: bardon.pro at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


When you don't use busybox but build a rootfs with standard System V init (with
the sysVinit package) /etc/inittab and all init scripts still remain for
Busybox (no runlevel supported, etc).

When busybox is not compiled and SysVinit chosen a compatible set of scripts
should be provided in /etc.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2011-01-14 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 15:57 bugzilla at busybox.net [this message]
2011-01-14 15:58 ` [Buildroot] [Bug 3085] Init scripts are not compatible with sysVinit (when busybox is not chosen) bugzilla at busybox.net
2011-01-14 16:53 ` bugzilla at busybox.net
2011-02-02 19:59 ` bugzilla at busybox.net

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=bug-3085-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.