1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../../general.ent">
|
---|
5 | %general-entities;
|
---|
6 | ]>
|
---|
7 |
|
---|
8 | <sect1 id="postlfs-config-shells" xreflabel="The /etc/shells File">
|
---|
9 | <?dbhtml filename="etcshells.html"?>
|
---|
10 |
|
---|
11 |
|
---|
12 | <title>The /etc/shells File</title>
|
---|
13 |
|
---|
14 | <indexterm zone="postlfs-config-shells">
|
---|
15 | <primary sortas="e-etc-shells">/etc/shells</primary>
|
---|
16 | </indexterm>
|
---|
17 |
|
---|
18 | <para>The <filename>shells</filename> file contains a list of
|
---|
19 | login shells on the system. Applications use this file to determine
|
---|
20 | whether a shell is valid. For each shell a single line should be
|
---|
21 | present, consisting of the shell's path, relative to the root of the
|
---|
22 | directory structure (/).</para>
|
---|
23 |
|
---|
24 | <para>For example, this file is consulted by <command>chsh</command>
|
---|
25 | to determine whether an unprivileged user may change the login shell for her
|
---|
26 | own account. If the command name is not listed, the user will be denied of
|
---|
27 | change.</para>
|
---|
28 |
|
---|
29 | <para>It is a requirement for applications such as
|
---|
30 | <application>GDM</application> which does not populate the
|
---|
31 | face browser if it can't find <filename>/etc/shells</filename>, or
|
---|
32 | FTP daemons which traditionally disallow access to users
|
---|
33 | with shells not included in this file.</para>
|
---|
34 |
|
---|
35 | <screen role="root"><userinput>cat > /etc/shells << "EOF"
|
---|
36 | <literal># Begin /etc/shells
|
---|
37 |
|
---|
38 | /bin/sh
|
---|
39 | /bin/bash
|
---|
40 |
|
---|
41 | # End /etc/shells</literal>
|
---|
42 | EOF</userinput></screen>
|
---|
43 |
|
---|
44 | </sect1>
|
---|