Gentoo Archives: gentoo-doc-cvs

From: "Joshua Saddler (nightmorph)" <nightmorph@g.o>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-working-rcscripts.xml
Date: Wed, 02 Mar 2011 08:09:58
Message-Id: 20110302080948.2746E2004F@flycatcher.gentoo.org
nightmorph    11/03/02 08:09:48

  Modified:             hb-working-rcscripts.xml
  Log:
  add suggestion on posix-compliance for initscripts, bug 353979

Revision  Changes    Path
1.32                 xml/htdocs/doc/en/handbook/hb-working-rcscripts.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-working-rcscripts.xml?rev=1.32&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-working-rcscripts.xml?rev=1.32&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-working-rcscripts.xml?r1=1.31&r2=1.32

Index: hb-working-rcscripts.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-rcscripts.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- hb-working-rcscripts.xml	11 Oct 2007 20:09:02 -0000	1.31
+++ hb-working-rcscripts.xml	2 Mar 2011 08:09:48 -0000	1.32
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-rcscripts.xml,v 1.31 2007/10/11 20:09:02 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-rcscripts.xml,v 1.32 2011/03/02 08:09:48 nightmorph Exp $ -->
 
 <sections>
 
@@ -14,8 +14,8 @@
 these aspects and explains how to deal with these scripts.
 </abstract>
 
-<version>1.25</version>
-<date>2007-10-11</date>
+<version>2</version>
+<date>2011-03-02</date>
 
 <section>
 <title>Runlevels</title>
@@ -651,7 +651,11 @@
 
 <p>
 Gentoo's init script syntax is based on the Bourne Again Shell (bash) so you are
-free to use bash-compatible constructs inside your init script.
+free to use bash-compatible constructs inside your init script. However, you may
+want to write your init scripts to be POSIX-compliant. Future init script
+systems may allow symlinking <path>/bin/sh</path> to other shells besides
+bash.  Init scripts that rely on bash-only features will then break these
+configurations.
 </p>
 
 </body>