1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 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="ch-final-preps-addinguser">
|
---|
9 | <?dbhtml filename="addinguser.html"?>
|
---|
10 |
|
---|
11 | <title>Adding the CLFS User</title>
|
---|
12 |
|
---|
13 | <para>When logged in as user <systemitem class="username">root</systemitem>,
|
---|
14 | making a single mistake can damage or destroy a system. Therefore, we
|
---|
15 | recommend building the packages as an unprivileged user.
|
---|
16 | You could use your own user name, but to make it easier to set up a clean
|
---|
17 | work environment, create a new user called <systemitem
|
---|
18 | class="username">clfs</systemitem> as a member of a new group (also named
|
---|
19 | <systemitem class="groupname">clfs</systemitem>) and use this user during
|
---|
20 | the installation process. As <systemitem class="username">root</systemitem>,
|
---|
21 | issue the following commands to add the new user:</para>
|
---|
22 |
|
---|
23 | <screen><userinput>groupadd clfs
|
---|
24 | useradd -s /bin/bash -g clfs -d /home/clfs clfs
|
---|
25 | mkdir -pv /home/clfs
|
---|
26 | chown -v clfs:clfs /home/clfs</userinput></screen>
|
---|
27 |
|
---|
28 | <variablelist>
|
---|
29 | <title>The meaning of the command line options:</title>
|
---|
30 |
|
---|
31 | <varlistentry>
|
---|
32 | <term><parameter>-s /bin/bash</parameter></term>
|
---|
33 | <listitem>
|
---|
34 | <para>This makes <command>bash</command> the default shell for
|
---|
35 | user <systemitem class="username">clfs</systemitem>.</para>
|
---|
36 |
|
---|
37 | <important>
|
---|
38 | <para>The build instructions assume that the <command>bash</command>
|
---|
39 | shell is in use.</para>
|
---|
40 | </important>
|
---|
41 |
|
---|
42 | </listitem>
|
---|
43 | </varlistentry>
|
---|
44 |
|
---|
45 | <varlistentry>
|
---|
46 | <term><parameter>-g clfs</parameter></term>
|
---|
47 | <listitem>
|
---|
48 | <para>This option adds the new user to the
|
---|
49 | <systemitem class="groupname">clfs</systemitem> group.</para>
|
---|
50 | </listitem>
|
---|
51 | </varlistentry>
|
---|
52 |
|
---|
53 | <varlistentry>
|
---|
54 | <term><parameter>-d /home/clfs</parameter></term>
|
---|
55 | <listitem>
|
---|
56 | <para>This option sets the user's home directory, but does not create
|
---|
57 | it. We could have used <option>-m</option> to tell
|
---|
58 | <command>useradd</command> to create the directory as well, but this
|
---|
59 | would also copy whatever is in the host system's
|
---|
60 | <filename class="directory">/etc/skel</filename> directory into the new
|
---|
61 | user's home. We would prefer to have a clean user environment, so we
|
---|
62 | just create an empty directory after adding the user.</para>
|
---|
63 | </listitem>
|
---|
64 | </varlistentry>
|
---|
65 |
|
---|
66 | <varlistentry>
|
---|
67 | <term><parameter>clfs</parameter></term>
|
---|
68 | <listitem>
|
---|
69 | <para>This is the actual name for the created group and user.</para>
|
---|
70 | </listitem>
|
---|
71 | </varlistentry>
|
---|
72 |
|
---|
73 | </variablelist>
|
---|
74 |
|
---|
75 | <para>To log in as <systemitem class="username">clfs</systemitem> (as
|
---|
76 | opposed to switching to user <systemitem class="username">clfs</systemitem>
|
---|
77 | when logged in as <systemitem class="username">root</systemitem>, which
|
---|
78 | does not require the <systemitem class="username">clfs</systemitem> user
|
---|
79 | to have a password), give <systemitem class="username">clfs</systemitem>
|
---|
80 | a password:</para>
|
---|
81 |
|
---|
82 | <screen><userinput>passwd clfs</userinput></screen>
|
---|
83 |
|
---|
84 | <para>As <systemitem class="username">root</systemitem>,
|
---|
85 | grant <systemitem class="username">clfs</systemitem> full access to
|
---|
86 | <filename class="directory">${CLFS}/cross-tools</filename> and
|
---|
87 | <filename class="directory">${CLFS}/tools</filename> by making <systemitem
|
---|
88 | class="username">clfs</systemitem> the directorys' owner:</para>
|
---|
89 |
|
---|
90 | <screen><userinput>chown -v clfs ${CLFS}/tools
|
---|
91 | chown -v clfs ${CLFS}/cross-tools</userinput></screen>
|
---|
92 |
|
---|
93 | <para>If a separate working directory was created as suggested, run the
|
---|
94 | following command as <systemitem class="username">root</systemitem> to
|
---|
95 | give user <systemitem class="username">clfs</systemitem> ownership of this
|
---|
96 | directory as well:</para>
|
---|
97 |
|
---|
98 | <screen><userinput>chown -v clfs ${CLFS}/sources</userinput></screen>
|
---|
99 |
|
---|
100 | <para>Next, login as user <systemitem class="username">clfs</systemitem>.
|
---|
101 | This can be done via a virtual console, through a display manager, or
|
---|
102 | with the following substitute user command:</para>
|
---|
103 |
|
---|
104 | <screen><userinput>su - clfs</userinput></screen>
|
---|
105 |
|
---|
106 | <para>The <quote><parameter>-</parameter></quote> instructs
|
---|
107 | <command>su</command> to start a login shell as opposed to a non-login
|
---|
108 | shell. The difference between these two types of shells can be found
|
---|
109 | in detail in <filename>bash(1)</filename> and <command>info
|
---|
110 | bash</command>.</para>
|
---|
111 |
|
---|
112 | <note>
|
---|
113 | <para>Until specified otherwise, all commands from this point on
|
---|
114 | should be done as the <systemitem class="username">clfs</systemitem>
|
---|
115 | user.</para>
|
---|
116 | </note>
|
---|
117 |
|
---|
118 | </sect1>
|
---|