From eogren@earthlink.net  Sat Apr  8 07:31:52 2000
Return-Path: <eogren@earthlink.net>
Received: from merlin.prod.itd.earthlink.net (merlin.prod.itd.earthlink.net [207.217.120.156])
	by hub.freebsd.org (Postfix) with ESMTP id B8C4C37B8F5
	for <FreeBSD-gnats-submit@freebsd.org>; Sat,  8 Apr 2000 07:31:51 -0700 (PDT)
	(envelope-from eogren@earthlink.net)
Received: from rod.darktech.org (ip132.cambridge2.ma.pub-ip.psi.net [38.32.112.132])
	by merlin.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id HAA12687
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 8 Apr 2000 07:31:49 -0700 (PDT)
Received: by rod.darktech.org (Postfix, from userid 1001)
	id A10811F3; Sat,  8 Apr 2000 10:33:00 -0400 (EDT)
Message-Id: <20000408143300.A10811F3@rod.darktech.org>
Date: Sat,  8 Apr 2000 10:33:00 -0400 (EDT)
From: eogren@earthlink.net
Reply-To: eogren@earthlink.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: Handbook missing entry on changing shells 
X-Send-Pr-Version: 3.2

>Number:         17862
>Category:       docs
>Synopsis:       Handbook missing entry about changing shells
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    jim
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Apr  8 07:40:00 PDT 2000
>Closed-Date:    Mon Apr 10 12:18:06 PDT 2000
>Last-Modified:  Mon Apr 10 12:18:29 PDT 2000
>Originator:     Eric Ogren
>Release:        FreeBSD 4.0-STABLE i386
>Organization:
>Environment:

FreeBSD rod.darktech.org 4.0-STABLE FreeBSD 4.0-STABLE #3: Tue Apr  4 21:01:56 EDT 2000     eogren@rod.darktech.org:/usr/src/sys/compile/BLUE  i386

>Description:

   Reported by Mike Kohout <mwkohout@hotmail.com> on freebsd-doc. 

Handbook is missing an entry on how to change shells. Mike suggested
documenting user utilities and doing it manually; since this is the
"Basics" section of the handbook, I chose to document the use of chsh
only.

>How-To-Repeat:

Notice that in section 3.4, there is nothing telling the user how to
change the shell.

>Fix:

Index: chapter.sgml
===================================================================
RCS file: /usr/local/doctree/doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v
retrieving revision 1.16
diff -u -r1.16 chapter.sgml
--- chapter.sgml	2000/04/06 20:28:27	1.16
+++ chapter.sgml	2000/04/08 14:23:34
@@ -331,6 +331,38 @@
       $TERM</command> prints whatever your terminal is set to.
       <command>echo \$TERM</command> prints <envar>$TERM</envar> as
       is.</para>
+
+    <sect2 id="changing-shells">
+     <title>Changing your shell</title>
+
+     <para>The easiest way to change your shell is to use the 
+     <command>chsh</command>. Running <command>chsh</command> will
+     place you into the editor that is in your <envar>EDITOR</envar>
+     environment variable; if it is not set, you will be placed in
+     <command>vi</command>. Change the &quot;Shell:&quot; line
+     accordingly.</para>
+
+     <para>You can also give <command>chsh</command> the
+     <option>-s</option> option; this will set the shell for you
+     without having to enter the editor. For example, if you wanted to
+     change your shell to bash:</para>
+     <screen>&prompt.user; <userinput>chsh -s /usr/local/bin/bash</userinput></screen>
+     <para>would do the trick. Running <command>chsh</command> with no
+     parameters and editing the shell from there would work also.</para>
+
+     <note><para>The shell that you wish to use
+     <emphasis>must</emphasis> be present in the
+     <filename>/etc/shells</filename> file. If you have installed a
+     shell from the <link linkend="ports">ports collection</link>,
+     then this should have been done for you already. If you installed
+     the shell by hand, you must do this.</para>
+     
+     <para>For example, if you installed <command>bash</command> by hand
+     and placed it into <filename>/usr/local/bin</filename>, you would
+     want to:</para>
+     <screen>&prompt.root; <userinput>echo &quot;/usr/local/bin/bash&quot; &gt;&gt; /etc/shells</userinput></screen>
+     <para>And then rerun <command>chsh</command>.</para></note>
+   </sect2>
   </sect1>
 
   <sect1 id="editors">

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-doc->jim 
Responsible-Changed-By: jim 
Responsible-Changed-When: Sat Apr 8 13:30:21 PDT 2000 
Responsible-Changed-Why:  
I'll take this. 
State-Changed-From-To: open->closed 
State-Changed-By: jim 
State-Changed-When: Mon Apr 10 12:18:06 PDT 2000 
State-Changed-Why:  
Committed, thanks! 
>Unformatted:
