Difference between revisions of "Dash as /bin/sh"

From ArchWiki
Jump to: navigation, search
m (" don't " -> " do not ")
m (codeline -> ic)
Line 24: Line 24:
 
===Common places to check===
 
===Common places to check===
  
*Installed scripts with a {{codeline|#!/bin/sh}} shebang:
+
*Installed scripts with a {{Ic|#!/bin/sh}} shebang:
 
  $ find {,/usr}/bin -type f \
 
  $ find {,/usr}/bin -type f \
 
     -exec grep -q -- '^#!/bin/sh' {} \; \
 
     -exec grep -q -- '^#!/bin/sh' {} \; \
Line 49: Line 49:
 
==Initscript status==
 
==Initscript status==
  
* The FD checks with {{codeline|test -t}} in {{filename|/etc/rc.d/functions}} do not work correctly with dash, breaking colored output as a result. See http://bugs.archlinux.org/task/19551?project=1&order=id&sort=desc (the patch does not address this issue in particular).
+
* The FD checks with {{Ic|test -t}} in {{filename|/etc/rc.d/functions}} do not work correctly with dash, breaking colored output as a result. See http://bugs.archlinux.org/task/19551?project=1&order=id&sort=desc (the patch does not address this issue in particular).
:* Try using {{codeline|test(1)}} instead of the dash builtin?
+
:* Try using {{Ic|test(1)}} instead of the dash builtin?
:* Is the problem specific to calls involving {{codeline|init(1)}}?
+
:* Is the problem specific to calls involving {{Ic|init(1)}}?

Revision as of 17:45, 11 December 2011

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Dash as /bin/sh#)

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Dash as /bin/sh#)

Dash is a minimalist POSIX-complient shell. It can be much faster than Bash, and takes up less memory when in use. Most POSIX compliant scripts specify Template:Filename at the first line of the script, which means it will run Template:Filename as the shell, which by default in Arch is a symlink to Template:Filename.

You can re-symlink Template:Filename to Template:Filename, which can increase system performance, but first you must verify that none of the scripts that aren't explicitly #!/bin/bash scripts are safely POSIX compliant and do not require any of Bash's features.

This article is for those who want to help dash become the new Template:Filename.

From http://article.gmane.org/gmane.linux.arch.devel/11418:

Identifying bashisms

Features of bash that aren't included in Dash ('bashisms') will not work without being explicitly pointed to Template:Filename. The following instructions will allow you to find any scripts that may need modification.

Install Template:Package AUR from the AUR.

Common places to check

  • Installed scripts with a #!/bin/sh shebang:
$ find {,/usr}/bin -type f \
    -exec grep -q -- '^#!/bin/sh' {} \; \
    -exec checkbashisms -f -p {} +
  • Package install scripts:
$ find /var/lib/pacman/local -mindepth 2 -type f -name install \
    -exec checkbashisms -f -p {} + 2>&1 |\
    grep -v -e '^you may get strange results' \
            -e 'does not appear to have a #! interpreter line;$'
  • Initscripts and daemons:
$ find \
    /etc/rc.{conf,d,local{,.shutdown},multi,shutdown,single,sysinit} -type -f \
    -exec checkbashisms -f -p {} + 2>&1 |\
    grep -v -e '^you may get strange results' \
            -e 'does not appear to have a #! interpreter line;$'

Relinking /bin/sh

Once you have verified that it won't break any functionality, it should be safe to relink Template:Filename. To do so use the following command (as root):

 ln -sfT /bin/dash /bin/sh

Initscript status

  • Try using test(1) instead of the dash builtin?
  • Is the problem specific to calls involving init(1)?