Changeset 35c2fa60
- Timestamp:
- 10/04/2003 10:19:10 AM (21 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, 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:
- ec0ce9c
- Parents:
- 1e66abe
- Files:
-
- 1 deleted
- 15 edited
Legend:
- Unmodified
- Added
- Removed
-
INSTALL
r1e66abe r35c2fa60 1 1 LFS Book Conversion Tools Installation Instructions 2 2 3 After downloading the CVS source, there are some things that need to be set up3 After downloading the CVS source, there are some things that need to be set up 4 4 on your computer if you want to convert the XML source into something easier to 5 5 read (e.g. HTML, TXT, PS or PDF). If you are interested in this, then keep -
appendixa/bootscripts-shortdesc.xml
r1e66abe r35c2fa60 5 5 <para>The LFS-Bootscripts package contains SysV init style shell 6 6 scripts. These scripts do various tasks such as check filesystem 7 integrity during boot, load keymaps, set up networks and halt7 integrity during boot, load keymaps, set up networks and halt 8 8 processes at shutdown.</para> 9 9 -
appendixa/gzip-shortdesc.xml
r1e66abe r35c2fa60 3 3 <para>(Last checked against version &gzip-contversion;.)</para> 4 4 5 <para>The gzip package contains programs to compress and decompress files5 <para>The Gzip package contains programs to compress and decompress files 6 6 using the Lempel-Ziv coding (LZ77).</para> 7 7 -
appendixa/vim.xml
r1e66abe r35c2fa60 7 7 &aa-vim-down; 8 8 &aa-vim-shortdesc; 9 &aa-vim-alt;10 9 &aa-vim-desc; 11 10 &aa-vim-dep; -
chapter01/acknowledgements.xml
r1e66abe r35c2fa60 12 12 13 13 <listitem><para><ulink url="mailto:gerard@linuxfromscratch.org">Gerard 14 Beekmans</ulink> <gerard@linuxfromscratch.org> -- L FS Project15 Organization/Leadership.</para></listitem>14 Beekmans</ulink> <gerard@linuxfromscratch.org> -- Linux-From-Scratch 15 initiator, LFS Project organizer.</para></listitem> 16 16 17 17 <listitem><para><ulink url="mailto:matthew@linuxfromscratch.org">Matthew … … 29 29 <listitem><para><ulink url="mailto:bruce@linuxfromscratch.org">Bruce 30 30 Dubbs</ulink> <bruce@linuxfromscratch.org> -- LFS Quality Assurance Team 31 Leader, BLFS Book editor.</para></listitem>31 leader, BLFS Book editor.</para></listitem> 32 32 33 33 <listitem><para><ulink url="mailto:alex@linuxfromscratch.org">Alex … … 37 37 <listitem><para><ulink url="mailto:markh@linuxfromscratch.org">Mark 38 38 Hymers</ulink> <markh@linuxfromscratch.org> -- CVS maintainer, BLFS Book 39 Creator, former LFS Book editor.</para></listitem>39 creator, former LFS Book editor.</para></listitem> 40 40 41 41 <listitem><para><ulink url="mailto:iwanek@linuxfromscratch.org">James 42 42 Iwanek</ulink> <iwanek@linuxfromscratch.org> -- System Administration 43 team member.</para></listitem>43 Team member.</para></listitem> 44 44 45 45 <listitem><para><ulink url="mailto:nicholas@linuxfromscratch.org">Nicholas … … 53 53 <listitem><para><ulink url="mailto:bill@linuxfromscratch.org">Bill 54 54 Maltby</ulink> <bill@linuxfromscratch.org> -- LFS Project 55 Organization/Leadership.</para></listitem>55 organizer.</para></listitem> 56 56 57 57 <listitem><para><ulink url="mailto:scot@linuxfromscratch.org">Scot Mc … … 60 60 61 61 <listitem><para><ulink url="mailto:ryan@linuxfromscratch.org">Ryan 62 Oliver</ulink> <ryan@linuxfromscratch.org> -- Testing Team Leader, co-63 c reator of PLFS.</para></listitem>62 Oliver</ulink> <ryan@linuxfromscratch.org> -- Testing Team leader, 63 co-creator of PLFS.</para></listitem> 64 64 65 65 <listitem><para><ulink url="mailto:jwrober@linuxfromscratch.org">James … … 68 68 69 69 <listitem><para><ulink url="mailto:greg@linuxfromscratch.org">Greg 70 Schafer</ulink> <greg@linuxfromscratch.org> -- Toolchain Maintainer,70 Schafer</ulink> <greg@linuxfromscratch.org> -- Toolchain maintainer, 71 71 LFS Book editor, co-creator of PLFS.</para></listitem> 72 72 … … 166 166 mirror.</para></listitem> 167 167 168 <listitem><para><ulink url="mailto:guido@primerelay.net">Guido Passet</ulink> 169 <guido@primerelay.net> -- nl.linuxfromscratch.org 170 mirror.</para></listitem> 171 168 172 <listitem><para><ulink url="mailto:miha@xuy.biz">Mikhail Pastukhov</ulink> 169 173 <miha@xuy.biz> -- lfs.130th.net mirror.</para></listitem> 170 171 <listitem><para><ulink url="mailto:guido@primerelay.net">Guido Passet</ulink>172 <guido@primerelay.net> -- nl.linuxfromscratch.org173 mirror.</para></listitem>174 174 175 175 <listitem><para><ulink url="mailto:jpolen@rackspace.com">Jeremy Polen</ulink> … … 234 234 235 235 <listitem><para><ulink url="mailto:strider@linux.com">Mark Stone</ulink> for 236 donating shadowfax, the linuxfromscratch.org server.</para></listitem> 236 donating <emphasis>shadowfax</emphasis>, the first linuxfromscratch.org 237 server.</para></listitem> 237 238 238 239 <listitem><para><ulink url="mailto:highos@linuxfromscratch.org">Jesse 239 240 Tie-Ten-Quee</ulink> <highos@linuxfromscratch.org> for donating a Yamaha 240 CDRW 8824E cdwriter.</para></listitem>241 CDRW 8824E CD-writer.</para></listitem> 241 242 242 243 <listitem><para>Countless other people on the various LFS mailinglists who are 243 making this book happen by giving their suggestions, testing the book and244 submitting bug reports.</para></listitem>244 making this book happen by giving their suggestions, submitting bug reports, 245 and throwing in their criticism.</para></listitem> 245 246 246 247 </itemizedlist> … … 257 258 Project maintainer.</para></listitem> 258 259 259 <listitem><para>Robert Briggs for originally donating the linuxfromscratch.org 260 and linuxfromscratch.com domain names.</para></listitem> 260 <listitem><para>Robert Briggs for originally donating the 261 <emphasis>linuxfromscratch.org</emphasis> and 262 <emphasis>linuxfromscratch.com</emphasis> domain names.</para></listitem> 261 263 262 264 <listitem><para><ulink url="mailto:ian@ichilton.co.uk">Ian Chilton</ulink> 263 <ian@ichilton.co.uk> for maintaining the Hints project </para></listitem>265 <ian@ichilton.co.uk> for maintaining the Hints project.</para></listitem> 264 266 265 267 <listitem><para><ulink url="mailto:gimli@linuxfromscratch.org">Marc … … 269 271 <listitem><para><ulink url="mailto:sklein@linuxfromscratch.org">Seth W. 270 272 Klein</ulink> <sklein@linuxfromscratch.org> -- LFS FAQ 271 Creator.</para></listitem>273 creator.</para></listitem> 272 274 273 275 <listitem><para><ulink url="mailto:garrett@linuxart.com">Garrett … … 281 283 <listitem><para><ulink url="mailto:Geert.Poels@skynet.be">Geert Poels</ulink> 282 284 <Geert.Poels@skynet.be> -- Original BLFS banner creator; based on the 283 originalLFS banner by Garrett LeSage.</para></listitem>284 285 <listitem><para><ulink url="mailto:bkenoah@oswd.org">Frank Skettino</ulink> 286 <bkenoah@oswd.org> -- Initial design of the old website - <ulink287 url="http://www.oswd.org">OSWD</ulink>.</para></listitem>285 LFS banner by Garrett LeSage.</para></listitem> 286 287 <listitem><para><ulink url="mailto:bkenoah@oswd.org">Frank Skettino</ulink> 288 <bkenoah@oswd.org> for the initial design of the old website -- have a 289 look at <ulink url="http://www.oswd.org/"/>.</para></listitem> 288 290 289 291 <listitem><para><ulink url="mailto:highos@linuxfromscratch.org">Jesse -
chapter01/changelog.xml
r1e66abe r35c2fa60 116 116 117 117 <listitem><para>September 26th, 2003 [jeremy]: Added new workaround for the 118 devpts problems </para></listitem>118 devpts problems.</para></listitem> 119 119 120 120 <listitem><para>September 24th, 2003 [greg]: Various changes across the board … … 128 128 129 129 <listitem><para>September 22nd, 2003 [jeremy]: Added net-tools patch to fix 130 mii-tool compilation </para></listitem>130 mii-tool compilation.</para></listitem> 131 131 132 132 <listitem><para>September 22nd, 2003 [jwrober]: Chapter 5 - Updated the Why … … 173 173 page to match the website.</para></listitem> 174 174 175 <listitem><para>September 17th, 2003 [jeremy]: Upgraded File to 4.04 </para></listitem>175 <listitem><para>September 17th, 2003 [jeremy]: Upgraded File to 4.04.</para></listitem> 176 176 177 177 <listitem><para>September 17th, 2003 [jeremy]: Chapter 6 - changed 2 of the -
chapter01/how.xml
r1e66abe r35c2fa60 3 3 <?dbhtml filename="how.html" dir="chapter01"?> 4 4 5 <para>You are going to build your LFS system by using a previously installed 6 Linux distribution such as Debian, Mandrake, Red Hat, etc. The existing Linux 7 system (host) will be used as a starting point, because you will need programs 8 like a compiler, linker, text editor, and other development tools to build the 9 new system. Ordinarily, the required tools are available by default if you 10 selected <quote>development</quote> as one of your installation options when 11 you installed your Linux distribution.</para> 5 <para>You are going to build your LFS system by using a previously installed 6 Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This existing 7 Linux system (the host) will be used as a starting point, because you will need 8 programs like a compiler, linker and shell to build the new system. Normally 9 all the required tools are available if you selected <quote>development</quote> 10 as one of the options when you installed your distribution.</para> 12 11 13 <para> After you have downloaded the packages that make up an LFS system, you14 will create a new Linux native partition and filesystem. This new Linux 15 partition and filesystem is where your new LFS system will be compiled and 16 installed onto.</para>12 <para>In Chapter 3 you will first create a new Linux native partition and 13 filesystem, the place where your new LFS system will be compiled and installed. 14 Then in Chapter 4 you download all the packages and patches required to build 15 an LFS system, and store them on the new filesystem.</para> 17 16 18 17 <para>Chapter 5 will then discuss the installation of a number of packages that … … 69 68 70 69 <para>When all the software from Chapter 6 is installed, the temporary tools 71 built in Chapter 5 will be removed. Chapters 7, 8 and 9 will finalize the72 installation. The bootscripts are setup in Chapter 7, the kernel and boot 73 loader are setup in Chapter 8 and Chapter 9 has some pointers to help you after 74 you finish with the book. Then, finally, you reboot your computer into your75 new LFS system.</para>70 built in Chapter 5 are removed. In Chapters 7, 8 and 9 the installation will 71 then be finalized. The bootscripts are set up in Chapter 7, the kernel and 72 bootloader are set up in Chapter 8, and Chapter 9 has some pointers to help 73 you after you finish the book. Then, finally, you're ready to reboot your 74 computer into your new LFS system.</para> 76 75 77 76 <para>This is the process in a nutshell. Detailed information on the steps you -
chapter02/askforhelp.xml
r1e66abe r35c2fa60 94 94 of the package, we may encourage you to run. Sometimes packages will 95 95 generate false or expected failures. If you encounter these, you can check 96 the LFS Wiki page at <ulink url="http://wiki.linuxfromscratch.org "/> to see96 the LFS Wiki page at <ulink url="http://wiki.linuxfromscratch.org/"/> to see 97 97 whether we have already investigated and noted them. If we already know 98 98 about them, then usually there is no need to be concerned.</para> -
chapter04/chapter04.xml
r1e66abe r35c2fa60 18 18 19 19 <para>All the URLs, when possible, refer to the project's page at 20 <ulink url="http://www.freshmeat.net" >Freshmeat.net</ulink>. The Freshmeat20 <ulink url="http://www.freshmeat.net"/>. The Freshmeat 21 21 pages will give you easy access to the official download sites as well as 22 22 project websites, mailinglists, FAQs, Changelogs and more.</para> -
chapter05/chapter05.xml
r1e66abe r35c2fa60 1 1 <chapter id="chapter05"> 2 <title> Preparing the LFSsystem</title>2 <title>Constructing a temporary system</title> 3 3 <?dbhtml filename="chapter05.html" dir="chapter05"?> 4 4 -
chapter05/coreutils-inst.xml
r1e66abe r35c2fa60 23 23 <listitem><para><userinput>RUN_EXPENSIVE_TESTS=yes</userinput>: This tells the 24 24 test suite to run several additional tests that are considered relatively 25 expensive on some platforms. Ho vever, they are generally not a problem on25 expensive on some platforms. However, they are generally not a problem on 26 26 Linux.</para></listitem> 27 27 </itemizedlist> -
chapter05/gcc-pass2-inst.xml
r1e66abe r35c2fa60 22 22 case there is no point in running the test suites for GCC and Binutils until you 23 23 are able to resolve the issue. You can consult the LFS Wiki at 24 <ulink url="http://wiki.linuxfromscratch.org "/> for more information on how to24 <ulink url="http://wiki.linuxfromscratch.org/"/> for more information on how to 25 25 get PTYs working.</para> 26 26 -
chapter05/introduction.xml
r1e66abe r35c2fa60 33 33 see all kinds of compiler warnings scroll by on your screen. These are 34 34 normal and can be safely ignored. They are just what they say they are: 35 warnings -- mostly about improper, but not illegal, use of the C or C++35 warnings -- mostly about deprecated, but not invalid, use of the C or C++ 36 36 syntax. It's just that C standards have changed rather often and some 37 37 packages still use the older standard, which is not really a problem.</para> -
chapter05/tcl-inst.xml
r1e66abe r35c2fa60 35 35 36 36 <para>Sometimes, package test suites will give false failures. You can 37 consult the LFS Wiki at <ulink url="http://wiki.linuxfromscratch.org "/>37 consult the LFS Wiki at <ulink url="http://wiki.linuxfromscratch.org/"/> 38 38 to verify that these failures are normal. This applies to all tests 39 39 throughout the book.</para> -
chapter06/vim.xml
r1e66abe r35c2fa60 6 6 Estimated required disk space: &vim-compsize;</screen> 7 7 8 <sect2> 9 <title>Alternatives to Vim</title> 10 11 <para>If you prefer another editor -- like Emacs, Joe, or Nano -- to Vim, 12 have a look at <ulink url="&blfs-root;view/cvs/postlfs/editors.html"/> for 13 suggested installation instructions.</para> 14 15 </sect2> 16 8 17 &aa-vim-shortdesc; 9 &aa-vim-alt;10 18 &aa-vim-dep; 11 19 &c6-vim-inst;
Note:
See TracChangeset
for help on using the changeset viewer.