linux/poky.git/meta/recipes-core/base-files, branch yocto-3.1.23

base-files: set ptmxmode to 666

2019-11-27T13:25:18+00:00

Make sure that the (newer) /dev/pts/ptmx is accessible by users. This is useful e.g. when running containers which symlink /dev/ptmx to /dev/pts/ptmx on start. The default mode (000) does not allow to create ptys inside the container. Using 666 when symlinking /dev/ptmx is also recommended by the kernel documentation when /dev/ptmx is symlinked: https://www.kernel.org/doc/Documentation/filesystems/devpts.txt Also buildroot uses ptmxmode=0666. The patch introducing the change explains related use cases why this is necessary a bit more in depth: https://github.com/buildroot/buildroot/commit/8196b299ba12bd6741bf7f4462cad180dab77fb0#diff-2d4604b9e565eb19fa52ce31f282f06c (From OE-Core rev: c999bc5ddd9beb5274f77b885e2ac71205e42266) Signed-off-by: Stefan Agner Signed-off-by: Richard Purdie

base-files: drop legacy empty file /etc/default/usbd

2019-09-18T11:09:02+00:00

Doesn't seem to be referenced by anything in oe-core any more. (From OE-Core rev: 526188096bc37af3140c9210ece92ed94c3bdfe0) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

base-files: nsswitch.conf is glibc specific

2019-08-28T10:31:22+00:00

(From OE-Core rev: e9f751a6fd6a4fc1cfac74202e1b71291aade705) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

base-files: move hostname operations out of issue file settings

2019-04-23T22:30:20+00:00

The function do_install_basefilesissue is meant to deal with /etc/issue* files and the following setting could actually be overridden. BASEFILESISSUEINSTALL ?= "do_install_basefilesissue" So move the hostname operations out of this function. (From OE-Core rev: f17bcc46341db5ee91bb26389ccaebc68c49b97e) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

base-files: filesystems serves no real purpose

2019-01-31T23:23:27+00:00

mount can generally figure out the filesystem type from the superblock; otherwise, /proc/filesystems is a more correct fallback than /etc/filesystems and presumably always available. (From OE-Core rev: 4199676383ce50b81c05a4d2b2610c9cdb49342e) Signed-off-by: Jonas Bonn Signed-off-by: Richard Purdie

base-files: Avoid problems if DISTRO_VERSION contains undefined variable

2019-01-21T23:44:22+00:00

If DISTRO_VERSION is defined to some undefined variable, e.g., DISTRO_VERSION = "${FOO_VERSION}", and /bin/sh is dash, then do_install() would fail with an error such as: run.do_install.2945:193: run.do_install.2945: Syntax error: Unterminated quoted string This was due to unexpanded Python code making it into the shell code, confusing the shell parser. Reported-by: srinivasan (From OE-Core rev: fdd0b9e26ef11fa287692848ea3add64ba623433) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

netbase/base-files: move /etc/hosts from netbase to base-files

2019-01-11T10:39:08+00:00

Move /etc/hosts to base-files, and also add entry to it according to hostname setting. This fixes the problem of commands like `hostname -f' failing due to lack of such entry. (From OE-Core rev: 31e6d08f20a804fccb958e19045d8f9e9806071a) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

base-files: change permissions on /sys and /proc

2018-10-18T22:26:35+00:00

The kernel mounts /proc and /sys with the mode 555. Fedora explicitly sets this value in its filesystem setup package. Debian doesn't seem to set it explictly. Having them be 755 causes permission issues on upgrades inside a container where the guest does not have the permission to change the modes of the mount points. So, just bite the bullet and force them to be 555. (From OE-Core rev: 7e311b0c7222fa9127a96945c9ded7bee5e40eb3) Signed-off-by: Dan McGregor Signed-off-by: Richard Purdie

base-files: fix handling of resize

2018-08-14T10:36:31+00:00

The current handling of resize is incorrect. Using `resize > /dev/null 2>&1 && resize > /dev/null' will cause the second resize command to not execute because 'resize > /dev/null 2>&1' will fail for resize utility from busybox. What we really should do is just to check whether ${bindir}/resize is executable and execute it if so. Using '-x' is sufficient. (From OE-Core rev: 41688279cba3a5afc4fdc65fd245b9bb6ada695e) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

base-files: profile: Avoid using "command" to determine if programs exist

2018-07-26T12:16:40+00:00

Since the existence of "command" in itself is not guaranteed, using it to determine if other executables exist is moot. Instead just run the executables and let the shell determine if they exist. By piping stderr to /dev/null we avoid unnecessary warnings in case they do not exist. (From OE-Core rev: ba8510deb73e07f17be051fa15a91731ec10382f) Signed-off-by: Peter Kjellerstedt Signed-off-by: Ross Burton Signed-off-by: Richard Purdie