Changeset ec64d28
- Timestamp:
- 12/19/2012 07:57:20 PM (12 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 12.2, 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, gimp3, 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/for-12.3, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/spidermonkey128, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- b3aacc0
- Parents:
- 4abd884
- Files:
-
- 21 edited
Legend:
- Unmodified
- Added
- Removed
-
general/genlib/genlib.xml
r4abd884 rec64d28 41 41 42 42 <para>There are certain libraries which nearly <emphasis>everyone</emphasis> 43 will need at some point. In this chapter we list these and some othersand44 explainwhy you may want to install them.</para>43 will need at some point. In this chapter these and some others are listed and 44 it is explained why you may want to install them.</para> 45 45 46 46 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="apr.xml"/> -
general/genlib/libatomic_ops.xml
r4abd884 rec64d28 104 104 105 105 <para> 106 <command>sed -i 's#AC_PROG_RANLIB ...</command>: These seds massage the 107 autotool files so that a shared library is built, the tests pass and the 108 docs are installed where we want. 106 <command>sed -i 's#AC_PROG_RANLIB ...</command>: These 107 <command>sed</command>s massage the autotool files so that a shared 108 library is built, the tests pass, and the docs are installed in an 109 appropriate directory. 109 110 </para> 110 111 111 112 <para> 112 <command>autoreconf -i</command>: This regenerates the configure script 113 and the Makefile.in files and installs a missing file. 113 <command>autoreconf -i</command>: This regenerates the 114 <command>configure</command> script and the <filename>Makefile.in</filename> 115 files and installs a missing file. 114 116 </para> 115 117 -
gnome/core/gnome-session.xml
r4abd884 rec64d28 139 139 140 140 <para> 141 If you are not using <application> gdm</application> to start your141 If you are not using <application>GDM</application> to start your 142 142 <application>GNOME</application> desktop, you will need to invoke 143 143 <command>gnome-session</command> <emphasis>instead of</emphasis> invoking … … 153 153 daemons and either <application>Metacity</application> or 154 154 <application>gnome-shell</application>. A desktop manager such as 155 <application> gdm</application> will invoke <application>ConsoleKit</application>155 <application>GDM</application> will invoke <application>ConsoleKit</application> 156 156 before the window manager, but if you use <command>startx</command> the first 157 157 invocation after booting may fail because the daemon is not already running, 158 so we will invoke itfirst.158 so it is invoked first. 159 159 </para> 160 160 … … 164 164 backup your current <filename>~/.xinitrc</filename> before proceeding. 165 165 Note that you will be able to invoke <application>GNOME Terminal</application> 166 from the menu, so there is no reason to invoke xterm here. Create a new167 <filename>.xinitrc</filename> using this command:166 from the menu, so there is no reason to invoke <command>xterm</command> here. 167 Create a new <filename>.xinitrc</filename> using this command: 168 168 </para> 169 169 -
introduction/important/building-notes.xml
r4abd884 rec64d28 17 17 18 18 <para>Those people who have built an LFS system may be aware 19 of the general principles of downloading and unpacking software. We will20 however repeat some of that informationhere for those new to building19 of the general principles of downloading and unpacking software. Some 20 of that information is repeated here for those new to building 21 21 their own software.</para> 22 22 23 23 <para>Each set of installation instructions contains a URL from which you 24 can download the package. We do however keep a selection of patches25 available via HTTP. These are referenced as needed in the installation26 inst ructions.</para>24 can download the package. The patches; however, are stored on the LFS 25 servers and are available via HTTP. These are referenced as needed in the 26 installation instructions.</para> 27 27 28 28 <para>While you can keep the source files anywhere you like, we assume that -
introduction/important/libraries.xml
r4abd884 rec64d28 29 29 systems they are the only type available.</para> 30 30 31 <para>On almost all Linux platforms we also haveshared libraries31 <para>On almost all Linux platforms there are also shared libraries 32 32 (libfoo.so) - one copy of the library is loaded into virtual memory, and 33 33 shared by all the programs which call any of its functions. This is space -
introduction/important/locale-issues.xml
r4abd884 rec64d28 282 282 # Non-UTF-8 manual page is OK 283 283 iconv -f UTF-8 -t UTF-8 "$a" >/dev/null 2>&1 || continue 284 # If we got here, we foundUTF-8 manual page, bad.284 # Found a UTF-8 manual page, bad. 285 285 echo "UTF-8 manual page: $a" >&2 286 286 done -
introduction/welcome/packages.xml
r4abd884 rec64d28 30 30 31 31 <para>We would like to ask a favor, however. Although this is a public 32 resource for you to use, we do not want toabuse it. We have already had one32 resource for you to use, please do not abuse it. We have already had one 33 33 unthinking individual download over 3 GB of data, including multiple copies of 34 34 the same files that are placed at different locations (via symlinks) to make -
introduction/welcome/which.xml
r4abd884 rec64d28 19 19 followed in a linear manner. This is because LFS provides instructions 20 20 on how to create a base system which is capable of turning into anything 21 from a web server to a multimedia desktop system. BLFS is where we try21 from a web server to a multimedia desktop system. BLFS attempts 22 22 to guide you in the process of going from the base system to your intended 23 23 destination. Choice is very much involved.</para> -
multimedia/libdriv/libdvdnav.xml
r4abd884 rec64d28 89 89 90 90 <para><command>./autogen.sh</command>: This package does not come with the 91 normal configure script, so we need to use the <command>autogen.sh</command> 92 script to generate and run <command>configure</command>.</para> 91 normal <command>configure</command> script, so 92 the <command>autogen.sh</command> script is used to generate and run 93 <command>configure</command>.</para> 93 94 </sect2> 94 95 -
multimedia/libdriv/libdvdread.xml
r4abd884 rec64d28 83 83 84 84 <para><command>./autogen.sh</command>: This package does not come with the 85 normal configure script, so we need to use the <command>autogen.sh</command> 86 script to generate and run <command>configure</command>.</para> 85 normal <command>configure</command> script, so the 86 <command>autogen.sh</command> script is used to generate and run 87 <command>configure</command>.</para> 87 88 </sect2> 88 89 -
networking/netutils/wicd.xml
r4abd884 rec64d28 132 132 <sect2 role="commands"> 133 133 <title>Command Explanations</title> 134 <para><command>sed -i '/wpath...</command>: The sed prevents installation of logrotate 135 and systemd configuration files. You may omit it if you use these utilities.</para> 136 <para><option>--no-install-kde</option>: Prevent installation of 134 135 <para><command>sed -i '/wpath...</command>: This <command>sed</command> 136 prevents installation of <command>logrotate</command> and systemd 137 configuration files. You may omit it if you use these utilities.</para> 138 139 <para><option>--no-install-kde</option>: Prevent installation of an 137 140 autostart desktop file for KDE. If you use KDE, you should instead install the 138 141 <ulink url="http://projects.kde.org/projects/extragear/network/wicd-kde">Wicd KDE Client</ulink>. 139 142 </para> 143 140 144 <para><option>--no-install-acpi</option>: Prevent installation of 141 suspend and resume scripts for acpid. Omit this option if you use acpid.</para> 145 <command>suspend</command> and <command>resume</command> scripts for acpid. 146 Omit this option if you use acpid.</para> 147 142 148 <para><option>--no-install-pmutils</option>: Prevent installation of hooks for 143 149 pm-utils. Omit this option if you use pm-utils.</para> 150 144 151 <para><option>--no-install-init</option>: Prevent installation of any init scripts, 145 as we install our own bootscript.</para> 152 as a bootscript is installed later in the instructions.</para> 153 146 154 <para><option>--wicdgroup=<replaceable><group></replaceable></option>: 147 155 The group that will have permission to use the Wicd client (default is the … … 186 194 frontends. If you are only going to use Wicd from command-line, you can configure 187 195 it using the configuration files in <filename>/etc/wicd</filename>. For a list of 188 available options, take alook at the man-pages for: wicd-manager-settings.conf,196 available options, look at the man-pages for: wicd-manager-settings.conf, 189 197 wicd-wired-settings.conf and wicd-wireless-settings.conf.</para> 190 198 -
postlfs/config/bootdisk.xml
r4abd884 rec64d28 30 30 used as a rescue device: floppy, cdrom, usb drive, or even a network card. 31 31 Which one you use depends on your hardware and your BIOS. In the past, 32 we usually thought of rescue device asa floppy disk. Today, many32 a rescue device was thought to be a floppy disk. Today, many 33 33 systems do not even have a floppy drive.</para> 34 34 -
postlfs/config/inputrc.xml
r4abd884 rec64d28 63 63 <literal># Begin /etc/inputrc 64 64 65 # Make sure we don't output everything on the 1line65 # Make sure everything is not output to one line 66 66 set horizontal-scroll-mode Off 67 67 -
postlfs/config/profile.xml
r4abd884 rec64d28 273 273 274 274 <screen role="root"><userinput>cat > /etc/profile.d/umask.sh << "EOF" 275 <literal># By default we want the umask to getset.275 <literal># By default, the umask should be set. 276 276 if [ "$(id -gn)" = "$(id -un)" -a $EUID -gt 99 ] ; then 277 277 umask 002 -
postlfs/filesystems/aboutlvm.xml
r4abd884 rec64d28 58 58 </variablelist> 59 59 60 <para>To give a concrete example, suppose that wehave two 2 TB disks.60 <para>To give a concrete example, suppose that you have two 2 TB disks. 61 61 Also suppose a really large amount of space is required for a very large database, 62 62 mounted on <filename class='directory'>/srv/mysql</filename>. This is what -
postlfs/filesystems/aboutraid.xml
r4abd884 rec64d28 114 114 sdd2: 300 GB fd Linux raid auto /home (RAID 5) /dev/md2 </literal></screen> 115 115 116 <para>Is this arrangement, we are creating a separate boot partitionas the116 <para>Is this arrangement, a separate boot partition is created as the 117 117 first small RAID array and a root filesystem as the secong RAID array, 118 118 both mirrored. The third partition is a large (about 1TB) array for the 119 119 <filename class='directory'>/home</filename> directory. This provides 120 120 an ability to stripe data across multiple devices, improving speed for 121 botih reading and writing large files. Finally, we create a fourth array121 botih reading and writing large files. Finally, a fourth array is created 122 122 that concatenates two partitions into a larger device.</para> 123 123 -
postlfs/virtualization/qemu-kvm.xml
r4abd884 rec64d28 179 179 180 180 <para>To install an operating system, download an iso of your choice or use 181 a pre-intalled cdrom device. For the purposes of this example, we willuse181 a pre-intalled cdrom device. For the purposes of this example, use 182 182 Fedora 16 that is downloaded as 183 183 <filename>Fedora-16-x86_64-Live-LXDE.iso</filename> in the current -
pst/printing/gs.xml
r4abd884 rec64d28 248 248 JPEG 2000 files <!-- I can't get it to compile using a system installed 249 249 version of openjpeg. It seems the ghostscript version has been heavily 250 modified... --> so we can all remove the jasper source. The default color250 modified... --> so jasper source can be removed. The default color 251 251 management system is now <application>lcms2</application> so the 252 252 <application>lcms</application> source is not needed. … … 260 260 261 261 <para> 262 <parameter>LIBS=-lz</parameter>: We use the LIBS variable to tell the263 linker (ld) to link against the system installed262 <parameter>LIBS=-lz</parameter>: Use the <envar>LIBS</envar> variable to 263 tell the linker (ld) to link against the system installed 264 264 <application>zlib</application>. 265 265 </para> -
xsoft/graphweb/firefox.xml
r4abd884 rec64d28 317 317 318 318 <para> 319 <command>ln -sfv ... /usr/bin/firefox</command>: this puts a symbolic link 320 to the <command>firefox</command> executable in your ${PATH}. 321 </para> 322 323 <para> 324 <command>mkdir -p /usr/lib/mozilla/plugins</command>: this checks 319 <command>ln -sfv ... /usr/bin/firefox</command>: This puts a symbolic link 320 to the <command>firefox</command> executable in your <envar>PATH</envar> 321 variable. 322 </para> 323 324 <para> 325 <command>mkdir -p /usr/lib/mozilla/plugins</command>: This checks 325 326 that <filename class="directory">/usr/lib/mozilla/plugins</filename> 326 327 exists. … … 328 329 329 330 <para> 330 <command>ln -sv ... /usr/lib/firefox-&firefox-version;</command>: this331 <command>ln -sv ... /usr/lib/firefox-&firefox-version;</command>: This 331 332 makes a symbolic link to 332 333 <filename class="directory">/usr/lib/mozilla/plugins</filename>. It's not 333 really needed, <application>Firefox</application> checks334 really needed, as <application>Firefox</application> checks 334 335 <filename class="directory">/usr/lib/mozilla/plugins</filename> by 335 default, we make the symbolic linkto keep all the plugins installed in336 default, but the symbolic link is made to keep all the plugins installed in 336 337 one folder. 337 338 </para> -
xsoft/office/libreoffice.xml
r4abd884 rec64d28 315 315 <command>./download</command>: The build process runs the 316 316 <command>download</command> script which downloads some 470 MB of 317 tarballs. We run the download scriptto get it out of the way at the318 start so we can make a backup copy of the downloaded files.317 tarballs. The download script is ran to get it out of the way at the 318 start so a backup copy of the downloaded files are on hand. 319 319 </para> 320 320 -
xsoft/other/rox-filer.xml
r4abd884 rec64d28 210 210 211 211 <para> 212 That works fine for mounting, but to unmount it we need to runthe213 command <command>fusermount -u ${MOUNTPOINT}</command> . You could set212 That works fine for mounting, but to unmount it the 213 command <command>fusermount -u ${MOUNTPOINT}</command> is ran. You could set 214 214 that as your default umount command in your rox preferences, but you 215 215 would then be unable to unmount any normal mountpoints (that need 216 umount). What we need is a scriptthat will unmount a Fuse mountpoint216 umount). A script is needed that will unmount a Fuse mountpoint 217 217 with <command>fusermount -u ${MOUNTPOINT}</command> and everything else 218 218 with <command>umount</command>. As the
Note:
See TracChangeset
for help on using the changeset viewer.