Changeset 9e4bed20
- Timestamp:
- 07/22/2005 04:04:49 PM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- e540c04
- Parents:
- e45ae14c
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
general.ent
re45ae14c r9e4bed20 1 <!ENTITY day "2 1">1 <!ENTITY day "22"> 2 2 <!ENTITY month "07"> 3 3 <!ENTITY year "2005"> 4 4 <!ENTITY version "svn-&year;&month;&day;"> 5 <!ENTITY releasedate "July &day; st, &year;">5 <!ENTITY releasedate "July &day;nd, &year;"> 6 6 <!ENTITY pubdate "&year;-&month;-&day;"> <!-- metadata req. by TLDP --> 7 7 <!ENTITY blfs-version "svn"> <!-- svn|[release #] --> -
introduction/welcome/changelog.xml
re45ae14c r9e4bed20 25 25 <itemizedlist> 26 26 27 <listitem> 28 <para>July 22nd 2005 [randy]: Added textual updates to the "After LFS 29 Configuration" chapter.</para> 30 </listitem> 31 27 32 <listitem> 28 33 <para>July 21st 2005 [randy]: Added additional text to the "Conventions" -
postlfs/config/skel.xml
re45ae14c r9e4bed20 26 26 <para>Together, the <command>/usr/sbin/useradd</command> command and 27 27 <filename class="directory">/etc/skel</filename> directory (both are easy to 28 setup and use) provide a way to assure new users are added on your LFS 29 system with the same beginning settings for things like <envar>PATH</envar>, 30 keyboard processing and environmental variables. Using these two facilities 31 makes it easier to assure this initial state for each new user.</para> 28 set up and use) provide a way to assure new users are added to your LFS 29 system with the same beginning settings for things such as the 30 <envar>PATH</envar>, keyboard processing and other environmental variables. 31 Using these two facilities makes it easier to assure this initial state for 32 each new user added to the system.</para> 32 33 33 34 <para>The <filename class="directory">/etc/skel</filename> directory holds … … 40 41 <para>The <command>useradd</command> program uses a collection of 41 42 default values kept in <filename>/etc/default/useradd</filename>, 42 if it exists. If th efile does not exist, then it uses some internal43 if it exists. If this file does not exist, then it uses some internal 43 44 defaults. You can see the default values by running 44 45 <command>/usr/sbin/useradd -D</command>.</para> 45 46 46 <para>To change these values to something new, create a base <filename> 47 /etc/default/useradd</filename> file with the same values as the output of 48 <command>/usr/sbin/useradd -D</command>. Here is a sample.</para> 47 <para>To change these values to something new, create a base 48 <filename>/etc/default/useradd</filename> file as the 49 <systemitem class='username'>root</systemitem> user with the same values as 50 the output of <command>/usr/sbin/useradd -D</command>. Here is a 51 sample:</para> 49 52 50 53 <screen><literal># Begin /etc/default/useradd … … 60 63 61 64 <para>The only thing missing from the file is a default shell. Add that 62 by running:</para> 65 by running the following command as the 66 <systemitem class='username'>root</systemitem> user:</para> 63 67 64 68 <screen role="root"><userinput>/usr/sbin/useradd -D -s/bin/bash</userinput></screen> … … 67 71 <envar>SHELL</envar>=/bin/bash.</para> 68 72 69 <para><command>Useradd</command> has many parameters that 70 can be set in the <filename>/etc/default/useradd</filename> file.</para> 71 72 <para>For more information see <command>man useradd</command>.</para> 73 <para><command>useradd</command> has many parameters that 74 can be set in the <filename>/etc/default/useradd</filename> file. For more 75 information see <command>man useradd</command>.</para> 73 76 74 77 <bridgehead renderas="sect5">/etc/skel</bridgehead> 75 78 76 <para>To get started, create an <filename 77 class="directory">/etc/skel</filename> directory and make sure it is 78 writable only by the system administrator, usually <systemitem 79 class="username">root</systemitem>. Creating the 80 directory as <systemitem class="username">root</systemitem> is 81 the best way to go.</para> 79 <para>To get started, create an 80 <filename class="directory">/etc/skel</filename> directory and make sure it 81 is writable only by the system administrator, usually 82 <systemitem class="username">root</systemitem>. Creating the directory as 83 <systemitem class="username">root</systemitem> is the best way to go.</para> 82 84 83 85 <para>The mode of any files from this part of the book that you put in … … 111 113 will remind you of this. In brief, the book's commands have been written for 112 114 files <emphasis>not</emphasis> added to 113 <filename class="directory">/etc/skel</filename> and just send the results to114 the user's home directory. If the file is going to be in115 <filename class="directory">/etc/skel</filename> and instead just sends the 116 results to the user's home directory. If the file is going to be in 115 117 <filename class="directory">/etc/skel</filename>, change the book's command(s) 116 118 to send output there instead and then just copy the file from … … 126 128 <command>useradd</command> to create the user's home directory and 127 129 copy files from <filename class="directory">/etc/skel</filename> (can be 128 overridden) to the new user's home directory. For example:</para> 130 overridden) to the new user's home directory. For example (perform as the 131 <systemitem class="username">root</systemitem> user):</para> 129 132 130 133 <screen role="root"><userinput>useradd -m <replaceable>[newuser]</replaceable></userinput></screen>
Note:
See TracChangeset
for help on using the changeset viewer.