mirror of
https://github.com/Zeckmathederg/glfs.git
synced 2025-01-24 23:32:12 +08:00
more corner sweeping
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@838 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
parent
2537abaea6
commit
036393e17a
@ -8,7 +8,7 @@
|
||||
|
||||
<sect3><title>Configuration Information</title>
|
||||
|
||||
<para>Most ncftp configuration is done whilst in the program and the
|
||||
<para>Most ncftp configuration is done while in the program and the
|
||||
configuration files are dealt with automatically. One exception to this
|
||||
is <filename>~/.ncftp/prefs_v3</filename>. There are various options to
|
||||
alter in there, including:</para>
|
||||
|
@ -1,7 +1,8 @@
|
||||
<sect2>
|
||||
<title>Command explanations</title>
|
||||
|
||||
<para><userinput>GCC_VERSION=...</userinput> : STLport needs the location of the c++ headers, which are installed in
|
||||
<para><userinput>GCC_VERSION=...</userinput> : STLport needs the
|
||||
location of the C++ headers, which are installed in
|
||||
<userinput>/usr/include/c++/$GCC_VERSION</userinput>
|
||||
if installed as per the instructions in LFS.</para>
|
||||
<para><userinput>sed -e ...</userinput> : Replace the location where STLport
|
||||
|
@ -8,4 +8,4 @@
|
||||
<!ENTITY STLport-version "4.5.3">
|
||||
<!ENTITY STLport-download-http "http://www.stlport.org/archive/STLport-&STLport-version;.tar.gz">
|
||||
<!ENTITY STLport-download-ftp "">
|
||||
<!ENTITY STLport-size "25 MB">
|
||||
<!ENTITY STLport-size "728 KB">
|
||||
|
@ -19,7 +19,7 @@ legal issue with LZW compression (which Unisys claims a patent on).
|
||||
Reading gifs is not a problem as the uncompression routines do not seem
|
||||
to be limited in this way. Note that this has in the past been
|
||||
disputed. The best way to avoid this whole mess is to simply use
|
||||
libungif for looking at gif images on the web, whilst in any pages which
|
||||
libungif for looking at gif images on the web, while in any pages which
|
||||
you design, use the open source png format instead (which uses, not
|
||||
surprisingly, the libpng library) which has no patent issues at
|
||||
all.</para>
|
||||
|
@ -32,7 +32,7 @@ downloading the source also download the mozilla headers package available at
|
||||
the same location.
|
||||
</para>
|
||||
|
||||
<para>Download the patches for j2sdk source from <ulink url="&hfile-root;"/>
|
||||
<para>Download the patches for j2sdk source from <ulink url="&hfile-root;"/>.
|
||||
</para>
|
||||
|
||||
<para>If you have difficulties in building the jdk, check out the javafromscratch
|
||||
|
@ -14,7 +14,7 @@ you can download the package. We do however keep a selection of patches
|
||||
available via http/ftp. These are referenced as needed in the
|
||||
installation instructions.</para>
|
||||
|
||||
<para>Whilst you can keep the source tarballs anywhere you like, we
|
||||
<para>While you can keep the source tarballs anywhere you like, we
|
||||
assume that you have unpacked them and unzipped any required patches
|
||||
into <filename>/usr/src</filename>.</para>
|
||||
|
||||
|
@ -8,7 +8,7 @@ contributions toward the BLFS and LFS projects:</para>
|
||||
<itemizedlist>
|
||||
|
||||
<listitem><para>All those people listed on the Credits page for submitting
|
||||
patches, instructions and corrections to the book. The current editor would
|
||||
patches, instructions and corrections to the book. The former editor would
|
||||
especially like to thank Bruce, Larry and Billy for their enormous inputs to the
|
||||
project.</para></listitem>
|
||||
|
||||
|
@ -22,7 +22,7 @@ to turn next. This deals with not just configuration but also Security
|
||||
linkend="postlfs-filesystems"/>), Editors (<xref
|
||||
linkend="postlfs-editors"/>) and Shells (<xref linkend="postlfs-shells"/>).
|
||||
Indeed, you may wish to reference certain parts of this chapter (especially
|
||||
the sections on Editors and Filesystems) whilst building your LFS system.</para>
|
||||
the sections on Editors and Filesystems) while building your LFS system.</para>
|
||||
|
||||
<para>Following these basic items, most people will want to at least browse
|
||||
through the <xref linkend="general"/> part of the book. This part contains
|
||||
|
@ -11,6 +11,6 @@ Estimated Disk space required: &nas-buildsize;</screen>
|
||||
transport system. It can be described as the audio equivalent of an X
|
||||
server.</para>
|
||||
|
||||
<para>Download the bison patch from <ulink url="&hfile-root;"/></para>
|
||||
<para>Download the nas patch from <ulink url="&hfile-root;"/>.</para>
|
||||
|
||||
</sect2>
|
||||
|
@ -31,10 +31,10 @@ only need to set up the minimum directories.</para>
|
||||
<para>Next, we will set up the device files. I use devfs on my system, so
|
||||
the following command works well, as I only have the devices I use
|
||||
anyway. If you used MAKEDEV to create your devices, you'll want to
|
||||
trim the /mnt/loop1/dev directory to reclaim the inode space wasted
|
||||
by all of the devices in the dev directory you don't use.</para>
|
||||
trim the <filename>/mnt/loop1/dev</filename> directory to reclaim the inode space wasted
|
||||
by all of the devices in the <filename>dev</filename> directory you don't use.</para>
|
||||
<para><screen><userinput>cp -dpR /dev/* /mnt/loop1/dev</userinput></screen></para>
|
||||
<para>Now to tend to the /etc directory. To start, all we will do is use
|
||||
<para>Now to tend to the <filename>/etc</filename> directory. To start, all we will do is use
|
||||
the passwd and group file that worked for our static chroot environment
|
||||
when we built LFS. We'll also copy the startup scripts over and a few other files
|
||||
that serve well as starting points.</para>
|
||||
@ -60,12 +60,14 @@ EOF</userinput></screen>
|
||||
|
||||
To prevent automatic mounting of hard drive partitions,
|
||||
make sure to add the noauto option in their fstab entry. Also, add the
|
||||
following entries to the /mnt/loop1/etc/fstab to assist with mounting our
|
||||
following entries to the <filename>/mnt/loop1/etc/fstab</filename> to assist with mounting our
|
||||
floppy and the ram image</para>
|
||||
<para><screen>/dev/ram0 / ext2 defaults
|
||||
/dev/fd0 / ext2 defaults</screen></para>
|
||||
|
||||
<para>Next, we will install <ulink url="http://www.busybox.net/downloads/busybox-0.60.4.tar.bz2">busybox</ulink> onto the image. Busybox incorporates many of the *nix functions into a single small executable file.</para>
|
||||
<para>Next, we will install <ulink
|
||||
url="http://www.busybox.net/downloads/busybox-0.60.4.tar.bz2">busybox</ulink>
|
||||
onto the image. Busybox incorporates many of the unix functions into a single small executable file.</para>
|
||||
<screen><userinput>make &&
|
||||
make PREFIX=/mnt/loop1 install &&
|
||||
cp -ax /var/utmp /mnt/loop1/var &&
|
||||
@ -88,7 +90,7 @@ strip --strip-deb /tmp/ld-linux.so.2 /tmp/libc.so.6 /tmp/libdl.so.2 &&
|
||||
mv /tmp/ld-linux.so.2 /tmp/libc.so.6 /tmp/libdl.so.2 /mnt/loop1/lib/</userinput></screen>
|
||||
<para>
|
||||
We will also need to set up an rc script to handle the devfsd startup.
|
||||
Put this in <filename>/mnt/loop1/etc/init.d/rcS</filename></para>
|
||||
Put this in <filename>/mnt/loop1/etc/init.d/rcS</filename>.</para>
|
||||
<screen>#!/bin/sh
|
||||
mount -t devfs devfs /dev
|
||||
/sbin/devfsd /dev</screen>
|
||||
@ -99,7 +101,7 @@ make the smallest possible compressed image.</para>
|
||||
<screen><userinput>umount /mnt/loop1 && dd if=/tmp/rfloppy bs=1k | gzip -v9 > rootfs.gz</userinput></screen>
|
||||
<screen><userinput>ls -l rootfs.gz</userinput> to make sure it will fit on the diskette.</screen>
|
||||
<para>
|
||||
make a custom kernel that is optimized for size. Include only those features
|
||||
Make a custom kernel that is optimized for size. Include only those features
|
||||
you will need to rescue your system. no sense in building in support for things
|
||||
like xfree86 dri, etc, as most rescues are performed from the command prompt.
|
||||
</para>
|
||||
@ -112,8 +114,8 @@ like xfree86 dri, etc, as most rescues are performed from the command prompt.
|
||||
|
||||
<para>In this example the rescueimage(KERNEL) was 429+1 blocks in size.
|
||||
We will remember this for the next command. We now write the root file
|
||||
system right after the kernel on the floppy. by doing 16384+429+1=
|
||||
16814 </para>
|
||||
system right after the kernel on the floppy by doing 16384+429+1=
|
||||
16814.</para>
|
||||
<screen><userinput>rdev -r /dev/floppy/0 16814</userinput></screen>
|
||||
|
||||
|
||||
|
@ -8,7 +8,8 @@ help create an environment to run in. Each file has a specific use and
|
||||
may affect login and interactive environments differently.</para>
|
||||
|
||||
<para>An interactive login shell is started after a successful login by
|
||||
<filename>/bin/login</filename> by reading the /etc/passwd file. An
|
||||
<filename>/bin/login</filename> by reading the
|
||||
<filename>/etc/passwd</filename> file. An
|
||||
interactive non-login shell is started at the command line (e.g.
|
||||
[prompt]$<userinput>/bin/bash</userinput>). A non-interactive shell is
|
||||
usually present when a shell script is running. It is non-interactive
|
||||
|
@ -4,7 +4,7 @@
|
||||
<screen>shadow requires:
|
||||
<xref linkend="Linux_PAM"/></screen>
|
||||
|
||||
<para>Download the patch for shadow from <ulink url="&hfile-root;"/></para>
|
||||
<para>Download the patch for shadow from <ulink url="&hfile-root;"/>.</para>
|
||||
|
||||
<para>Reinstall shadow by running the following commands:</para>
|
||||
|
||||
|
@ -28,8 +28,8 @@ the simple static IP setup given in the main LFS book.</para></sect2>
|
||||
bulk of this part.</para></sect2>
|
||||
|
||||
<sect2><title>Part VI - Server Networking</title>
|
||||
<para>Here we deal with setting up mail and other servers (such as SSH, CVS
|
||||
etc).</para></sect2>
|
||||
<para>Here we deal with setting up mail and other servers (such as SSH,
|
||||
CVS, etc.).</para></sect2>
|
||||
|
||||
<sect2><title>Part VII - Content Serving</title>
|
||||
<para>In this part we deal with databases and web server software (including
|
||||
@ -45,7 +45,7 @@ it, this part covers it.</para></sect2>
|
||||
|
||||
<sect2><title>Part X - Gnome</title>
|
||||
<para>Gnome is the main alternative to KDE in the Desktop Environment arena
|
||||
and we cover both gnome-1.4 and gnome-2.0 here.</para></sect2>
|
||||
and we cover both gnome-1.4 and gnome-2.2 here.</para></sect2>
|
||||
|
||||
<sect2><title>Part XI - X Software</title>
|
||||
<para>Office programs and graphical web browsers are important to most
|
||||
|
Loading…
Reference in New Issue
Block a user