|
Lines 54-66
Link Here
|
| 54 |
|
54 |
|
| 55 |
<para>&linux; users are often surprised to find that |
55 |
<para>&linux; users are often surprised to find that |
| 56 |
<application>Bash</application> is not the default shell in |
56 |
<application>Bash</application> is not the default shell in |
| 57 |
&os;. In fact, <application>Bash</application> is not even in |
57 |
&os;. In fact, <application>Bash</application> is not even |
| 58 |
the default installation. Instead, &os; uses &man.tcsh.1; as |
58 |
in the default installation. Instead, &os; uses &man.tcsh.1; |
| 59 |
the default shell. However, <application>Bash</application> and |
59 |
as the default root shell, and the <application>Bourne |
| 60 |
other shells are available for installation using the &os; <link |
60 |
shell</application>-compatible &man.sh.1; as the default user |
| 61 |
xlink:href="&url.base;/doc/en_US.ISO8859-1/books/handbook/ports.html">Packages |
61 |
shell. &man.sh.1; is very similar to <application>Bash</application> |
| 62 |
and Ports Collection</link>.</para> |
62 |
but with a much smaller feature-set. Generally shell scripts |
|
|
63 |
written for &man.sh.1; will run in <application>Bash</application>, |
| 64 |
but the reverse is not always true.</para> |
| 63 |
|
65 |
|
|
|
66 |
<para>However, <application>Bash</application> and other shells |
| 67 |
are available for installation using the &os; <link |
| 68 |
xlink:href="&url.base;/doc/en_US.ISO8859-1/books/handbook/ports.html">Packages |
| 69 |
and Ports Collection</link>.</para> |
| 70 |
|
| 64 |
<para>After installing another shell, use &man.chsh.1; to change |
71 |
<para>After installing another shell, use &man.chsh.1; to change |
| 65 |
a user's default shell. It is recommended that the |
72 |
a user's default shell. It is recommended that the |
| 66 |
<systemitem class="username">root</systemitem> user's default |
73 |
<systemitem class="username">root</systemitem> user's default |
|
Lines 130-136
Link Here
|
| 130 |
equivalents of <filename>.deb</filename> files on |
137 |
equivalents of <filename>.deb</filename> files on |
| 131 |
Debian/Ubuntu based systems and <filename>.rpm</filename> |
138 |
Debian/Ubuntu based systems and <filename>.rpm</filename> |
| 132 |
files on Red Hat/Fedora based systems. Packages are |
139 |
files on Red Hat/Fedora based systems. Packages are |
| 133 |
installed using <application>pkg</application>. For example, |
140 |
installed using <command>pkg</command>. For example, |
| 134 |
the following command installs |
141 |
the following command installs |
| 135 |
<application>Apache 2.4</application>:</para> |
142 |
<application>Apache 2.4</application>:</para> |
| 136 |
|
143 |
|
|
Lines 247-253
Link Here
|
| 247 |
rebooting the system:</para> |
254 |
rebooting the system:</para> |
| 248 |
|
255 |
|
| 249 |
<screen>&prompt.root; <userinput>service <replaceable>sshd</replaceable> start</userinput> |
256 |
<screen>&prompt.root; <userinput>service <replaceable>sshd</replaceable> start</userinput> |
| 250 |
&prompt.root; <userinput>service apache24 start</userinput></screen> |
257 |
&prompt.root; <userinput>service <replaceable>apache24</replaceable> start</userinput></screen> |
| 251 |
|
258 |
|
| 252 |
<para>If a service has not been enabled, it can be started from |
259 |
<para>If a service has not been enabled, it can be started from |
| 253 |
the command line using <option>onestart</option>:</para> |
260 |
the command line using <option>onestart</option>:</para> |