Changeset ec7b0466 for chapter04/addinguser.xml
- Timestamp:
- 09/27/2022 06:07:58 PM (2 years ago)
- Branches:
- 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- ef93b66
- Parents:
- 2646c57
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/addinguser.xml
r2646c57 rec7b0466 15 15 the packages in the next two chapters are built as an unprivileged user. 16 16 You could use your own user name, but to make it easier to set up a clean 17 working environment, create a new user called <systemitem17 working environment, we will create a new user called <systemitem 18 18 class="username">lfs</systemitem> as a member of a new group (also named 19 <systemitem class="groupname">lfs</systemitem>) and usethis user during19 <systemitem class="groupname">lfs</systemitem>) and log in as this user during 20 20 the installation process. As <systemitem class="username">root</systemitem>, 21 21 issue the following commands to add the new user:</para> … … 25 25 26 26 <variablelist> 27 <title>Th e meaning of the command line options:</title>27 <title>This is what the command line options mean:</title> 28 28 29 29 <varlistentry> … … 55 55 <listitem> 56 56 <para>This parameter prevents possible copying of files from a skeleton 57 directory ( default is <filename class="directory">/etc/skel</filename>)57 directory (the default is <filename class="directory">/etc/skel</filename>) 58 58 by changing the input location to the special null device.</para> 59 59 </listitem> … … 69 69 </variablelist> 70 70 71 <para>To log in as <systemitem class="username">lfs</systemitem> (as opposed71 <para>To enable logging in as <systemitem class="username">lfs</systemitem> (as opposed 72 72 to switching to user <systemitem class="username">lfs</systemitem> when logged 73 73 in as <systemitem class="username">root</systemitem>, which does not require … … 78 78 79 79 <para>Grant <systemitem class="username">lfs</systemitem> full access to 80 all directories under <filename class="directory">$LFS</filename> by making81 <systemitem class="username">lfs</systemitem> the directoryowner:</para>80 all the directories under <filename class="directory">$LFS</filename> by making 81 <systemitem class="username">lfs</systemitem> the owner:</para> 82 82 83 83 <screen><userinput>chown -v lfs $LFS/{usr{,/*},lib,var,etc,bin,sbin,tools} … … 86 86 esac</userinput></screen> 87 87 88 <note><para>In some host systems, the followingcommand does not complete89 properly and suspends the login tothe &lfs-user; user to the background.88 <note><para>In some host systems, the following <command>su</command> command does not complete 89 properly and suspends the login for the &lfs-user; user to the background. 90 90 If the prompt "lfs:~$" does not appear immediately, entering the 91 91 <command>fg</command> command will fix the issue.</para></note> … … 99 99 <para>The <quote><parameter>-</parameter></quote> instructs 100 100 <command>su</command> to start a login shell as opposed to a non-login shell. 101 The difference between these two types of shells can be found in detail in101 The difference between these two types of shells is described in detail in 102 102 <filename>bash(1)</filename> and <command>info bash</command>.</para> 103 103
Note:
See TracChangeset
for help on using the changeset viewer.