openembedded-core.git/meta/recipes-core/sysvinit, branch thud

meta: Use double colon for chown OWNER:GROUP

2018-11-06T12:14:24+00:00

Rationale - excerp from `info chown`
====================================

OWNER‘:’GROUP
     If the OWNER is followed by a colon and a GROUP (a group name or
     numeric group ID), with no spaces between them, the group ownership
     of the files is changed as well (to GROUP).

   Some older scripts may still use ‘.’ in place of the ‘:’ separator.
POSIX 1003.1-2001 (*note Standards conformance::) does not require
support for that, but for backward compatibility GNU ‘chown’ supports
‘.’ so long as no ambiguity results.  New scripts should avoid the use
of ‘.’ because it is not portable, and because it has undesirable
results if the entire OWNER‘.’GROUP happens to identify a user whose
name contains ‘.’.

Signed-off-by: Kosta Zertsekel 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

sysvinit: Fix build with glibc 2.28 + libxcrypt

2018-08-14T15:32:50+00:00

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

sysvinit-inittab: do not use 'exit 1' to postpone to first boot

2018-05-15T09:00:27+00:00

Instead, first check if we need to do anything at all during first boot,
and if so, either postpone to first boot via pkg_postinst_ontarget()
when running on host, or run the necessary setup code when running on target.

Signed-off-by: Alexander Kanavin 
Signed-off-by: Ross Burton

sysvinit: inherit distro_features_check

2018-01-04T12:56:03+00:00

Use distro_features_check so that we can have a uniform controller.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

initscripts: don't use update-alternatives

2017-12-02T11:24:36+00:00

Stop using update-alternatives for managing /etc/init.d/functions. Also,
make the initscripts-functions subpackage to (runtime) conflict with
lsbinitscripts.

[YOCTO #10944]

Signed-off-by: Markus Lehtonen

sysvinit-inittab: start_getty: Cleanup comments

2017-09-21T08:23:59+00:00

Signed-off-by: Andrea Adami 
Signed-off-by: Ross Burton

sysvinit-inittab: start_getty: consider whitespaces in tty driver name

2017-09-21T08:23:59+00:00

Unbreak serial console when driver name contains spaces (PXA serial).

Fix commit ac0e954
"start_getty: Over added SERIAL_CONSOLE cause error in userspace log"

Signed-off-by: Andrea Adami 
Signed-off-by: Ross Burton

start_getty: Over added SERIAL_CONSOLE cause error in userspace log

2017-06-03T22:43:28+00:00

Error log will be logged into /var/log/message.
Added in more condition checking on the script. Check
/proc/tty/drivers and /proc/tty/driver/*
file system to retrieve active targeted serial.
Only establish getty with active serial in runtime.

[YOCTO #10844]

Reviewed-by: Saul Wold 
Signed-off-by: Choong YinThong 
Signed-off-by: Ross Burton

sysvinit-inittab: fix getty device removal

2016-12-16T08:30:01+00:00

getty devices were not being removed in some cases because device name
was not at the end of the line, for example a ttyS1 device:

S1:12345:respawn:/bin/start_getty 115200 ttyS1 vt102

Removing this limitation allows sed to remove any line containing
the device.

Signed-off-by: Leonardo Sandoval 
Signed-off-by: Ross Burton

sysvinit-inittab: make TERM=vt102 on serial consoles

2016-11-23T11:02:27+00:00

This makes more sense than the default TERM=linux (as set
by the linux kernel).
In addition, when using busybox init, it tries to achieve
the same (in a different way).

Both agetty, and busybox getty support the terminal type as
the last argument.

Signed-off-by: André Draszik 
Signed-off-by: Ross Burton