Changeset 2483c44
- Timestamp:
- 03/15/2001 04:54:07 PM (23 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 01c8218
- Parents:
- 44512db5
- Location:
- chapter01
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/alfsdiscuss.xml
r44512db5 r2483c44 3 3 4 4 <para> 5 The alfs-discuss list discusses the development of ALFS which stands for6 Automated Linux FromScratch. The goal of this project is to develop an5 The alfs-discuss list discusses the development of ALFS, which stands for 6 Automated Linux From Scratch. The goal of this project is to develop an 7 7 installation tool that can install an LFS system automatically for you. 8 8 It's main goal is to speed up compilation by taking away your need to 9 manually enter the commands to configure, compile and install packages.9 manually enter the commands to configure, compile, and install packages. 10 10 </para> 11 11 -
chapter01/changelog.xml
r44512db5 r2483c44 3 3 4 4 <para> 5 If, for example, a change is listed for chapter 5 it (usually) means the 6 same change has been made in the chapters for the other architectures. 5 If, for example, a change is listed for chapter 5, it (usually) means the 6 same change has been made in the corresponding chapter for the other 7 architectures. 7 8 </para> 8 9 … … 24 25 <listitem><para> 25 26 Chapter 4: Changed the wording to make it more general as ext2 no 26 longer is the only used file system. Reiser for exampleis often used27 longer is the only used file system. Reiserfs, for example, is often used 27 28 too now. 28 29 </para></listitem> 29 30 30 31 <listitem><para> 31 Chapter 5: Added static mawk, texinfo and partially gettext to faciliate32 Chapter 5: Added static mawk, texinfo, and partially gettext to faciliate 32 33 the move of Glibc from Chapter 5 to Chapter 6. 33 34 </para></listitem> … … 38 39 used to create device files. This second file (MAKEDEV-temp) doesn't 39 40 contain user names and group names but only user id's and group id's. We 40 need a few device files to get Glibc installed, but before GLibc is41 installed user and group names are not recognized yet;only the numeric41 need a few device files to get Glibc installed, but, before Glibc is 42 installed, user and group names are not recognized yet, only the numeric 42 43 id's. This requires a slightly modified MAKEDEV script which will be 43 44 generated by patching the original one. This patching is done here in … … 51 52 52 53 <listitem><para> 53 Chapter 5: Simplified ln commands 54 Chapter 5: Simplified ln commands. 54 55 </para></listitem> 55 56 … … 74 75 75 76 <listitem><para> 76 Chapter 5+6: Upgraded from gcc-2.95.2 to gcc-2.95.2.177 Chapter 5+6: Upgraded gcc-2.95.2 to gcc-2.95.2.1. 77 78 </para></listitem> 78 79 79 80 <listitem><para> 80 Chapter 5+6: Moved Glibc from chapter 5 to chapter 6 81 Chapter 5+6: Moved Glibc from chapter 5 to chapter 6. 81 82 </para></listitem> 82 83 83 84 <listitem><para> 84 Chapter 6: Changed libexecdir=/usr/bin in fileutils to libexecdir=/bin 85 Chapter 6: Changed libexecdir=/usr/bin in fileutils to libexecdir=/bin. 85 86 </para></listitem> 86 87 87 88 <listitem><para> 88 Chapter 6: Updated Glibc installation instructions. 'configparms' file89 Chapter 6: Updated Glibc installation instructions. The 'configparms' file 89 90 creation has been deleted. No need to pick a compiler (either distro's 90 91 native or the /usr/local/gcc2952/bin/gcc one); we're in chroot 91 now so we'll use the one we have 92 now so we'll use the one we have. 92 93 </para></listitem> 93 94 … … 114 115 115 116 <listitem><para> 116 Chapter 6: When entering chroot the $TERM variable inside chroot is set117 Chapter 6: When entering chroot, the $TERM variable inside chroot is set 117 118 properly. This is accomplished by: chroot ... -i HOME=/root TERM=$TERM ... 118 119 </para></listitem> … … 125 126 <listitem><para> 126 127 Chapter 6: Changed all "rm file && ln -s dest file" into 127 "ln -sf file" (in glibc, bzip2 and gzip installation ).128 "ln -sf file" (in glibc, bzip2 and gzip installations). 128 129 </para></listitem> 129 130 130 131 <listitem><para> 131 132 Chapter 7: Fixed the delays in the killproc function in the functions 132 script. Now after kill, first check PIDs, then sleep 2 if needed. More133 script. Now, after kill, first check PIDs, then sleep 2 if needed. More 133 134 details can be read in the comments in the script itself. 134 135 </para></listitem> -
chapter01/contactinfo.xml
r44512db5 r2483c44 5 5 Direct all your emails to the 6 6 <ulink url="mailto:lfs-discuss@linuxfromscratch.org">lfs-discuss 7 </ulink> mailing list preferably.7 </ulink> mailing list preferably. 8 8 </para> 9 9 -
chapter01/lfsannounce.xml
r44512db5 r2483c44 6 6 you can't post any messages to this list. This list is used to announce 7 7 new stable releases. If you want to be informed about development 8 releases as well then you'll have to join the lfs-discuss list. If9 you're already on the lfs-discuss list there's little use subscribing to8 releases as well, then you'll have to join the lfs-discuss list. If 9 you're already on the lfs-discuss list, there's little use subscribing to 10 10 this list as well because everything that is posted to the lfs-announce 11 11 list will be posted to the lfs-discuss list as well. -
chapter01/lfsdiscuss.xml
r44512db5 r2483c44 3 3 4 4 <para> 5 The lfs-discuss mailing list discusses matters strictly related to the5 The lfs-discuss mailing list discusses matters strictly related to the 6 6 LFS-BOOK. If you have problems with the book, want to report a bug or 7 two or have suggestions to improve the book, use this mailinglist.7 two, or have suggestions to improve the book, use this mailing list. 8 8 </para> 9 9 -
chapter01/lfssecurity.xml
r44512db5 r2483c44 3 3 4 4 <para> 5 The lfs-security mailing list discusses securityrelated matters. If you5 The lfs-security mailing list discusses security-related matters. If you 6 6 have security concerns or have heard about a package used by LFS that 7 7 has known security problems, you can address that on this list. -
chapter01/maillists.xml
r44512db5 r2483c44 1 1 <sect1 id="ch01-maillists"> 2 <title>Mailing lists and archives</title>2 <title>Mailing lists and archives</title> 3 3 4 4 <para> 5 The linuxfromscratch.org server is hosting the following public accessible6 mailing lists:5 The linuxfromscratch.org server is hosting the following publicly accessible 6 mailing lists: 7 7 </para> 8 8 … … 14 14 15 15 <listitem><para> 16 16 lfs-apps 17 17 </para></listitem> 18 18 … … 26 26 27 27 <listitem><para> 28 28 alfs-discuss 29 29 </para></listitem> 30 30 31 31 <listitem><para> 32 32 alfs-docs 33 33 </para></listitem> 34 34 35 35 <listitem><para> 36 36 alfs-ipc 37 37 </para></listitem> 38 38 39 39 <listitem><para> 40 40 alfs-profile 41 41 </para></listitem> 42 42 43 43 <listitem><para> 44 44 alfs-backend 45 45 </para></listitem> 46 46 -
chapter01/othermodes.xml
r44512db5 r2483c44 10 10 11 11 <para> 12 As the name implies the <emphasis>Set command</emphasis> tells you what12 As the name implies, the <emphasis>Set command</emphasis> tells you what 13 13 to write to set a mode. The <emphasis>Unset command</emphasis> tells 14 14 you what to write to unset a mode. … … 18 18 Replace listname in the example subject headers with the listname to which 19 19 you want to apply the mode to. If you want to set more than one mode (to 20 the same list or multiple lists) with one email you can do so by writing20 the same list or multiple lists) with one email, you can do so by writing 21 21 junk in the subject header like "hello" and then put the commands in the 22 22 body of the message instead. … … 35 35 <para> 36 36 All lists have the digest mode available and you can set yourself to 37 digest mode ,after you subscribe to a list. Being in digest mode will37 digest mode after you subscribe to a list. Being in digest mode will 38 38 cause you to stop receiving individual messages as they are posted to 39 39 the list and instead you will receive one email daily containing all 40 the messages posted to the list that day.40 the messages posted to the list during that day. 41 41 </para> 42 42 … … 44 44 There is a second digest mode called digest2. When you are set to this 45 45 mode you will receive the daily digests but you will also continue to 46 receive the individual messages to the lists a rethey are posted. To46 receive the individual messages to the lists as they are posted. To 47 47 set yourself to this mode write <emphasis>digest2</emphasis> instead of 48 48 <emphasis>digest</emphasis> in the subject header. … … 61 61 <para> 62 62 If you are going to be away for a while or wish to stop receiving 63 messages from the lists but you don't want to unsubscribe you can set63 messages from the lists but you don't want to unsubscribe, you can set 64 64 yourself to vacation mode. This has the same effect as unsubscribing 65 65 yourself, but you don't have to go through the unsubscribe process and -
chapter01/subscribe.xml
r44512db5 r2483c44 3 3 4 4 <para> 5 You can subscribe to any of the above 5 You can subscribe to any of the above-mentioned mailinglists by sending 6 6 an email to <ulink url="mailto:listar@linuxfromscratch.org"> 7 7 listar@linuxfromscratch.org</ulink> and write <emphasis>subscribe -
chapter01/unsubscribe.xml
r44512db5 r2483c44 25 25 unsubscribe lfs-apps 26 26 unsubscribe alfs-discuss 27 27 28 </literallayout></blockquote> 28 29
Note:
See TracChangeset
for help on using the changeset viewer.