Re: [lfs-support] Problems starting the final LFS system
Have a closer look: /dev/sdaX in fstab and /dev/hdaX in error message IDE and SCSI? Typo? Cheerio. On 14 May 2012 15:37, Lázaro Morales laz...@frioclima.com.cu wrote: En 11/05/2012 15:58:14, Bruce Dubbs bruce.du...@gmail.com escribió: Lázaro Morales wrote: Hello, After complete the LFS book, when I restart the computer I get a few errors messages and the computer stuck after this: /lib/lsb/init-functions: line 590: /run/var/bootlog: No such file or directory /etc/rc.d/init.d/rc: line 217: /var/log/boot.log: Read-only file system /etc/rc.d/init.d/rc: line 220: /var/log/boot.log: Read-only file system [ 301.811991] rc used greatest stack depth: 5556 byte left INIT: Id 2 respawning too fast: disable for 5 minutes INIT: Id 4 respawning too fast: disable for 5 minutes INIT: Id 5 respawning too fast: disable for 5 minutes INIT: Id 6 respawning too fast: disable for 5 minutes INIT: Id 1 respawning too fast: disable for 5 minutes INIT: Id 3 respawning too fast: disable for 5 minutes INIT: no more processes left in this runlevel The LFS version is 7.1 and is running on VirtualBox with PAE/NX and VT-x, the processor is a dual-core E5300 and the virtual machine have 512MiB of RAM. Could be this a problem? LFS can be compiled on VirtualBox? I think you have a problem in your kernel configuration. Section 8.3 says to ensure you have devtmpfs built into the kernel. The first thing the boot scripts do is create a tmpfs for /run and a directory /run/var. The first line above indicates that that /dev was never mounted. -- Bruce Thanks Bruce and Ken! During the compilation process through the book I created 'Snapshots' in VirtualBox in the critical sections. I restored the last, just before configure the GRUB and found that I had two typo errors in 'inittab' and 'fstab' files. Now after restart I get a new error related to partitions. Activating all swap files/partitions...swapon: /dev/hda3: stat failed: No such file or directory Mounting root file system in read-only mode... Checking file systems...fsck.ext3: No such file or directory while trying to open /dev/hda4 What this mean? I have four partitions: Partition Mount Point Description sda1 / Initial OS, CentOS. sda2 swap Swap for the initial OS. sda3 swap Swap for LFS sda4 LFS Ext3 for LFS Thanks again for your time, Lázaro. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Problems starting the final LFS system
What this mean? I have four partitions: Partition Mount Point Description sda1 / Initial OS, CentOS. sda2 swap Swap for the initial OS. sda3 swap Swap for LFS sda4 LFS Ext3 for LFS As a side note, having a separate swap partition for LFS isn't required, provided there is already a swap partition available on the host system. (See 2.2. Creating a New Partition for details): The swap partition for an LFS system can be the same as the one used by the host system, in which case it is not necessary to create another one. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Problems starting the final LFS system
En 14/05/2012 08:54:50, Эмиль Кранц bl8r1...@tut.by escribió:
Have a closer look: /dev/sdaX in fstab and /dev/hdaX in error message
IDE and SCSI? Typo?
Cheerio.
The virtual machine have 1 virtual disk IDE. The '/dev' folder is:
root:/sources# ls -l /dev | grep sda
lrwxrwxrwx 1 root root 4 May 4 11:55 root- sda1
brw-rw 1 root daemon8, 0 May 4 11:55 sda
brw-rw 1 root daemon8, 1 May 4 11:55 sda1
brw-rw 1 root daemon8, 2 May 4 11:55 sda2
brw-rw 1 root daemon8, 3 May 4 12:08 sda3
brw-rw 1 root daemon8, 4 May 4 11:56 sda4
The 'fstab' file:
# Begin /etc/fstab
# file system mount-point type options dump fsck
#order
/dev/hda4 /ext3 defaults 1 1
/dev/hda3 swap swap pri=10 0
proc /procproc nosuid,noexec,nodev 0 0
sysfs /sysfs sysfs nosuid,noexec,nodev 0 0
devpts /dev/pts devptsgid=4,mode=620 0 0
tmpfs /run tmpfs defaults 0 0
devtmpfs /dev devtmpfs mode=0755,nosuid 0 0
# End /etc/fstab
The GRUB file
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,4)
menuentry GNU/Linux, Linux 3.2.6-lfs-7.1 {
linux /boot/vmlinuz-3.2.6-lfs-7.1 root=/dev/sda4 ro
}
Is something wrong there?
Thanks,
Lázaro
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Problems starting the final LFS system
En 14/05/2012 09:20:37, Lázaro Morales laz...@frioclima.com.cu escribió: sysfs /sysfs sysfs nosuid,noexec,nodev 0 0 Sorry, this is the old 'fstab' file, I corrected this error, the mount point for 'sysfs' is '/sys'. Regards, Lázaro -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Problems starting the final LFS system
Your fstab partitions are /dev/hda4 and /dev/hda3,
while in your grub - set root=(hd0,4) and root=/dev/sda4
I mean it should be either SDA or HDA,
SDA for SCSI drives while HDA for IDE drives
Correct drive names uniformly in /etc/fstab and /boot/grub/grub.cfg
depending on your hard drive type.
EK
On 14 May 2012 16:20, Lázaro Morales laz...@frioclima.com.cu wrote:
En 14/05/2012 08:54:50, Эмиль Кранц bl8r1...@tut.by escribió:
Have a closer look: /dev/sdaX in fstab and /dev/hdaX in error message
IDE and SCSI? Typo?
Cheerio.
The virtual machine have 1 virtual disk IDE. The '/dev' folder is:
root:/sources# ls -l /dev | grep sda
lrwxrwxrwx 1 root root 4 May 4 11:55 root- sda1
brw-rw 1 root daemon8, 0 May 4 11:55 sda
brw-rw 1 root daemon8, 1 May 4 11:55 sda1
brw-rw 1 root daemon8, 2 May 4 11:55 sda2
brw-rw 1 root daemon8, 3 May 4 12:08 sda3
brw-rw 1 root daemon8, 4 May 4 11:56 sda4
The 'fstab' file:
# Begin /etc/fstab
# file system mount-point type options dump fsck
#order
/dev/hda4 /ext3 defaults 1 1
/dev/hda3 swap swap pri=10 0
proc /procproc nosuid,noexec,nodev 0 0
sysfs /sysfs sysfs nosuid,noexec,nodev 0 0
devpts /dev/pts devptsgid=4,mode=620 0 0
tmpfs /run tmpfs defaults 0 0
devtmpfs /dev devtmpfs mode=0755,nosuid 0 0
# End /etc/fstab
The GRUB file
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,4)
menuentry GNU/Linux, Linux 3.2.6-lfs-7.1 {
linux /boot/vmlinuz-3.2.6-lfs-7.1 root=/dev/sda4 ro
}
Is something wrong there?
Thanks,
Lázaro
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Problems starting the final LFS system
On Mon, 14 May 2012 14:31:11 +0100
Lázaro Morales laz...@frioclima.com.cu wrote:
En 14/05/2012 08:54:50, Эмиль Кранц bl8r1...@tut.by escribió:
Have a closer look: /dev/sdaX in fstab and /dev/hdaX in error message
IDE and SCSI? Typo?
Cheerio.
The virtual machine have 1 virtual disk IDE. The '/dev' folder is:
root:/sources# ls -l /dev | grep sda
lrwxrwxrwx 1 root root 4 May 4 11:55 root- sda1
brw-rw 1 root daemon8, 0 May 4 11:55 sda
brw-rw 1 root daemon8, 1 May 4 11:55 sda1
brw-rw 1 root daemon8, 2 May 4 11:55 sda2
brw-rw 1 root daemon8, 3 May 4 12:08 sda3
brw-rw 1 root daemon8, 4 May 4 11:56 sda4
The 'fstab' file:
# Begin /etc/fstab
# file system mount-point type options dump fsck
#order
/dev/hda4 /ext3 defaults 1 1
/dev/hda3 swap swap pri=10 0
proc /procproc nosuid,noexec,nodev 0 0
sysfs /sysfs sysfs nosuid,noexec,nodev 0 0
devpts /dev/pts devptsgid=4,mode=620 0 0
tmpfs /run tmpfs defaults 0 0
devtmpfs /dev devtmpfs mode=0755,nosuid 0 0
# End /etc/fstab
The GRUB file
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,4)
menuentry GNU/Linux, Linux 3.2.6-lfs-7.1 {
linux /boot/vmlinuz-3.2.6-lfs-7.1 root=/dev/sda4 ro
}
Is something wrong there?
Yes, in grub.cfg you have root=/dev/sda4 (and the kernel boots, so it's
happy with /dev/sda) then the bootscripts choke because you
have /dev/hda in /etc/fstab.
sed -i 's#/dev/hda#/dev/sda#' /etc/fstab
Andy
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Problems starting the final LFS system
En 14/05/2012 10:10:38, Andrew Benton a...@benton.eu.com escribió: Yes, in grub.cfg you have root=/dev/sda4 (and the kernel boots, so it's happy with /dev/sda) then the bootscripts choke because you have /dev/hda in /etc/fstab. sed -i 's#/dev/hda#/dev/sda#' /etc/fstab Andy Thanks very much to Andrew and EK, and all in general. Now I finally have finished the book. Thanks again, Lázaro. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] LFS-71.: Solution for automation of 'tar X', 'cd X' ... 'cd ..', 'rm -R X'.
Hi there, As for each package you should decompress the package, enter decompressed folder, compileinstall and finally remove decompressed folder, and also while you do not learn any new thing by doing these each time, so I would like to share my automation solution which does these just by getting a partial name of the package: To create the main .sh file, issue following commands while you're logged in by chroot (section 6 of LFS-7.1) and also you're in '$LFS/sources' directory: cat t.sh EOF if [ $1 == ]; then echo 'USAGE: t.bash [name]' return fi FNAME=$(ls $1* | grep tar.xz) if [ $FNAME == ]; then FNAME=$(ls $1* | grep tar.gz) if [ $FNAME == ]; then FNAME=$(ls $1* | grep tar.bz2) if [ $FNAME == ]; then echo 'match not found!' return else TARPARAM='-jxf' EXT='.tar.bz2' fi else TARPARAM='-zxf' EXT='.tar.gz' fi else TARPARAM='-Jxf' EXT='.tar.xz' fi DIR=$(echo $FNAME | sed s/$EXT//g) echo `rm -fR $DIR` echo `ls $1*` echo `tar $TARPARAM $FNAME` rm -vfR ut.sh echo -e 'cd ..\necho `rm -fR '$DIR'`\necho `ls '$1'*`\nrm -vfR ut.sh' ut.sh chmod 777 ut.sh cd $DIR EOF chmod 777 t.sh Now, to use automation, act like following: Issue following command to decompress and enter to decompressed folder by just specifying package partial name:source ./t.sh [package-partial-name] e.g. source ./t.sh autoco for autoconf-2.68 package.NOTE: package-partial-name should be long enough to distinct the package from others e.g. source ./t.sh bi is not suitable at all because can not distinct between binutils and bison!Do the book's instructions to configure, compile, test and install the package.Issue following command to undo the above instruction #1.source ../ut.sh. Sicerely Yours, Yasser. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] LFS-7.1: 6.37. Automake-1.11.3 (TEST FAILURE)!
Hi, 'make -j2 check' on 'LFS-7.1: 6.37. Automake-1.11.3 (http://www.linuxfromscratch.org/lfs/view/stable/chapter06/automake.html)' informs me for one failure with following red message :( = 1 of 842 tests failed (96 tests were not run) See tests/test-suite.log Please report to bug-autom...@gnu.org = make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory `/sources/automake-1.11.3/tests' make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory `/sources/automake-1.11.3/tests' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/sources/automake-1.11.3/tests' make: *** [check-recursive] Error 1 I also reviewed 'tests/test-suite.log' for word 'Error' and found following rows which are maybe related: + make Making all in src make[1]: Entering directory `/sources/automake-1.11.3/tests/depcomp10.dir/build/src' source='../../src/foo.c' object='foo.o' libtool=no \ DEPDIR=.deps depmode=hp /bin/sh ../../depcomp \ gcc -DPACKAGE_NAME=\depcomp10\ -DPACKAGE_TARNAME=\depcomp10\ -DPACKAGE_VERSION=\1.0\ -DPACKAGE_STRING=\depcomp10\ 1.0\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\depcomp10\ -DVERSION=\1.0\ -I. -I../../src -g -O2 -c -o foo.o ../../src/foo.c cc1: error: unrecognized command line option '-M.deps/foo.TPo' make[1]: *** [foo.o] Error 1 make[1]: Leaving directory `/sources/automake-1.11.3/tests/depcomp10.dir/build/src' make: *** [all-recursive] Error 1 + Exit 77 Is this failure expected or is a fatal error (and the process could not be continued before resolving it)?! Or do you think that eliminating '-j2' switch will resolve it (I should know before trying because it's test take 31 minutes to complete(i.e. 1 hour without -j2!))? Thanks in advance! -Yasser -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS-7.1: 6.37. Automake-1.11.3 (TEST FAILURE)!
On Mon, May 14, 2012 at 10:56:10PM +0430, Yasser Zamani wrote: Is this failure expected or is a fatal error (and the process could not be continued before resolving it)?! Or do you think that eliminating '-j2' switch will resolve it (I should know before trying because it's test take 31 minutes to complete(i.e. 1 hour without -j2!))? Thanks in advance! -Yasser A few general points, since I don't have any test results from 7.1 handy (I generally only run full tests when building a new set of versions, and I've upgraded to new machines after confirming 7.1 was good) : 1. For me, there are often occasional test failures. Some of these are caused by my deviations from the book (avoiding as many static libraries as I can), others are probably down to different hardware, or even different kernel versions. When we were first able to run tests (LFS-5, if my memory is correct), it looked very useful - in LFS-4 I remember some people had apparently inexplicable build failures. In practice, most test failures are not particularly useful in diagnosing that anything is wrong: more often, it's a shortcoming of the test. Also, even if all the tests pass 100%, it says nothing about whether the resulting system will be good enough (see recent posts on lfs-dev about unpatched glibc). So, if you have *many* test failures, it can indicate a problem. For people making changes to the book, particularly to how packages are built, or to the build order, changes in detailed failure results can be very informative - I remember a problem in early cross-lfs which I traced to a different build order. For everyone else, use a pinch of salt. 2. We know you are developing scripts. I will venture to suggest that when moving to scripts, or when making major changes in how your scripts work, it is useful to keep your previous results so that you know if a test failure is a difference : if it isn't, you can ignore it for the purposes of validating the scripts. If it is different, see point (1.) and, if you care enough, try googling to see if anyone else has found the problem recently, and any solutions or explanations offered. 3. If it only takes an hour to rerun make -j1 check, it's probably going to be more efficient for you to try that rather than wait for mailing list responses. I've only recently got multiprocessor desktops ( on my old single processor machines, make -j2 often took longer then make -j1 ) and so far I've found about half a dozen packages in my whole desktop build where make -j1 is needed. Often, the results are obvious, but occasionally the failures are sporadic with very misleading error messages. The other problem with using make -j1 in *tests* is that the results might be mixed together (e.g. gcc, where using contrib/test_summary makes the results comprehensible). So, if your machine has CPU cycles to spare, *trying* multiple makes or checks is worthwhile. But if the build or tests fail, or if the test logs are too garbled to be useful, you will need to be prepared to retry with a single make. In this case, your scripts, your results :) ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
