source: chapter06/coreutils-inst.xml@ c1a2afc

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 12.2 12.2-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/loongarch-12.2 xry111/mips64el xry111/multilib xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since c1a2afc was 494f01f, checked in by Gerard Beekmans <gerard@…>, 21 years ago

Slight rewording of the reason for creating dummy user and groups during chapter 6 - Coreutils

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3036 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 3.0 KB
Line 
1<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
2
3<sect2>
4<title>Installation of Coreutils</title>
5
6<para>Normally the functionality of <userinput>uname</userinput> is somewhat
7broken, in that the <userinput>-p</userinput> switch always returns "unknown".
8The following patch fixes this behaviour for Intel architectures:</para>
9
10<screen><userinput>patch -Np1 -i ../&coreutils-uname-patch;</userinput></screen>
11
12<para>We do not want Coreutils to install its version of the
13<userinput>hostname</userinput> program, because it is inferior to the version
14provided by Net-tools. Prevent its installation by applying a patch:</para>
15
16<screen><userinput>patch -Np1 -i ../&coreutils-hostname-patch;</userinput></screen>
17
18<para>Now prepare Coreutils for compilation:</para>
19
20<screen><userinput>./configure --prefix=/usr</userinput></screen>
21
22<para>Compile the package:</para>
23
24<screen><userinput>make</userinput></screen>
25
26<para>The <userinput>su</userinput> program from Coreutils wasn't installed in
27Chapter 5 because it needed <emphasis>root</emphasis> privilege to do so. We're
28going to need it in a few moments for the test suite. Therefore we work around
29the problem by installing it now:</para>
30
31<screen><userinput>make install-root</userinput></screen>
32
33<para>This package has a test suite available which can perform a number of
34checks to ensure it built correctly. However, this particular test suite
35makes some assumptions with regards to the presence of non-root users and
36groups that don't apply this early into the LFS build. We therefore create
37a dummy system user and two dummy groups to allow the tests to run
38properly. Should you choose not to run the test suite, skip down to
39"Install the package". The following commands will prepare us for the test
40suite. Create two dummy groups and a dummy user name:</para>
41
42<screen><userinput>echo "dummy1:x:1000" >> /etc/group
43echo "dummy2:x:1001:dummy" >> /etc/group
44echo "dummy:x:1000:1000:::/bin/bash" >> /etc/passwd</userinput></screen>
45
46<para>Some tests are meant to run as <emphasis>root</emphasis>:</para>
47
48<screen><userinput>make check-root</userinput></screen>
49
50<para>The remainder of the tests are run as the <emphasis>dummy</emphasis>
51user:</para>
52
53<screen><userinput>su dummy -c "make RUN_EXPENSIVE_TESTS=yes check"</userinput></screen>
54
55<para>Remove the dummy groups and user name:</para>
56
57<screen><userinput>sed -i.bak '/dummy/d' /etc/passwd /etc/group</userinput></screen>
58
59<para>Install the package:</para>
60
61<screen><userinput>make install</userinput></screen>
62
63<para>And move some programs to their proper locations:</para>
64
65<screen><userinput>mv /usr/bin/{basename,cat,chgrp,chmod,chown,cp,dd,df} /bin
66mv /usr/bin/{dir,dircolors,du,date,echo,false,head} /bin
67mv /usr/bin/{install,ln,ls,mkdir,mkfifo,mknod,mv,pwd} /bin
68mv /usr/bin/{rm,rmdir,shred,sync,sleep,stty,su,test} /bin
69mv /usr/bin/{touch,true,uname,vdir} /bin
70mv /usr/bin/chroot /usr/sbin</userinput></screen>
71
72<para>Finally, create a few necessary symlinks:</para>
73
74<screen><userinput>ln -s test /bin/[
75ln -s ../../bin/install /usr/bin</userinput></screen>
76
77</sect2>
78
Note: See TracBrowser for help on using the repository browser.