Changeset 14377f4
- Timestamp:
- 09/25/2012 06:59:37 PM (12 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, 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, 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:
- f5976ac
- Parents:
- a764ff2
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/pkgmgt.xml
ra764ff2 r14377f4 219 219 commercial distributions. Examples of package managers that follow this 220 220 approach are RPM (which, incidentally, is required by the <ulink 221 url="http:// www.linux-foundation.org/en/Specifications">Linux221 url="http://refspecs.linuxfoundation.org/lsb.shtml">Linux 222 222 Standard Base Specification</ulink>), pkg-utils, Debian's apt, and 223 223 Gentoo's Portage system. A hint describing how to adopt this style of -
prologue/architecture.xml
ra764ff2 r14377f4 11 11 <title>LFS Target Architectures</title> 12 12 13 <para>The primary target architecture of LFS is the 32-bit Intel CPU. If you 14 have not built an LFS system before, you should probably start with that 15 target. The 32-bit architecture is the most widely supported Linux system and 16 is most compatible with both open source and proprietary software.</para> 17 18 <para>On the other hand, the instructions in this book are known to work, with 19 some modifications, with both Power PC and 64-bit AMD/Intel CPUs. To build a 13 <para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit) 14 and x86_64 (64-bit) CPUs. On the other hand, the instructions in this book are 15 also known to work, with some modifications, with the Power PC CPU. To build a 20 16 system that utilizes one of these CPUs, the main prerequisite, in addition to 21 17 those on the next few pages, is an existing Linux system such as an earlier LFS … … 48 44 project for this advanced topic.</para> 49 45 50 <para>There is one last comment about 64-bit systems. There are some packages 51 that cannot currently be built in a "pure" 64-bit system or require specialized 52 build instructions. Generally, these packages have some embedded 32-bit 53 specific assembly language instructions that fail when building on a 64-bit 54 system. This includes some Xorg drivers from <ulink 55 url="http://www.linuxfromscratch.org/blfs/view/svn/">Beyond Linux From Scratch 56 (BLFS)</ulink>. Many of these problems can be worked around, but may require 57 some specialized procedures or patches.</para> 46 <para>There is one last comment about 64-bit systems. There are some older 47 packages that cannot currently be built in a "pure" 64-bit system or require 48 specialized build instructions. Generally, these packages have some embedded 49 32-bit specific assembly language instructions that fail when building on a 50 64-bit system. This includes some Xorg drivers for some legacy video cards at 51 <ulink url="http://xorg.freedesktop.org/releases/individual/driver/"> 52 http://xorg.freedesktop.org/releases/individual/driver/</ulink>. Many of these 53 problems can be worked around, but may require some specialized procedures or 54 patches.</para> 58 55 59 56 </sect1> -
udev-lfs/contrib/debian/write_cd_aliases
ra764ff2 r14377f4 1 1 #!/bin/sh -e 2 3 # Updated for LFS by B. Dubbs, 2012-09-23 4 # Fix RULES_LOCK location 5 2 6 3 7 RULES_FILE="/etc/udev/rules.d/82-persistent-cd.rules" … … 5 9 ############################################################################## 6 10 lock_rules_file() { 7 RULES_LOCK="/ dev/.udev/.lock-${RULES_FILE##*/}"11 RULES_LOCK="/run/udev/lock-${RULES_FILE##*/}" 8 12 9 retry=30 13 if [ ! -d /run/udev/ ]; then 14 echo "write_cd_aliases: /run/udev does not exist!" >&2 15 exit 2 16 fi 17 18 retry=10 10 19 while ! mkdir $RULES_LOCK 2> /dev/null; do 11 20 if [ $retry -eq 0 ]; then
Note:
See TracChangeset
for help on using the changeset viewer.