summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/initscripts
Commit message (Collapse)AuthorAgeFilesLines
* initscripts: Fix regression for requiring /bin/bashJason Wessel2015-08-101-2/+2
| | | | | | | | | | | | | | | | | | | It is not possible to create a rootfs with only busybox + initscipts. This is a result of a regression from commit a4b53872a8a9a2743299acbff015f7f2750a69d6 (initscripts: add /sbin/sushell for systemd service debug-shell). The /sbin/sushell should just use /bin/sh else you end up with a problem when creating the end image with a failed smart transaction shown below: ERROR: Unable to install packages. Command '/proj/bitbake_build/tmp/sysroots/x86_64-linux/usr/bin/smart --quiet --data-dir=/proj/bitbake_build/tmp/work/qemuarma9-wrs-linux-gnueabi/wrlinux-image-glibc-small/1.0-r1/rootfs/var/lib/smart install -y dropbear@armv7at2_vfp hac@armv7at2_vfp run-postinsts@all kernel-modules@qemuarma9 packagegroup-core-boot@qemuarma9' returned 1: error: Can't install initscripts-1.0-r155.0@armv7at2_vfp: no package provides /bin/bash (From OE-Core rev: 4917e36a77bd6821b45db52caa43939d344d92f6) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: urandom: respect ${localstatedir} instead of hardcoding /varAndré Draszik2015-07-311-1/+2
| | | | | | | (From OE-Core rev: 5f3f4196988675e9be5aea8eac56687641b90c10) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: add /sbin/sushell for systemd service debug-shellKai Kang2015-07-092-1/+14
| | | | | | | | | | | | | | | | | Add file /sbin/sushell for systemd service debug-shell which starts with /bin/sushell when SELinux is enabled. Copy and add sushell file from Fedora 22. Add runtime dependency bash as well when systemd is enabled to eliminate QA warning: WARNING: QA Issue: /sbin/sushell_initscripts contained in package initscripts requires /bin/bash, but no providers found in its RDEPENDS [file-rdeps] (From OE-Core rev: a4b53872a8a9a2743299acbff015f7f2750a69d6) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: Remove /etc/volatile.cache on upgradeBryan Evenson2015-04-201-0/+5
| | | | | | | | | | | | | | | | | /etc/volatile.cache is a cached copy of a script (which is generated by /etc/init.d/populate-volatile.sh) that generates the volatile filesystem directories. Since volatile.cache is a generated file, it is not necessarily changed if populate-volatile.sh is updated. As a result, the stale script can add/remove the wrong directories on the next system boot. If initscripts is being upgraded, make sure volatile.cache gets deleted. (From OE-Core rev: 317269b4a5c698e30b87bd597b436283512cbde9) Signed-off-by: Bryan Evenson <bevenson@melinkcorp.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: set proper S valuePetter Mabäcker2015-01-231-0/+2
| | | | | | | | | | | | | | After removal of auto-creating S we must ensure that all recipes are using a proper value for S. Fix all recipes that only need to set S equals to WORKDIR. [YOCTO #5627] (From OE-Core rev: 9d220b1bfe4589736604dd5a7129e3699377d830) Signed-off-by: Petter Mabäcker <petter@technux.se> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: avoid overwritting editable files during package updatingJian Liu2014-12-031-0/+2
| | | | | | | | | | | | | | | Use CONFFILES to mark editable files as such, /etc/init.d/checkroot.sh If there is no %config micro before the file name in the spec file, this file will be overwritten after updating package. This will make our settings lost. (From OE-Core rev: a265af666a80298ccca0eb80d6f15ca3d4be8b57) Signed-off-by: Jian Liu <jian.liu@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: mask several init scriptsChen Qi2014-09-031-0/+4
| | | | | | | | | | | We now support executing scripts under /etc/rcS.d. So we need to mask several more init scripts here to prevent them from running at boot time. (From OE-Core rev: c8f9527f18e5dd813c0330ba409875d34c36f6ab) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: fix bashism in bootmisc.shBen Shelton2014-07-231-1/+5
| | | | | | | | | | | | | | | | | | | | In the commit 'initscripts: save /etc/timestamp with seconds accuracy', a bashism was introduced in the bootmisc.sh script in the code to set the current date from the stored value in /etc/timestamp. This causes that operation to fail with the following message when /bin/sh is not bash: /etc/init.d/rc: /etc/rcS.d/S55bootmisc.sh: line 73: syntax error: bad substitution Fixed by using pattern matching removal rather than bash-specific substring expansion. [YOCTO #6566] (From OE-Core rev: c8a451adc71e4ce9ab963f61d7830c2d75aaffca) Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: Add support for /etc/default/urandomRichard Tollerton2014-07-191-0/+1
| | | | | | | | | | | | Source /etc/default/urandom if present. This allows the rootfs to remain read-only while enabling the user to override the location of the random seed file. (From OE-Core rev: 415e1a4ac8120b28118671698459b098c965a4f6) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: make hostname.sh coreutils-compatibleRichard Tollerton2014-07-191-1/+1
| | | | | | | | | | | inetutils and busybox hostname utils support `hostname -F`; coreutils hostname doesn't. So just use `cat` instead. (From OE-Core rev: acb8674e498468088d867ffae9a458caa08d95d5) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: Use current date as an additional source of entropyKen Sharp2014-07-191-6/+5
| | | | | | | | | | | If the seed file is empty or does not exist, the date is an extremely poor backup source of entropy, but it is better than nothing. (From OE-Core rev: 0a41a7c20316c7d3330233a624d8cf20ea5a81ae) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: parametrize random seed file locationRichard Tollerton2014-07-191-5/+8
| | | | | | | | | | | | Currently, the random seed file location is hardcoded to /var/lib/urandom/random-seed. Refactor it to a parameter (RANDOM_SEED_FILE) so the file location is defined in only one place. (From OE-Core rev: 558ba23cfdd60bf64b9214460a2772be70079796) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: save /etc/timestamp with seconds accuracyBlair Elliott2014-07-192-3/+4
| | | | | | | | | | | | Currently, /etc/timestamp is saved with minutes accuracy. To increase the accuracy, modify the save-rtc.sh and bootmisc.sh scripts to save and read /etc/timestamp respectively with seconds accuracy. (From OE-Core rev: 8fed53e4e72230c61f23cb36eda36c228aede1e0) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: bootmisc.sh: Make sysctl -p honor VERBOSERichard Tollerton2014-07-191-1/+6
| | | | | | | | | | busybox sysctl may lack the "-q" setting, so simulate it with redirects. (From OE-Core rev: 5672b5188557b940340bdc3e6a3ac30835b829fb) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: update populate-volatile.shKai Kang2014-06-241-4/+6
| | | | | | | | | | | | | | | | | | If a partition such as /tmp mounted on a volatile directory which create by script populate-volatile.sh from initscripts, it will show errors. In /var/log/boot, error message: Thu Jun 19 05:39:09 2014: bootlogd. Thu Jun 19 05:39:10 2014: rm: cannot remove '/tmp': Device or resource busy Check volatile directories and if it is be mounted then don't force make it as a link. (From OE-Core rev: cc4b0936c7a6a1563dc88d62d8c9020791eaa446) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: avoid pipe with sedMatthieu Crapet2014-05-081-2/+2
| | | | | | | | | | | | | | | Small optimisation in /etc/init.d/populate-volatile.sh. Replace: cat <file> | sed -e xxx By: sed -e xxx <file> (From OE-Core rev: c91739cd08ed5451a0927586a14db54c4c328ad7) Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: Fix PR reversalRichard Purdie2014-04-251-1/+1
| | | | | | (From OE-Core rev: 343f1c49ed223cd188287d4815f9dd956376c94d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Globally replace 'base_contains' calls with 'bb.utils.contains'Otavio Salvador2014-04-251-2/+2
| | | | | | | | | | | The base_contains is kept as a compatibility method and we ought to not use it in OE-Core so we can remove it from base metadata in future. (From OE-Core rev: d83b16dbf0862be387f84228710cb165c6d2b03b) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* PR bumps to remove PRINC use in meta-openpliMike Looijmans2014-04-241-1/+1
| | | | | | | | | Resolves warnings of this kind in the OpenPLi layer: WARNING: Use of PRINC * was detected in the recipe * (From OE-Core rev: 5ffb38d6ace7faae839c8cac7327b5b1c2daae1a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: bump PRsMartin Jansa2014-03-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * resolves following warnings: WARNING: Use of PRINC 17 was detected in the recipe meta-openembedded/meta-systemd/recipes-core/systemd/systemd-machine-units_1.0.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe meta-openembedded/meta-gpe/recipes-support/fbreader/fbreader_0.12.10.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe meta-openembedded/meta-gpe/recipes-support/fbreader/fbreader_git.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe meta-openembedded/meta-multimedia/recipes-multimedia/sox/sox_14.4.0.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe meta-openembedded/meta-oe/recipes-multimedia/mplayer/mplayer-common.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe meta-smartphone/meta-android/recipes-bsp/chroot-script/chroot-script_1.0.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-connectivity/avahi/avahi-ui_0.6.31.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-connectivity/bind/bind_9.8.1.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-core/systemd/systemd-serialgetty.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-extended/screen/screen_4.0.3.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-extended/shadow/shadow-securetty_4.1.4.3.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-extended/shadow/shadow_4.1.4.3.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-graphics/packagegroups/packagegroup-core-x11-xserver.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-kernel/modutils-initscripts/modutils-initscripts.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.25.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-support/libcap/libcap_2.22.bb (or one of its .bbappends) WARNING: Use of PRINC 11 was detected in the recipe openembedded-core/meta/recipes-bsp/keymaps/keymaps_1.0.bb (or one of its .bbappends) WARNING: Use of PRINC 11 was detected in the recipe openembedded-core/meta/recipes-core/systemd/systemd-compat-units.bb (or one of its .bbappends) WARNING: Use of PRINC 12 was detected in the recipe openembedded-core/meta/recipes-core/initscripts/initscripts_1.0.bb (or one of its .bbappends) WARNING: Use of PRINC 13 was detected in the recipe openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends) WARNING: Use of PRINC 2 was detected in the recipe meta-openembedded/meta-oe/recipes-navigation/navit/navit_svn.bb (or one of its .bbappends) WARNING: Use of PRINC 2 was detected in the recipe meta-openembedded/meta-oe/recipes-support/lvm2/lvm2_2.02.97.bb (or one of its .bbappends) WARNING: Use of PRINC 2 was detected in the recipe openembedded-core/meta/recipes-connectivity/portmap/portmap_6.0.bb (or one of its .bbappends) WARNING: Use of PRINC 2 was detected in the recipe openembedded-core/meta/recipes-extended/pam/libpam_1.1.6.bb (or one of its .bbappends) WARNING: Use of PRINC 2 was detected in the recipe openembedded-core/meta/recipes-graphics/packagegroups/packagegroup-core-x11.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe meta-openembedded/meta-efl/recipes-efl/efl/entrance_svn.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe meta-openembedded/meta-oe/recipes-multimedia/mplayer/mplayer2_git.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe openembedded-core/meta/recipes-bsp/formfactor/formfactor_0.0.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe openembedded-core/meta/recipes-connectivity/avahi/avahi_0.6.31.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe openembedded-core/meta/recipes-connectivity/dhcp/dhcp_4.2.5-P1.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe openembedded-core/meta/recipes-core/init-ifupdown/init-ifupdown_1.0.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe openembedded-core/meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb (or one of its .bbappends) WARNING: Use of PRINC 5 was detected in the recipe meta-openembedded/meta-oe/recipes-core/meta/distro-feed-configs.bb (or one of its .bbappends) WARNING: Use of PRINC 5 was detected in the recipe openembedded-core/meta/recipes-connectivity/bluez/bluez4_4.101.bb (or one of its .bbappends) WARNING: Use of PRINC 6 was detected in the recipe openembedded-core/meta/recipes-core/packagegroups/packagegroup-base.bb (or one of its .bbappends) WARNING: Use of PRINC 6 was detected in the recipe openembedded-core/meta/recipes-core/packagegroups/packagegroup-core-boot.bb (or one of its .bbappends) WARNING: Use of PRINC 6 was detected in the recipe openembedded-core/meta/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bb (or one of its .bbappends) WARNING: Use of PRINC 7 was detected in the recipe meta-openembedded/meta-oe/recipes-navigation/gpsd/gpsd_3.7.bb (or one of its .bbappends) WARNING: Use of PRINC 7 was detected in the recipe openembedded-core/meta/recipes-core/udev/udev-extraconf_1.0.bb (or one of its .bbappends) (From OE-Core rev: c6825ec6e92e20bb64a051d1576f363c16e98d68) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: fix syntax error in postinstsChen Qi2014-02-131-1/+0
| | | | | | | | | Fix syntax error in pkg_postinst of initscripts. (From OE-Core rev: 8240975b937197aee5ab1d651997fe500e8bbd91) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: mask initscripts from systemdRoss Burton2014-02-111-0/+25
| | | | | | | | | | | Many of the init scripts in here will do nasty things if systemd decides to run them. Mask the obviously bad ones so that systemd won't attempt to invoke them if initscripts is installed with systemd. (From OE-Core rev: 844f897710dfee9c59599d09b5c8c906e0d70ac0) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: define failure/success/warning/pass functionsRoy Li2014-01-281-0/+31
| | | | | | | | | | | define failure/success/warning/pass functions, some packages' initscript need them, and /etc/core-lsb/lsb_log_message from lsb needs them too. (From OE-Core rev: b78154c4a52b5a198e90bca8f83990fe9251fb72) Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: split the functions script into a separate packageChen Qi2014-01-061-2/+6
| | | | | | | | | | | | | | | | | | | | | Many SysV init scripts need the /etc/init.d/functions script. But this script is part of the initscripts package. As a result, the initscripts package should always be installed into the system to avoid errors when starting daemons. However, it makes no sense to install the initscripts package into a systemd based image, because what the init scripts provide has already been provided by the systemd. On the other hand, the functions script might be still needed in a systemd based image because other init scripts such as distcc might need it. The above situation leads to a natural separation of the functions script from the initscripts package. And this patch does so. It separates the functions script into initscripts-functions packages. (From OE-Core rev: 736dd8380f41d6ff1d3d0e4fe33cc01e2e873ef6) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: remove erroneous call to /etc/default/rcS in mountnfs.shRoss Burton2013-11-241-2/+0
| | | | | | | | | | This doesn't exist when using systemd as it's part of the sysvinit package, and this script doesn't need it. (From OE-Core rev: 426a22bb67c7823ee733f8c2bd85421b785c3631) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: add missing dmesg.sh to run-level SHans Beckerus2013-11-201-1/+3
| | | | | | | | | | | | In commit faa8cc6c2a582a32c695f3f2b0d45b6892c769fd dmesg.sh was added to the set of init.d scripts. But the script was never put in any run-level. This patch will add dmesg.sh to run-level S. (From OE-Core rev: 7d2767d4e27c6d0eaa56f3e126df56e65a5364c9) Signed-off-by: Hans Beckerus <hans.beckerus AT gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysvinit: fix problem in switching runlevelsChen Qi2013-11-201-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Previously, if we switch to runlevel 1 and then switch back to runlevel 5, the network interface will be brought down and the NFS service will not be restarted correctly. The problem is that the networking and rpcbind services are brought down in runlevel 1 but not brought up in runlevel 5. This patch fixes the above problem. It's based on the assumption that in sysvinit-based system, runlevel 1 does not have networking support. This patch adjusts some init script parameters used by update-rc.d. It makes sure that networking starts before rpcbind which in turn starts before mountnfs.sh. When switching to runlevel 0, 1 and 6, the umountnfs.sh is run first before stopping rpcbind service, and the network is brought down afterwards. [YOCTO #5513] (From OE-Core rev: f12e1291b51ba6692b6809570d6a9b73c70a7fe9) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysvinit: adjust boot sequence and remove hack from udevChen Qi2013-11-081-1/+1
| | | | | | | | | | | | | | | | | | | | | Adjust the boot sequence in sysvinit based systems. The mountall.sh (mounting the local file system) needs to be started before udev and bootlogd. This patch makes mountall.sh start before udev and removes the hack of mounting tmpfs in the udev init script. This patch also adds some comments to the udev init script to make it clear why we create the '/var/volatile/tmp' directory. [YOCTO #5273] (From OE-Core rev: f6a9df6b7cd411b52e71022b8f7bf8bda6395649) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: insure checkroot.sh runs before anything writing to the fileJeffrey C Honig2013-10-181-1/+1
| | | | | | | | | | | | | | | If bootlogd was configured to write to a log file on the root file system, the checkroot.sh was not able to change the rootfs to read-only because bootlogd was started earlier and had a file descriptor open. Lowering the order of checkroot.sh ensures that the volatile filesystem is set up before anything writes to it. (From OE-Core rev: 13c9bc143f6861517970dafdc7e7a45740d0933d) Signed-off-by: Jeffrey C Honig <jeffrey.honig@windriver.com> Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: filter out empty lines from volatiles in check_requirements()Ming Liu2013-09-101-2/+2
| | | | | | | | | | So far the rules of check_requirements() is too strict to lead mismatch when empty lines exist in volatiles. (From OE-Core rev: 71ab9ee58b0ba5e3f5cbf403d1b8fb79fc7f5ed1) Signed-off-by: Ming Liu <ming.liu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* read-only-rootfs-hook.sh: check before bind mounting /var/libChen Qi2013-08-261-4/+29
| | | | | | | | | | | | | | | | It's possible that /var/lib is on a separate writable partition. In such situation, we should not bind mount /var/lib with tmpfs, becasue it's already writable. This patch fixes this problem by checking whether /var/lib is already on a writable partition. [YOCTO #4888] (From OE-Core rev: 86ac10995fd08226f82d87e23fda5d4898c3190f) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* checkroot.sh: check for conflicting configurationsChen Qi2013-08-261-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In our current boot scripts, two ways are used to determine whether the rootfs is read-only or not. One by checking the READ_ONLY_ROOTFS value in /etc/default/rcS, the other by checking the /etc/fstab entry. >From a normal Linux user's point of view, the way of checking the /etc/fstab entry is preferred. However, as there are several boot scripts that need to know whether rootfs is read-only or not, checking /etc/fstab in each script brings too much overhead. Thus, these boot scripts use the READ_ONLY_ROOTFS value in /etc/default/rcS. In normal use cases, there would be no problem, as both /etc/default/rcS and the /etc/fstab are modified at rootfs time. However, if the user changes the mount option for rootfs in /etc/fstab to read-write, and he/she forgets to change the value in /etc/default/rcS, there would be unexpected results. For example, the udev-cache would still be disabled. So at a minimal, a check for conflicting configurations between /etc/fstab and /etc/default/rcS should be added in checkroot.sh so that there would be reasonable warnings if users have configured the system in a non-consistent way. [YOCTO #4880] (From OE-Core rev: 1565a0c5a3f245703e280ca90cf11d3f9374788a) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: remove obsolete device_table.txtChen Qi2013-08-202-199/+0
| | | | | | | | | | | | | | | | device_table.txt was once used by an init script named 'devices' to create the basic files under /dev. However, it's no longer used now. The devices init script has been removed, and makedevs command has been disabled by default in busybox. Besides, considering the device managers and devtmpfs filesystem, this file is not likely to be used again. So we remove it. (From OE-Core rev: cc3842255ade0ad6fb312f06f5e5e1edd9767c94) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate-volatile.sh: use 'cp -a' to avoid potential problemChen Qi2013-08-161-1/+2
| | | | | | | | | | | | Previously, dead links in target directory will not be copied. This is incorrect as dead links are not uncommon in our rootfs. So we use '-a' option instead. (From OE-Core rev: 742440441222e0627abbdd3eb2ee16401e8f4adf) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate-volatile.sh: don't spawn background process at rootfs timeChen Qi2013-08-161-3/+3
| | | | | | | | | | | | | | | | | | | If we're building a read-only rootfs, we'll get the following error now and then. tar: .: file changed as we read it The root cause is that we spawn background process at rootfs time. When the tar command is running, it's possible that files under rootfs are changed by background processes, thus this error. [YOCTO #4937] (From OE-Core rev: 4bd419f95868d5b8707a45cee5f6c5c6a840a65b) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate-volatile.sh: use $ROOT_DIR/var/volatile/tmp as TMPDIRChen Qi2013-08-161-1/+1
| | | | | | | | | | | | | | | | | | It's possible that a 'No such directory' error occurs when doing check_requirement in populate-volatile.sh at rootfs time. This is because the $ROOT_DIR/var/tmp might be a dead link. Use $ROOT_DIR/var/volatile/tmp as the TMPDIR instead to avoid this error. [YOCTO #4883] [YOCTO #4103] (From OE-Core rev: 7c2c36a97bab46c73a3a1fb743ad3ec67a4c072e) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* checkroot.sh: respect the value of ENABLE_ROOTFS_FSCKChen Qi2013-08-121-1/+1
| | | | | | | | | | | | | | Previously, fsck is always disabled because the value of rootcheck in the checkroot.sh script is always set to 'no'. We should respect the value of ENABLE_ROOTFS_FSCK in /etc/default/rcS to allow for filesystem check. (From OE-Core rev: 5c11cf4db8f43003fb7132b92a78659f70f07ce0) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: add dmesg file to /var/logJackie Huang2013-07-103-2/+33
| | | | | | | | | | | | | We should create the /var/log/dmesg.log file as a default. If we don't then a later kernel error can flush the dmesg ring buffer, losing valuable debug information. (From OE-Core rev: faa8cc6c2a582a32c695f3f2b0d45b6892c769fd) Signed-off-by: Xin Ouyang <Xin.Ouyang@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: overwrite default hostname.shJackie Huang2013-07-101-2/+10
| | | | | | | | | | | | | | | | | | | /etc/init.d/hostname.sh does not have a graceful fallback if the /etc/hostname file doesn't exist. Other systems such as Ubuntu and RH will either leave the hostname in place, if a proper hostname is already set, otherwise it will set the hostname to 'localhost' when the /etc/hostname files doesn't exist. As you can see we have to add some additional handling to provide this behavior when the system's hostname command doesn't take the '-b' option. (From OE-Core rev: 09e59f1dad9fb52adb1717840837e42a36a6c7a1) Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: let status return 0 when proc is running wellJesse Zhang2013-05-301-0/+1
| | | | | | | | | | | | | Ensure that the status returns 0 instead of the last shell command result, otherwise the calling script can not properly detect the status of pid. (From OE-Core rev: d9d4fdc769dfe6bf9838f5c5f3189a80f0e3cf90) Signed-off-by: Jesse Zhang <sen.zhang@windriver.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: add /run directory from FHS 3 draft specificationJonathan Liu2013-05-291-4/+3
| | | | | | | | | | | | | | | | | | | | This adds the /run directory from the Filesystem Hierarchy Standard 3.0 Draft [1] and refactors the filesystem as follows: - Remove creation of /var/volatile/run - Remove creation of /var/volatile/lock - Remove symbolic link from /var/run to /var/volatile/run - Remove symbolic link from /var/lock to /var/volatile/lock - Add symbolic link from /var/run to /run - Add symbolic link from /var/lock -> /run/lock - Add /run to /etc/fstab for sysvinit compatibility [1] http://www.linuxbase.org/betaspecs/fhs/fhs.html#runRuntimeVariableData (From OE-Core rev: 0e326280a15b0f2c4ef2ef4ec441f63f55b75873) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate-volatile.sh: remove repeated leading slashes in TNAMEJonathan Liu2013-05-241-7/+7
| | | | | | | | | | | | | | | | This avoids triple slashes in the generated /etc/volatile.cache to reduce disk usage and in the output when verbose mode is enabled. As all the paths for volatiles start with a slash, we can change TNAME=${ROOT_DIR}/${TNAME} to TNAME=${ROOT_DIR}${TNAME}. To avoid a double slash when ROOT_DIR is /, we strip the extra slash from ROOT_DIR. (From OE-Core rev: af56670f656ec0989aa7fd6cf6037cbc9cd88185) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: fix read-only-rootfs-hook.sh to start earlierPaul Eggleton2013-04-102-1/+2
| | | | | | | | | | | Mount /var/volatile ourselves so that we can set up the writable area first. This fixes the urandom service not starting properly when read-only-rootfs is enabled. (From OE-Core rev: 44c7d8a27a84a04251408e9a7d9550629bc17704) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: fix read-only-rootfs-hook.sh to avoid using unionfsPaul Eggleton2013-04-101-11/+4
| | | | | | | | | | | Unionfs isn't available everywhere, and we can get similar results (if not quite as neatly) by using bind mounts + tmpfs and copying the data over. (From OE-Core rev: 5a8ba93efa554c3b4d3b48ca8d668419a8c77f42) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev: move /run volatile entry to udev instead of initscriptsRoss Burton2013-03-261-1/+0
| | | | | | | | | | | | | | | | initscripts is generally installed on systemd-using images, but because it specifies that /run is a symlink to /var/run managed by volatiles it totally breaks systemd by copying/deleting /run from underneath systemd. Deleting sockets mid-boot doesn't leave systemd in a happy place. As this volatile reference of /run was introduced by udev 182, move it's reference to the udev recipe. This way it will never be present on systemd images, as systemd manages /run as a tmpfs itself. (From OE-Core rev: 5b0257e318340c2d6c8d3b0c3fa32272d6e9526b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate-volatile.sh: remove trailing whitespacesChen Qi2013-03-071-3/+3
| | | | | | | | | | Remove trailing whitespaces. (From OE-Core rev: 082dca6f73858581863f103b467ff73cebe2c0da) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate-volatile.sh: improve the handling of link config itemsChen Qi2013-03-071-16/+21
| | | | | | | | | | | | | | | | | | | | | | | | Previously, if there's a link config item in the config file like l root root 1777 /tmp /var/tmp and /tmp has existed, the symlink will not be created correctly. Another example is the /run directory. If /run directory has been created by some recipe or script before populate-volatile.sh runs, the symlink of /run to /var/run will not be created correctly. This patch ensures that the system creates symlinks exactly as the config file tells it. [YOCTO #3404] [YOCTO #3406] (From OE-Core rev: a54287d8e3d75a727c8ed5654a822bda256b0849) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate-volatile.sh: add ROOT_DIR variable to support running at rootfs timeChen Qi2013-03-071-17/+45
| | | | | | | | | | | | | | | | | | | | | | | | For populate-volatile.sh script to run correctly both at rootfs time and at system boot time, it needs to be aware of which situation it is now in. We use the ROOT_DIR variable to indicate whether it is run at rootfs time or not. ROOT_DIR being "/" indicates that this script is run at system boot time, otherwise, it is run at rootfs time. Also, we ignore failures when running this script at rootfs time. For example, if ${ROOT_DIR}/var/dir1 is symlink to /var/volatile/dir1, it's possible that the link is a dead link. So if we're going to create some file under ${ROOT_DIR}/var/dir1, it will fail. But the failure does no harm, because this script will always run at system boot time to set up the correct files and directories. [YOCTO #3406] (From OE-Core rev: 45396e3edcce4a33fcbef6456f31811f30c26c63) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: Add status function to /etc/init.d/functionsJesse Zhang2013-02-082-1/+16
| | | | | | | | | | | | | | [ CQID: WIND00388860 ] Many initscripts want a simple way to display status information. Add the 'status' function to the functions file. (From OE-Core rev: adcb39845b6d3af9472fa5051a1d918344eb6bda) Signed-off-by: Jesse Zhang <sen.zhang@windriver.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initiscripts: Fix populate-volatiles.sh whitespaceRichard Purdie2013-02-061-110/+97
| | | | | | (From OE-Core rev: d69935fbef2b5a8b187e58ac5ade0ffb9f95f803) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-13 20:04:25 +0000