openembedded-core.git/meta/recipes-core/base-files, branch krogoth

This is a backport from master of 2 consecutive fixes.

2016-11-08T23:03:21+00:00

First fix commit:
1100af93cb07caf24d568c039d52fb0c80714c30
Second fix commit:
b7b2e348716161deb21c9864ac5caa5f1df1fa9c

The error these commits fix can prevent Eclipse debugging on
certain target configurations.

* base-files: Add shell test quoting

  tty can return "not a tt" which results in warnings when /etc/profile
  is executed.

  (From OE-Core rev: eed586dd238efe859442b21b425f04e262bcdb2b)

  Signed-off-by: Jussi Kukkonen 
  Signed-off-by: Richard Purdie 

* base-files: fix profile error under < /dev/null

  Previous attempts to constrain execution of `resize` to only TTYs did
  not properly handle situations when `tty` would return the string "not a
  tty". The symptom is "/etc/profile: line 34: test: too many arguments".
  Fix this by utilizing the exit code of `tty`. Also use `case` instead of
  `cut` to eliminate a subshell.

  (From OE-Core rev: e67637e4472ff3a1e2801b84ee3d69d4e14b9efc)

  Signed-off-by: Richard Tollerton 
  Signed-off-by: Ross Burton 
  Signed-off-by: Richard Purdie 

Signed-off-by: brian avery 
Signed-off-by: Armin Kuster

base-files: restrict resize to run on serial consoles only in profile │·

2016-08-23T16:28:58+00:00

We don't need/wan't to run resize on an ssh connection. It's useless and
it breaks the Eclipse SSH debug connection. So, we added a check.

YOCTO #9362

Signed-off-by: bavery 
Signed-off-by: Ross Burton

base-files: add some safety checks in profile

2016-06-29T18:34:40+00:00

Add some safety checks when sourcing files in /etc/profile.d/, in particular:
- source only *.sh files, not every file. This is the practice in use in both
  Fedora and Debian/Ubuntu (see
  https://help.ubuntu.com/community/EnvironmentVariables#A.2Fetc.2Fprofile.d.2F.2A.sh);
- check the input is actually a file and is readable. This check is especially
  important if profile.d is empty, as "*.sh" will get expanded only if
  profile.d is not empty. Previously if profile.d was present but empty,
  "/etc/profile.d/*" was sourced causing errors on login and breaking stuff, for
  example X startup.

(From OE-Core rev: 8961bc4b71723477a3b4a837a1d9c25c1b860b9e)

Signed-off-by: Diego Rondini 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

readline: move inputrc into readline

2016-01-07T13:40:08+00:00

inputrc is the global configuration file for the readline library.

Signed-off-by: Joseph A. Lutz 
Signed-off-by: Ross Burton

base-files: stage /etc/skel

2015-11-25T07:56:49+00:00

Having skel in the staging area lets other recipes access these files.
For ex. recipes inheriting useradd, if passing "-m" to USERADD_PARAM,
.bashrc and .profile are put automatically in $HOME, as expected.

Signed-off-by: Ioan-Adrian Ratiu 
Signed-off-by: Ross Burton

base-files: Remove /proc/bus/usb from fstab.

2015-05-15T16:58:48+00:00

The usb filesystem was removed in Linux 3.5.

Signed-off-by: Andreas Oberritter 
Signed-off-by: Richard Purdie

base-files: Check for /run and /var/lock softlinks on upgrade

2015-04-20T14:01:20+00:00

Commit ea647cd9eebdc3e3121b84074519c4bb305adac9 moved the locations
of /run and /var/lock to match the FHS 3 draft specifications.
However, the install doesn't remove the existing directories.
As a result, upgrading a system may result in /run as a softlink
to /var/run and /var/run as a softlink to /run, creating a circular
link.

During pre-install, check for the existence of the old softlinks and
remove them so the new directories can be installed.

Signed-off-by: Bryan Evenson

base-files: clean up and clarify hostname logic

2015-02-23T18:00:12+00:00

Change the hostname logic the default value is ${MACHINE}, and explain how to
change it.

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

base-files/profile: change EDITOR to not be busybox specific

2015-02-14T08:40:35+00:00

Setting "EDITOR=/bin/vi" breaks on non-busybox systems, as
vim will populate /usr/bin/vi instead, and you get stuff like:

  op3:~/poky/meta-builder$ git commit -s
  error: cannot run /bin/vi: No such file or directory
  error: unable to start editor '/bin/vi'
  Please supply the message using either -m or -F option.
  op3:~/poky/meta-builder$ which vi
  /usr/bin/vi
  op3:~/poky/meta-builder$

Since we've already specified a proper path above in the profile,
we've no need to call out where in the path vi lives, and hence
this will work with busybox and a full vim install w/o busybox.

Signed-off-by: Paul Gortmaker 
Signed-off-by: Ross Burton

base-files: avoid overwritting editable files during package updating

2014-12-03T12:22:41+00:00

Use CONFFILES to mark editable files as such,
  /etc/motd
  /etc/nsswitch.conf
  /etc/profile

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.

Signed-off-by: Jian Liu 
Signed-off-by: Ross Burton