Project

General

Profile

Actions

Bug #85

closed

The init scripts are not being run because nothing runs them.

Added by Hammel over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
root file system
Target version:
Start date:
28 Feb 2011
Due date:
% Done:

100%

Estimated time:
Severity:
High

Description

There are multiple init scripts under /etc/init.d but they are not being run because none of the inittab run scripts runs that directory to run scripts.

This is easily fixed by adding the attached code to rc1:


Related issues

Blocks BeagleBox - Bug #76: Pango fonts must be setup at boot time.ClosedHammel28 Feb 2011

Actions
Actions #1

Updated by Hammel over 13 years ago

Added to rc1. Need to test with a rootfs rebuild to make sure it gets picked up and actually works.

Actions #2

Updated by Hammel over 13 years ago

The rc scripts are all wrong. They need to be simplified so that rcS just runs /etc/init.d/S* and that only rcS is called from inittab. Then the bits in /etc/init.d/volatile and /etc/init.d/rc1 can be migrated to proper init scripts (re: files starting with S).

So there should be:
S00dev - Setup /var/volatile if it doesn't exist and mount onto a tmpfs; create /lib/modules/`uname -r`/ if it doesn't exist; Migrate devices to a tmpfs
S01volatile - the new name of the volatile init script originally called from inittab
S02postvolatile - stuff to do after the volatile script completes; this allows easy merge of S01volatile with original Ubuntu volatile script later, if necessary.

Actions #3

Updated by Hammel over 13 years ago

Scripts implemented. Currently under test.

Actions

Also available in: Atom PDF