Bug 3085 - Init scripts are not compatible with sysVinit (when busybox is not chosen)
Summary: Init scripts are not compatible with sysVinit (when busybox is not chosen)
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: 2009.11
Hardware: PC Linux
: P5 major
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-14 15:57 UTC by Bardon.j
Modified: 2011-02-02 19:59 UTC (History)
1 user (show)

See Also:
Host: x86_64-linux-gnu
Target: x86_64-custom-linux-gnu
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bardon.j 2011-01-14 15:57:23 UTC 
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.
Comment 1 Thomas Petazzoni 2011-01-14 16:53:34 UTC 
This has been fixed by http://git.buildroot.net/buildroot/commit/?id=7e2bf63080cc0011c84ee46ee2aba161569154c5

This commit was not part of Buildroot 2010.11, but will be part of Buildroot 2011.02, scheduled to be released end of next month.

The sysvinit inittab proposed is probably not perfect (for example it doesn't work well for halt/reboot), but at least it allows the system to boot properly. Feel free to suggest further improvements.