[3f8be484] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?> |
---|
[aa18ac0] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" |
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ |
---|
[3f8be484] | 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 | |
---|
[95112ed] | 11 | <title>Adding the CLFS User</title> |
---|
[3f8be484] | 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 |
---|
[95112ed] | 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 |
---|
[3f8be484] | 20 | the installation process. As <systemitem class="username">root</systemitem>, |
---|
| 21 | issue the following commands to add the new user:</para> |
---|
| 22 | |
---|
[95112ed] | 23 | <screen><userinput>groupadd clfs |
---|
[a4b892f] | 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> |
---|
[3f8be484] | 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 |
---|
[95112ed] | 35 | user <systemitem class="username">clfs</systemitem>.</para> |
---|
[61dfcb4] | 36 | |
---|
| 37 | <important> |
---|
| 38 | <para>The build instructions assume that the <command>bash</command> |
---|
| 39 | shell is in use.</para> |
---|
| 40 | </important> |
---|
| 41 | |
---|
[3f8be484] | 42 | </listitem> |
---|
| 43 | </varlistentry> |
---|
| 44 | |
---|
| 45 | <varlistentry> |
---|
[95112ed] | 46 | <term><parameter>-g clfs</parameter></term> |
---|
[3f8be484] | 47 | <listitem> |
---|
[95112ed] | 48 | <para>This option adds user <systemitem class="username">clfs</systemitem> |
---|
| 49 | to group <systemitem class="groupname">clfs</systemitem>.</para> |
---|
[3f8be484] | 50 | </listitem> |
---|
| 51 | </varlistentry> |
---|
| 52 | |
---|
| 53 | <varlistentry> |
---|
[95112ed] | 54 | <term><parameter>clfs</parameter></term> |
---|
[3f8be484] | 55 | <listitem> |
---|
| 56 | <para>This is the actual name for the created group and user.</para> |
---|
| 57 | </listitem> |
---|
| 58 | </varlistentry> |
---|
| 59 | |
---|
| 60 | </variablelist> |
---|
| 61 | |
---|
[95112ed] | 62 | <para>To log in as <systemitem class="username">clfs</systemitem> (as |
---|
| 63 | opposed to switching to user <systemitem class="username">clfs</systemitem> |
---|
[3f8be484] | 64 | when logged in as <systemitem class="username">root</systemitem>, which |
---|
[95112ed] | 65 | does not require the <systemitem class="username">clfs</systemitem> user |
---|
| 66 | to have a password), give <systemitem class="username">clfs</systemitem> |
---|
[3f8be484] | 67 | a password:</para> |
---|
| 68 | |
---|
[95112ed] | 69 | <screen><userinput>passwd clfs</userinput></screen> |
---|
[3f8be484] | 70 | |
---|
[95112ed] | 71 | <para>Grant <systemitem class="username">clfs</systemitem> full access to |
---|
[040521bc] | 72 | <filename class="directory">${CLFS}/cross-tools</filename> and |
---|
| 73 | <filename class="directory">${CLFS}/tools</filename> by making <systemitem |
---|
[95112ed] | 74 | class="username">clfs</systemitem> the directorys' owner:</para> |
---|
[3f8be484] | 75 | |
---|
[040521bc] | 76 | <screen><userinput>chown -v clfs ${CLFS}/tools |
---|
| 77 | chown -v clfs ${CLFS}/cross-tools</userinput></screen> |
---|
[3f8be484] | 78 | |
---|
[8659630] | 79 | <para>If a separate working directory was created as suggested, |
---|
[95112ed] | 80 | give user <systemitem class="username">clfs</systemitem> ownership of this directory:</para> |
---|
[3f8be484] | 81 | |
---|
[040521bc] | 82 | <screen><userinput>chown -v clfs ${CLFS}/sources</userinput></screen> |
---|
[3f8be484] | 83 | |
---|
[95112ed] | 84 | <para>Next, login as user <systemitem class="username">clfs</systemitem>. |
---|
[3f8be484] | 85 | This can be done via a virtual console, through a display manager, or |
---|
| 86 | with the following substitute user command:</para> |
---|
| 87 | |
---|
[95112ed] | 88 | <screen><userinput>su - clfs</userinput></screen> |
---|
[3f8be484] | 89 | |
---|
| 90 | <para>The <quote><parameter>-</parameter></quote> instructs |
---|
| 91 | <command>su</command> to start a login shell as opposed to a non-login |
---|
| 92 | shell. The difference between these two types of shells can be found |
---|
| 93 | in detail in <filename>bash(1)</filename> and <command>info |
---|
| 94 | bash</command>.</para> |
---|
| 95 | |
---|
[61dfcb4] | 96 | <note> |
---|
| 97 | <para>Until specified otherwise, all commands from this point on |
---|
| 98 | should be done as the <systemitem class="username">clfs</systemitem> |
---|
| 99 | user.</para> |
---|
| 100 | </note> |
---|
| 101 | |
---|
[3f8be484] | 102 | </sect1> |
---|