openembedded-core.git/meta/recipes-core/initscripts, branch pyro Mirror of openembedded-core initscripts/sysfs.sh: mount configfs if present 2017-03-01T12:54:20+00:00 Mike Looijmans mike.looijmans@topic.nl 2017-02-22T14:32:09+00:00 4f52130475d026c32f0380d301f56f6fa3df7ac9 configfs is another kernel virtual file system that should be mounted if configured, so if it's configured into the kernel, mount it. It is used to configure e.g. USB gadget mode and devicetree overlays. Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl> Signed-off-by: Ross Burton <ross.burton@intel.com> 
configfs is another kernel virtual file system that should be mounted
if configured, so if it's configured into the kernel, mount it. It is
used to configure e.g. USB gadget mode and devicetree overlays.

Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
Signed-off-by: Ross Burton <ross.burton@intel.com>
initscripts: Add PACKAGE_WRITE_DEPS for postinst 2017-01-19T22:51:06+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2017-01-19T17:01:10+00:00 853f05b4d81c9af0fe1050cd15f13b8d3f9a93a9 The postinstall needs systemd-systemctl-native, mark the dependency Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The postinstall needs systemd-systemctl-native, mark the dependency

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
initscripts: populate-volatile: suppress read-only-rootfs warnings 2016-12-22T08:46:37+00:00 André Draszik adraszik@tycoint.com 2016-12-20T09:02:40+00:00 765ee275f5499254b1f09e394c757072bea5f459 rm: can't remove '/etc/resolv.conf': Read-only file system ln: /etc/resolv.conf: File exists /etc/default/volatiles contains an entry: l root root 0644 /etc/resolv.conf /var/run/resolv.conf which causes populate-volatile.sh to execute the following in link_file(): if [ -L \"$2\" ]; then [ \"\$(readlink -f \"$2\")\" != \"\$(readlink -f \"$1\")\" ] && { rm -f \"$2\"; ln -sf \"$1\" \"$2\"; }; elif [ -d \"$2\" ]; then ... At the time the image is created, /etc/resolv.conf is already a symlink to /var/run/resolv.conf, but at boot time when populate-volatiles.sh is run, /var/run/resolv.conf doesn't exist, causing it to try to rm -f and ln -sf which of course fails due to the read-only filesystem. [YOCTO #10814] Signed-off-by: André Draszik <adraszik@tycoint.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
rm: can't remove '/etc/resolv.conf': Read-only file system
ln: /etc/resolv.conf: File exists

/etc/default/volatiles contains an entry:
l root root 0644 /etc/resolv.conf /var/run/resolv.conf

which causes populate-volatile.sh to execute the following in link_file():
  if [ -L \"$2\" ]; then
    [ \"\$(readlink -f \"$2\")\" != \"\$(readlink -f \"$1\")\" ] && { rm -f \"$2\"; ln -sf \"$1\" \"$2\"; };
  elif [ -d \"$2\" ]; then
    ...

At the time the image is created, /etc/resolv.conf is already a
symlink to /var/run/resolv.conf, but at boot time when
populate-volatiles.sh is run, /var/run/resolv.conf doesn't
exist, causing it to try to rm -f and ln -sf which of course
fails due to the read-only filesystem.

[YOCTO #10814]

Signed-off-by: André Draszik <adraszik@tycoint.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
initscripts: populate-volatile: don't run commands in background 2016-12-22T08:46:36+00:00 Mans Rullgard mans@mansr.com 2016-12-16T16:28:38+00:00 bead9e59768209dd70f9cba51d2f1e5925cc284d If commands are run asynchronously they may be completed out of order causing problems if later entries depend on earlier ones. Signed-off-by: Mans Rullgard <mans@mansr.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
If commands are run asynchronously they may be completed out of
order causing problems if later entries depend on earlier ones.

Signed-off-by: Mans Rullgard <mans@mansr.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
initscripts: populate-volatile: improve config file parsing 2016-12-13T22:47:26+00:00 Mans Rullgard mans@mansr.com 2016-12-01T12:30:34+00:00 415eaacb83b1c6df5210fb423e3e96e530b1dc42 This improves the config file parsing to permit blank lines and comments following an entry or preceeded by whitespace. Signed-off-by: Mans Rullgard <mans@mansr.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
This improves the config file parsing to permit blank lines and
comments following an entry or preceeded by whitespace.

Signed-off-by: Mans Rullgard <mans@mansr.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
initscripts: Start devpts at 06 instead of 38 2016-09-03T22:45:45+00:00 Mike Looijmans mike.looijmans@topic.nl 2016-08-31T13:22:51+00:00 4cb06256e0d13f3f5d0b280853b900d7d342b7f2 For example bootlogd needs devpts to be running, but bootlogd starts at 07. Starting bootlogd early makes perfect sense, so the best option here is to move devpts up to 06 to prevent this error message at boot: cannot allocate pseudo tty: No such file or directory Systems that have CONFIG_LEGACY_PTYS in the kernel will not see this message. Since it is called "LEGACY" for a reason, fixing this in userspace appears to be the better option here. The devpts script does not need anything except a mounted "/dev" which has been arranged in "S02sysfs.sh" already. Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
For example bootlogd needs devpts to be running, but bootlogd starts
at 07. Starting bootlogd early makes perfect sense, so the best option
here is to move devpts up to 06 to prevent this error message at boot:
cannot allocate pseudo tty: No such file or directory

Systems that have CONFIG_LEGACY_PTYS in the kernel will not see this
message. Since it is called "LEGACY" for a reason, fixing this in
userspace appears to be the better option here.

The devpts script does not need anything except a mounted "/dev" which
has been arranged in "S02sysfs.sh" already.

Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
initscripts: Check for logrotate in dmesg.sh 2016-08-23T16:44:05+00:00 Ovidiu Vancea ovidiu.vancea@ni.com 2016-08-12T15:04:12+00:00 277a5975d43125623b5a51ddcb48f9ee2474d0fc Autodetect previously hardcoded logrotate location because it can be installed in multiple places like /usr/bin/logrotate which is very common besides /usr/sbin Signed-off-by: Ovidiu Vancea <ovidiu.vancea@ni.com> Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Autodetect previously hardcoded logrotate location because it can be
installed in multiple places like /usr/bin/logrotate which is very
common besides /usr/sbin

Signed-off-by: Ovidiu Vancea <ovidiu.vancea@ni.com>
Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
initscripts: check if swapon/swapoff exists before executing them 2016-05-30T08:30:33+00:00 Ming Liu peter.x.liu@external.atlascopco.com 2016-05-26T21:14:33+00:00 2cb1142710cc2beb762c4c2b8edd44d3a97dafa0 Not all built images contain swapon/swapoff, for instance, it is configurable with or without them in busybox. So it'd better to check if they exist or not before executing them. Redirecting the potential errors to /dev/null is not good enough, which might suppress the *real* errors. Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Not all built images contain swapon/swapoff, for instance, it is
configurable with or without them in busybox. So it'd better to check if
they exist or not before executing them.

Redirecting the potential errors to /dev/null is not good enough, which
might suppress the *real* errors.

Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
initscripts: start urandom after populate-volatiles 2016-02-13T08:27:17+00:00 Jens Rehsack rehsack@gmail.com 2016-02-12T09:18:44+00:00 1f07dcfcecbd42f947b83c6f75d1a66186bcad68 In case of read-only rootfs, populoate-volatiles might be used to create some links (or bind-mounts) required for having a writable /var/lib. Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
In case of read-only rootfs, populoate-volatiles might be used to create
some links (or bind-mounts) required for having a writable /var/lib.

Signed-off-by: Jens Rehsack <sno@netbsd.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
initscripts: populate-volatiles.sh: add mount-bind feature 2016-02-13T08:27:17+00:00 Jens Rehsack rehsack@gmail.com 2016-02-12T09:17:32+00:00 ab42fcaf1427a29c31ac2e93965e20849b1b1234 Add ability to run "mount --bind" to populate-volatiles. Since several programs use realpath to determine several full qualified file names, there is no symlink to be resolved. So when speccing /run/lock - that's the location - not /var/run/lock because of the program is smarter than the operator/distributor. See https://github.com/rehsack/meta-jens/blob/jethro/recipes-core/initscripts/initscripts/volatiles for an example how to use the "b" feature. Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Add ability to run "mount --bind" to populate-volatiles. Since several
programs use realpath to determine several full qualified file names,
there is no symlink to be resolved. So when speccing /run/lock - that's
the location - not /var/run/lock because of the program is smarter
than the operator/distributor.

See https://github.com/rehsack/meta-jens/blob/jethro/recipes-core/initscripts/initscripts/volatiles
for an example how to use the "b" feature.

Signed-off-by: Jens Rehsack <sno@netbsd.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>