gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update LFS target architectures.

Browse Source 
Fix a url in pkgmgfor LFS.
Tweak a debian udev script for LFS.


git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9998 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Bruce Dubbs 2012-09-25 18:59:37 +00:00
parent a764ff2e68
commit 14377f4ac0
3 changed files with 24 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chapter06/pkgmgt.xml
View File

@ -218,7 +218,7 @@ make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput></screen>
<para>This approach is used by most of the package managers found in the <para>This approach is used by most of the package managers found in the
commercial distributions. Examples of package managers that follow this commercial distributions. Examples of package managers that follow this
approach are RPM (which, incidentally, is required by the <ulink approach are RPM (which, incidentally, is required by the <ulink
url="http://www.linux-foundation.org/en/Specifications">Linux url="http://refspecs.linuxfoundation.org/lsb.shtml">Linux
Standard Base Specification</ulink>), pkg-utils, Debian's apt, and Standard Base Specification</ulink>), pkg-utils, Debian's apt, and
Gentoo's Portage system. A hint describing how to adopt this style of Gentoo's Portage system. A hint describing how to adopt this style of
package management for LFS systems is located at <ulink package management for LFS systems is located at <ulink

27
prologue/architecture.xml
View File

@ -10,13 +10,9 @@
<title>LFS Target Architectures</title> <title>LFS Target Architectures</title>
<para>The primary target architecture of LFS is the 32-bit Intel CPU. If you <para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit)
have not built an LFS system before, you should probably start with that and x86_64 (64-bit) CPUs. On the other hand, the instructions in this book are
target. The 32-bit architecture is the most widely supported Linux system and also known to work, with some modifications, with the Power PC CPU. To build a
is most compatible with both open source and proprietary software.</para>
<para>On the other hand, the instructions in this book are known to work, with
some modifications, with both Power PC and 64-bit AMD/Intel CPUs. To build a
system that utilizes one of these CPUs, the main prerequisite, in addition to system that utilizes one of these CPUs, the main prerequisite, in addition to
those on the next few pages, is an existing Linux system such as an earlier LFS those on the next few pages, is an existing Linux system such as an earlier LFS
installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets
@ -47,14 +43,15 @@ instructions needed for a straightforward base Linux system. You can refer to
the <ulink url="http://trac.cross-lfs.org/">Cross Linux From Scratch</ulink> the <ulink url="http://trac.cross-lfs.org/">Cross Linux From Scratch</ulink>
project for this advanced topic.</para> project for this advanced topic.</para>
<para>There is one last comment about 64-bit systems. There are some packages <para>There is one last comment about 64-bit systems. There are some older
that cannot currently be built in a "pure" 64-bit system or require specialized packages that cannot currently be built in a "pure" 64-bit system or require
build instructions. Generally, these packages have some embedded 32-bit specialized build instructions. Generally, these packages have some embedded
specific assembly language instructions that fail when building on a 64-bit 32-bit specific assembly language instructions that fail when building on a
system. This includes some Xorg drivers from <ulink 64-bit system. This includes some Xorg drivers for some legacy video cards at
url="http://www.linuxfromscratch.org/blfs/view/svn/">Beyond Linux From Scratch <ulink url="http://xorg.freedesktop.org/releases/individual/driver/">
(BLFS)</ulink>. Many of these problems can be worked around, but may require http://xorg.freedesktop.org/releases/individual/driver/</ulink>. Many of these
some specialized procedures or patches.</para> problems can be worked around, but may require some specialized procedures or
patches.</para>
</sect1> </sect1>

13
udev-lfs/contrib/debian/write_cd_aliases
View File

@ -1,12 +1,21 @@
#!/bin/sh -e #!/bin/sh -e
# Updated for LFS by B. Dubbs, 2012-09-23
# Fix RULES_LOCK location
RULES_FILE="/etc/udev/rules.d/82-persistent-cd.rules" RULES_FILE="/etc/udev/rules.d/82-persistent-cd.rules"
############################################################################## ##############################################################################
lock_rules_file() { lock_rules_file() {
RULES_LOCK="/dev/.udev/.lock-${RULES_FILE##*/}" RULES_LOCK="/run/udev/lock-${RULES_FILE##*/}"
retry=30 if [ ! -d /run/udev/ ]; then
echo "write_cd_aliases: /run/udev does not exist!" >&2
exit 2
fi
retry=10
while ! mkdir $RULES_LOCK 2> /dev/null; do while ! mkdir $RULES_LOCK 2> /dev/null; do
if [ $retry -eq 0 ]; then if [ $retry -eq 0 ]; then
echo "Cannot lock $RULES_FILE!" >&2 echo "Cannot lock $RULES_FILE!" >&2