Re: [lfs-support] No wireless connection to network
Op Mon, 18 Nov 2013 06:35:07 +0100 schreef Bruce Dubbs bruce.du...@gmail.com:
hans kaper wrote:
Compared with the discussion about efi-booting, which I follow with interest
and admiration, I am still in the stone-age. I installed LFS 7.4 on an old
laptop. It boots fine, but I cannot connect wireless to my network.
Wired is no problem (although I cannot find the eth0-device anywhere; how
does this work?).
The laptop uses a Cisco-Linksys wireless usb-adapter. Running udevadm
monitor and inserting the adapter gives device-information that I put in a
rule into 70-persistent-netrules with the name wlan0:
SUBSYSTEM=usb, ACTION==add, ATTR{idVendor}==13b1,
ATTR{manufacturer}=Cisco-Linksys , ATTR{idProduct}==0020, NAME=wlan0
I added ifconfig.wlan0 to /etc/sysconfig:
ONBOOT=yes
IFACE=wlan0
SERVICE=ipv4-static
IP=192.168.178.26
GATEWAY=192.168.178.0
PREFIX=24
The GATEWAY shouldn't have this address with this netmask. The .0 is
the network address and it will probably confuse the routing table.
You are right, a typo.
I am now looking into the kernel, comparing the Mint-kernel with lfs, whether I
miss something there.
And installing wpa-supplicant of course, but that only makes sense when the
device is found and ready.
Hans.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
[lfs-support] No wireless connection to network
Compared with the discussion about efi-booting, which I follow with interest
and admiration, I am still in the stone-age. I installed LFS 7.4 on an old
laptop. It boots fine, but I cannot connect wireless to my network.
Wired is no problem (although I cannot find the eth0-device anywhere; how does
this work?).
The laptop uses a Cisco-Linksys wireless usb-adapter. Running udevadm monitor
and inserting the adapter gives device-information that I put in a rule into
70-persistent-netrules with the name wlan0:
SUBSYSTEM=usb, ACTION==add, ATTR{idVendor}==13b1,
ATTR{manufacturer}=Cisco-Linksys , ATTR{idProduct}==0020, NAME=wlan0
I added ifconfig.wlan0 to /etc/sysconfig:
ONBOOT=yes
IFACE=wlan0
SERVICE=ipv4-static
IP=192.168.178.26
GATEWAY=192.168.178.0
PREFIX=24
BROADCAST=192.168.178.255
WIRELESS_DEV=wlan0
#SERVICE=dhcpcd
In the kernel I have a line CONFIG_WIRELESS=y (but CONFIG_IPWIRELESS is not
set !?). But on booting I get the errors:
- cannot find device wlan0
- interface wlan0 does not exist.
Puppy Linux and Mint-13 on the same laptop have no problem finding wireless my
Fritz!Box-modem.
Can anyone help me with this problem?
Hans.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Some BLFS Packages Before Making LFS-7.4 Bootable
Op Thu, 31 Oct 2013 21:02:22 +0100 schreef Ken Moffat zarniwh...@ntlworld.com: On Thu, Oct 31, 2013 at 02:28:27PM -0500, Dan McGhee wrote: So that I can hit the deck running after I get my new system to boot, I want to add a few packages, and their associated boot scripts, from BLFS. These are dhcpd, wpa-supplicant, libxml, libn, open-ssl and d-bus. I seem to remember reading somewhere, and I thought it was in the LFS book, that it was OK to do what I'm thinking of. I don't see anything that will hinder my plan, but I thought I'd ask here where many people know a lot more about this than I do. Anything to be careful of? Thanks, Dan There used to be some packages that gave problems if building in chroot. But I don't remember what they were. In the last couple of years I've done some complete builds in chroot while I sorted out changes to my build scripts, so I don't think you'll have any problems. You might want to add a text browser so that you can read the BLFS book. And Midnight Commander (MC) as a file-manager, which comes even with a small text-editor. I find it indispensable. MC ans its dependencies are easy to make and install. Links is very good to browse the BLFS book. After you have installed it, it even starts from inside MC, clicking on the index-file. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Grateful
Op Fri, 18 Oct 2013 23:42:03 +0200 schreef Dan McGhee beesn...@grm.net:
I decided to write this since even in my old age I like receiving
feedback that my efforts are not in vain.
Hats off to you {,B}LFS editors, maintainers, developers and list
supporters. The job you do is almost insurmountable, yet you do it with
aplomb. The LFS book is exactly what it says it is: a follow the
directions exactly learning experience to build an operation system.
That takes work and attention to details. Not only that, but you take
care of broken links on the web site, e-mails not automatically going to
those who need them--yes, I follow the list--and all sorts of other
housekeeping chores.
But given all of this, you take the time to aid people. I know I can be
a pest because I like to have things right in my mind before I go
ahead. It's worse right now since I'm scouring the rust from my
building skills. Just this week, Ken Moffat, Bruce Dubbs and Pierre
Labastie have taken the time to point me in the right direction so I can
do things the way I want to.
I remember from my working days that the trenches can get so deep I
wanted to throw in the towel. I urge you not to lose your attitudes.
Thanks to you all.
Dan
Hear, hear
I was pondering such action, but Dan beat me. I stray into support-sites now
and then, but none of them comes near to the quality, politeness and
thouroughness of this site!
Thank you from me too.
Hans.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Grateful
Op Sun, 20 Oct 2013 15:53:50 +0200 schreef hans kaper spaky...@xs4all.nl:
Op Fri, 18 Oct 2013 23:42:03 +0200 schreef Dan McGhee beesn...@grm.net:
I decided to write this since even in my old age I like receiving
feedback that my efforts are not in vain.
Hats off to you {,B}LFS editors, maintainers, developers and list
supporters. The job you do is almost insurmountable, yet you do it with
aplomb. The LFS book is exactly what it says it is: a follow the
directions exactly learning experience to build an operation system.
That takes work and attention to details. Not only that, but you take
care of broken links on the web site, e-mails not automatically going to
those who need them--yes, I follow the list--and all sorts of other
housekeeping chores.
But given all of this, you take the time to aid people. I know I can be
a pest because I like to have things right in my mind before I go
ahead. It's worse right now since I'm scouring the rust from my
building skills. Just this week, Ken Moffat, Bruce Dubbs and Pierre
Labastie have taken the time to point me in the right direction so I can
do things the way I want to.
I remember from my working days that the trenches can get so deep I
wanted to throw in the towel. I urge you not to lose your attitudes.
Thanks to you all.
Dan
Hear, hear
I was pondering such action, but Dan beat me. I stray into support-sites now
and then, but none of them comes near to the quality, politeness and
thouroughness of this site!
And patience, of course.
Thank you from me too.
Hans.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Inetutils check error (SOLVED)
Op Wed, 09 Oct 2013 23:16:30 +0200 schreef William Harrington kb0...@berzerkula.org: On Oct 9, 2013, at 3:32 PM, hans kaper wrote: Always helps to not miss a package install! I can usually tell when someone missed a package, but this is the first encounter of someone not installing iana-etc I semi-automatically generate build-scripts (build-scripts based on the work of Dan McGhee, by the way) with Perl-scripts and regular expressions. A package that has a sourcename with two dashes instead of one (or no dashes at all), means trouble. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Inetutils check error
Building Inetutils in LFS 7_4 I got a check error. It did not prevent a successful build, but it did prevent reaching internet. The log was: make[3]: Entering directory `/sources/inetutils-1.9.1/tests' localhost: hans-Dimension-8300 PASS: localhost ping: unknown protocol icmp. Failed at pinging 127.0.0.1. PING ::1 (::1): 56 data bytes 64 bytes from localhost: icmp_seq=0 ttl=64 time=0.104 ms --- ::1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.104/0.104/0.104/0.000 ms FAIL: ping-localhost.sh traceroute to 127.0.0.1 (127.0.0.1), 64 hops max ../src/traceroute: can't find supplied protocol 'icmp' Failed at UDP tracing. traceroute to 127.0.0.1 (127.0.0.1), 64 hops max ../src/traceroute: can't find supplied protocol 'icmp' Failed at ICMP tracing. FAIL: traceroute-localhost.sh hans-Dimension-8300 PASS: hostname.sh == 2 of 4 tests failed I saw no errors in the make-part and rebuild several times with the same effect. The md5sum is correct. Any ideas? Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Inetutils check error
Op Wed, 09 Oct 2013 18:03:55 +0200 schreef William Harrington kb0...@berzerkula.org: On Oct 9, 2013, at 10:33 AM, hans kaper wrote: FAIL: ping-localhost.sh traceroute to 127.0.0.1 (127.0.0.1), 64 hops max ../src/traceroute: can't find supplied protocol 'icmp' Failed at UDP tracing. traceroute to 127.0.0.1 (127.0.0.1), 64 hops max ../src/traceroute: can't find supplied protocol 'icmp' Failed at ICMP tracing. FAIL: traceroute-localhost.sh Perhaps your host is blocking or dropping icmp or it is altogether disabled? Sorry, I was not exact and complete enough: when I boot LXF7.4, I cannot reach internet. And the build of LFS7.4 gave the aforementioned error. When I boot into LFS7.3: no problem (and no errors in the build, while the two sources are identical!). Maybe I should compare the two builds more closely. I will try that. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Inetutils check error
Op Wed, 09 Oct 2013 21:48:49 +0200 schreef hans kaper spaky...@xs4all.nl: Op Wed, 09 Oct 2013 18:03:55 +0200 schreef William Harrington kb0...@berzerkula.org: On Oct 9, 2013, at 10:33 AM, hans kaper wrote: FAIL: ping-localhost.sh traceroute to 127.0.0.1 (127.0.0.1), 64 hops max ../src/traceroute: can't find supplied protocol 'icmp' Failed at UDP tracing. traceroute to 127.0.0.1 (127.0.0.1), 64 hops max ../src/traceroute: can't find supplied protocol 'icmp' Failed at ICMP tracing. FAIL: traceroute-localhost.sh Perhaps your host is blocking or dropping icmp or it is altogether disabled? Sorry, I was not exact and complete enough: when I boot LXF7.4, I cannot reach internet. And the build of LFS7.4 gave the aforementioned error. When I boot into LFS7.3: no problem (and no errors in the build, while the two sources are identical!). Maybe I should compare the two builds more closely. I will try that. I did. The logfiles are identical, apart from the timestamp, upto the check-part. So the problem lies somewhere else. I will rebuild Inetutils in LFS7.3, but will make a backup of LFS7.3 first. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Inetutils check error (SOLVED)
Op Wed, 09 Oct 2013 22:08:55 +0200 schreef hans kaper spaky...@xs4all.nl: Op Wed, 09 Oct 2013 21:48:49 +0200 schreef hans kaper spaky...@xs4all.nl: Op Wed, 09 Oct 2013 18:03:55 +0200 schreef William Harrington kb0...@berzerkula.org: On Oct 9, 2013, at 10:33 AM, hans kaper wrote: FAIL: ping-localhost.sh traceroute to 127.0.0.1 (127.0.0.1), 64 hops max ../src/traceroute: can't find supplied protocol 'icmp' Failed at UDP tracing. traceroute to 127.0.0.1 (127.0.0.1), 64 hops max ../src/traceroute: can't find supplied protocol 'icmp' Failed at ICMP tracing. FAIL: traceroute-localhost.sh Perhaps your host is blocking or dropping icmp or it is altogether disabled? Sorry, I was not exact and complete enough: when I boot LXF7.4, I cannot reach internet. And the build of LFS7.4 gave the aforementioned error. When I boot into LFS7.3: no problem (and no errors in the build, while the two sources are identical!). Maybe I should compare the two builds more closely. I will try that. I did. The logfiles are identical, apart from the timestamp, upto the check-part. So the problem lies somewhere else. I will rebuild Inetutils in LFS7.3, but will make a backup of LFS7.3 first. I rebuild Inetutils in LFS7.3: no problem. But I found something else: in build LFS7.4 no logfile from Iana!? And no /etc/protocols and no etc/services. I must have missed an error there. Must make my scripts more fool-proof!! William, sorry for the trouble and thanks for the attention. Hans. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Unable to login SOLVED
Op Fri, 04 Oct 2013 23:13:20 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: Then: strace -olog.txt login I looked at a trace for my system. Do you have /etc/group? These are my opens, disregarding library and files not found: open(/etc/login.defs, O_RDONLY) = 3 open(/root/.bash_history, O_RDONLY) = 3 The last part of the list of files were not opened because login did not come that far. Check that login.defs, nsswitch.conf, passwd, login.access, and group all exist. Note that shadow is not opened. Because you use no password? All the files are there. I copied passwd, groups and shadow from my succesful build of LFS7_3 to LFS7_4, but no log-in, although a different error-message. Then, in the end, I re-installed Shadow et voila: a successful login! Analysing the logs, I saw no differences with the first install, apart from installs by libtool from /usr/bin/install instead of /tools/bin/install, but that shall originate from the fact that in the first build libtool was build after Shadow. That leaves the question why the failures occurred in the first place? Any suggestion were I should look in the strace-logfiles to get a clue? LFS is for learning, he? The login-failure occurred after the password was given. In the successful login login.access was opened, but that was not the case in the failed login, although /etc/login.access existed. There was also no failure of opening that file. But again, Bruce, I am, very grateful for your extensive help!! Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Unable to login
Op Thu, 03 Oct 2013 23:04:51 +0200 schreef William Harrington
kb0...@berzerkula.org:
On Oct 3, 2013, at 3:24 PM, hans kaper wrote:
I added a line and an error occurred. So login.defs was read.
Now find the line that is causing the invalid argument
chroot and run login and see what happens.
The same error!!
Also, install strace and run login and see what happens.
Installing strace gives a make-error:
gcc -DHAVE_CONFIG_H -I. -I./linux/i386 -I./linux -I./linux -Wall
-Wwrite-strings -g -O2 -MT process.o -MD -MP -MF .deps/process.Tpo -c -o
process.o process.c
In file included from process.c:66:0:
/usr/include/linux/ptrace.h:58:8: error: redefinition of 'struct
ptrace_peeksiginfo_args'
struct ptrace_peeksiginfo_args {
^
In file included from defs.h:159:0,
from process.c:37:
/usr/include/sys/ptrace.h:191:8: note: originally defined here
struct ptrace_peeksiginfo_args
^
make[2]: *** [process.o] Error 1
make[2]: Leaving directory `/sources/strace-4.8'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/sources/strace-4.8'
make: *** [all] Error 2
I tried to verify the packet with gpg: error: public key not found. How to
find that key?
I am not that experienced with gpg.
By the way, thanks to Bruce and you for the effort to help me.
Hans.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Unable to login
Op Fri, 04 Oct 2013 17:13:50 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: hans kaper wrote: Op Thu, 03 Oct 2013 23:04:51 +0200 schreef William Harrington kb0...@berzerkula.org: On Oct 3, 2013, at 3:24 PM, hans kaper wrote: Also, install strace and run login and see what happens. Use the patch: http://www.linuxfromscratch.org/patches/downloads/strace/strace-4.8-glibc_2.18_build_fix-1.patch That worked! First line in Password is now: root::0:0:root:/root:/bin/bash I omitted the x after the first :, as Bruce advised. I assume that then no password is necessary. Next I chroot as in the begin of ch.6, so that devices are loaded. Then: strace -olog.txt login The log-file gives a lot of data, but I think the most important are: . read(0, root\n, 1024) (reading from the kbd) . open(/etc/passwd, O_RDONLY|O_CLOEXEC) = 3 .. read(3, root::0:0:root:/root:/bin/bash\nb..., 4096) = 159 ... write(4, Wachtwoord: , 12)= 12 (=Password: ) read(4, \n, 4096) = 1 (just Enter, no password necessary) write(4, \n, 1) ... _llseek(4, 0, 0xbfeae3e0, SEEK_CUR) = -1 ESPIPE (Illegal seek) I assume the last line is the error, but I don't know what it means. If I give the password, the result is the same. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Unable to login
I build LFS 7.4 from the book. It boots all-right but I cannot login: login: root password: xx crypt: Invalid argument Trying another user fails too. I double checked inittab and the shadow-build, but found no faults. The same goes for the kernel-config file. What can be the reason of the failing login? Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Unable to login
Op Thu, 03 Oct 2013 22:05:25 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: hans kaper wrote: I build LFS 7.4 from the book. It boots all-right but I cannot login: login: root password: xx crypt: Invalid argument Trying another user fails too. I double checked inittab and the shadow-build, but found no faults. The same goes for the kernel-config file. What can be the reason of the failing login? Did you set the password for root? -- Bruce Of course. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Unable to login
Op Thu, 03 Oct 2013 22:13:02 +0200 schreef William Harrington kb0...@berzerkula.org: On Oct 3, 2013, at 3:01 PM, hans kaper wrote: login: root password: xx crypt: Invalid argument Not using pam? LFS book 7.4, page 124:... They also require Linux-PAM which is not available in LFS. Also, double check your login.defs in /etc I added a line and an error occurred. So login.defs was read. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Unable to login
Op Thu, 03 Oct 2013 22:20:51 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: hans kaper wrote: Op Thu, 03 Oct 2013 22:05:25 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: hans kaper wrote: I build LFS 7.4 from the book. It boots all-right but I cannot login: login: root password: xx crypt: Invalid argument Trying another user fails too. I double checked inittab and the shadow-build, but found no faults. The same goes for the kernel-config file. What can be the reason of the failing login? Did you set the password for root? Of course. Then you probably have the wrong password or didn't install shadow properly. I checked the shadow-build , but did not find any errors. To get in, you can edit /etc/passwd so root's entry is: root::0:0:root:/root:/bin/bash That did not work either; same error. I don't expect a keyboard-problem: all the letters appear as typed. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] More control and package management using package users
Op Mon, 23 Sep 2013 21:05:01 +0200 schreef Rob Taylor rtaylor...@gmail.com:I have been working through LFS 7.2, 7.3 and 7.4 testing and revising scripts for this package management system.I have added a number of scripts and in some cases almost entirely rewritten the existing scripts. While I have tested these scripts no one else has so, my version of this package should be considered Alpha or Beta at best. You can play with the revised project and see my notes here:https://www.javacrypt.com/lfs/I don't have a lot of time for development or support so use at your own risk and use the lists here or Google as a resource if my replies seem rather slow. Enjoy,Robert Taylor Looks impressive. I stopped using the package management system; too much trouble and not enough benefits, but I still use scripts that are based on it. I will look into yours; maybe I can learn from it.Another interesting piece of work on this subject you can find at https://github.com/ericherman/package-users.There was also a discussion on this subject on this support site about two years ago, initiated by Drew Ames.Hans.-- 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.4 grub-install problem
Op Fri, 20 Sep 2013 16:48:17 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: Geoff Swan wrote: I recently proceeded with the LFS-7.4 build, using a FC16 bootstrap host, which built nicely all the way to the grub-install part in chapter 8.4. The FC16 bootstrap OS is on sda and the new LFS build is on sdb, so eventually sda can be removed and replaced with the LFS drive. I've never put grub on anything other than sda. I do know that grub has some areas on the disk that it needs to access outside of a file system. Fedora uses some security modules like selinux. I don't know if that is the issue or not. Grub2 can be installed on any drive: grub-install /dev/sdx , where x=a,b,c or whatever disks you have and choose. #Installeren Grub2: #in my case root filesysteem is Mint_13 with Grub2 installed, on sdb6 sudo mount /dev/sdb6 /mnt #mount boot-partition: sudo mount /dev/sdb15 /mnt/boot #mount devices: sudo mount --bind /dev /mnt/dev sudo chroot /mnt update-grub grub-install /dev/sda #(or /dev/sdb or .) If necessary: restart sudo update-grub install-grub /dev/sda # (or /dev/sdb or ) #to find other installed systems I think, when Grub2 is installed on your LFS-partition, the same commands will work. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Error building gcc pass 2 in ch.5
Op Wed, 18 Sep 2013 22:25:30 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: hans kaper wrote: After failing to be able to use the tools from LFS 7.3 in 7.4, I decided to build the tools from the book 7.4. I soon ran into another problem: after building the tools up and until Binutils pass 2 without errors, I got the following error building GCC, pass 2: ../../gcc-4.8.1/gcc/system.h:205:20: fatal error: cstring: No such file or directory # include cstring ^ compilation terminated. The file cstring is not found. I assume it has to be somewhere in the gcc-build but I don't know why not. I deleted the tools and started anew, with the same result. The md5sum for GCC is correct and so are the system-requirements. The build-directories were deleted from /source after the pass 1-build. Any idea what is wrong? Did you install libstdc++-4.8.1 (section 5.8)? Did you delete prior gcc-build and gcc-4.8.1 directories before reextracting gcc for each of GCC-4.8.1 - Pass 1, Libstdc++-4.8.1, GCC-4.8.1 - Pass 2? -- Bruce Yes, I did all that. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Error building gcc pass 2 in ch.5
Op Wed, 18 Sep 2013 22:25:30 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: hans kaper wrote: ../../gcc-4.8.1/gcc/system.h:205:20: fatal error: cstring: No such file or directory # include cstring ^ compilation terminated. The file cstring is not found. I assume it has to be somewhere in the gcc-build but I don't know why not. I deleted the tools and started anew, with the same result. The md5sum for GCC is correct and so are the system-requirements. The build-directories were deleted from /source after the pass 1-build. Any idea what is wrong? Did you install libstdc++-4.8.1 (section 5.8)? Did you delete prior gcc-build and gcc-4.8.1 directories before reextracting gcc for each of GCC-4.8.1 - Pass 1, Libstdc++-4.8.1, GCC-4.8.1 - Pass 2? -- Bruce Yes, I did all that. But looking at my logs, I don't see any log for Libstdc!!?? So I will restart from there. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Error building gcc pass 2 in ch.5 (solved)
Op Thu, 19 Sep 2013 14:10:20 +0200 schreef hans kaper spaky...@xs4all.nl: Op Wed, 18 Sep 2013 22:25:30 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: hans kaper wrote: After failing to be able to use the tools from LFS 7.3 in 7.4, I decided to build the tools from the book 7.4. I soon ran into another problem: after building the tools up and until Binutils pass 2 without errors, I got the following error building GCC, pass 2: ... Did you install libstdc++-4.8.1 (section 5.8)? Did you delete prior gcc-build and gcc-4.8.1 directories before reextracting gcc for each of GCC-4.8.1 - Pass 1, Libstdc++-4.8.1, GCC-4.8.1 - Pass 2? -- Bruce Yes, I did all that. But looking at my logs, I don't see any log for Libstdc!!?? So I will restart from there. Hans. That did work: I made a mistake in the Listdc++-script. Bruce and Ken: thanks again. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Error building gcc pass 2 in ch.5
After failing to be able to use the tools from LFS 7.3 in 7.4, I decided to build the tools from the book 7.4. I soon ran into another problem: after building the tools up and until Binutils pass 2 without errors, I got the following error building GCC, pass 2: i686-lfs-linux-gnu-g++ -c -fomit-frame-pointer -g -O2 -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild -I../../gcc-4.8.1/gcc -I../../gcc-4.8.1/gcc/build -I../../gcc-4.8.1/gcc/../include -I../../gcc-4.8.1/gcc/../libcpp/include -I/mnt/lfs/sources/gcc-build/./gmp -I/mnt/lfs/sources/gcc-4.8.1/gmp -I/mnt/lfs/sources/gcc-build/../gcc-4.8.1/mpfr/src -I/mnt/lfs/sources/gcc-4.8.1/mpc/src -I../../gcc-4.8.1/gcc/../libdecnumber -I../../gcc-4.8.1/gcc/../libdecnumber/bid -I../libdecnumber -I../../gcc-4.8.1/gcc/../libbacktrace\ -o build/genconstants.o ../../gcc-4.8.1/gcc/genconstants.c In file included from ../../gcc-4.8.1/gcc/genconstants.c:28:0: ../../gcc-4.8.1/gcc/system.h:205:20: fatal error: cstring: No such file or directory # include cstring ^ compilation terminated. The file cstring is not found. I assume it has to be somewhere in the gcc-build but I don't know why not. I deleted the tools and started anew, with the same result. The md5sum for GCC is correct and so are the system-requirements. The build-directories were deleted from /source after the pass 1-build. Any idea what is wrong? Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Error building Headers in ch. 6
Op Tue, 25 Jun 2013 21:54:07 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: Just to note that the packages in Chapter 5 and Chapter 6 do not have to be identical: http://www.linuxfromscratch.org/~bdubbs/files/updating-lfs.html Just to recap, I built Chapter 5 using LFS 6.6. I then completed Chapters 6+ with SVN-20120610 (About LFS-7.2 and a half). The only issue is that the packages, when you are done with Chapter 5, have to support all the versions specified in the Host System Requirements. -- Bruce So I copied the tools I built with LFS 7.3, which worked successfully there, to a new partition on the same system to build LFS 7.4 (SVN LFS-BOOK-SVN-20130831 to be exact). I then started with ch.6, but got stuck building the Linux Headers: /tools/lib/gcc/i686-pc-linux-gnu/4.7.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lc /tools/lib/gcc/i686-pc-linux-gnu/4.7.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find crtn.o: No such file or directory collect2: error: ld returned 1 exit status make[1]: *** [scripts/basic/fixdep] Error 1 make: *** [scripts_basic] Error 2 CHK include/generated/uapi/linux/version.h HOSTCC scripts/basic/fixdep /tools/lib/gcc/i686-pc-linux-gnu/4.7.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find crt1.o: No such file or directory ... collect2: error: ld returned 1 exit status make[1]: *** [scripts/basic/fixdep] Error 1 make: *** [scripts_basic] Error 2 FAILED! So I went back to LFS 7.3 and rebuild the Linux Headers there: no problem!! So what is wrong with a simple copy of the tools? Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] gcc (pass 2) compile error
Op Sun, 14 Jul 2013 03:08:09 +0200 schreef Erich Schulman (KT4VOL/KTN4CA) chibito...@gmail.com:Unfortunately I have now been stopped dead in my tracks. I used Acronis Disk Director 11 to increase my swap to 6 GB. Instead, it nuked my swap, /home, and /lfs partitions. I may as well go back to the Debian netinstall .iso and start over. I have never had it mess up a Windows partition before.Use GParted. I never had any problem with it, it shows very clearly which partitions you have and does not let youoverwrite one partition with another (unless you explicitly say so).By the way: a swap-partition-size of 6 GB is rather big.Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Ch.5.20: findutils install error
Op Thu, 04 Jul 2013 22:42:47 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: hans kaper wrote: Building LFS 7.3 I get an install-error in ch.5.20: Findutils-4.4.2: It seems you did not configure with --prefix=/tools. The log should say: test -z /tools/bin || /tools/bin/mkdir -p /tools/bin /tools/bin/install -c 'find' '/tools/bin/find' -- Bruce You are right. For unknown reasons I strayed into ch.6, copied the config-commands there, discovered the error, stopped the build, deleted lines 2 and 3 from the command, but forgot about line 1. Thanks. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Ch 5.13: Check fails to build
I am building LFS 7.3, copy-pasting from the book into scriptfiles. I restarted with ch.5 about five times, but I get no further then ch. 5.13, building Check 0.9.9. I have not seen any conspicuous errors building from the earlier paragraphs and certainly no FAILURES. The end of the make-log is: /mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-gnu/4.7.2/../../../../i686-pc-linux-gnu/bin/ld: check_thread_stress-check_thread_stress.o: undefined reference to symbol 'pthread_create@@GLIBC_2.1' /mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-gnu/4.7.2/../../../../i686-pc-linux-gnu/bin/ld: note: 'pthread_create@@GLIBC_2.1' is defined in DSO /tools/lib/libpthread.so.0 so try adding it to the linker command line /tools/lib/libpthread.so.0: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status make[2]: *** [check_thread_stress] Error 1 make[2]: Leaving directory `/mnt/lfs/sources/check-0.9.9/tests' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/mnt/lfs/sources/check-0.9.9' make: *** [all] Error 2 FAILED! libpthread.so.0 is a link to libpthread-2.17.so. Anyone any ideas? Or can I just carry on, because it is a failure in a test? Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Ch 5.13: Check fails to build
Op Thu, 04 Jul 2013 16:56:55 +0200 schreef Thanos Baloukas baloukast...@sch.gr: On 07/04/2013 05:14 PM, hans kaper wrote: Take a look there: http://www.linuxfromscratch.org/lfs/errata/stable/ Yes, it works!! Thanos and Pierre, many thanks. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Ch.5.20: findutils install error
Building LFS 7.3 I get an install-error in ch.5.20: Findutils-4.4.2: .. make[3]: Entering directory `/mnt/lfs/sources/findutils-4.4.2/find' test -z /usr/bin || /tools/bin/mkdir -p /usr/bin /tools/bin/install -c 'find' '/usr/bin/find' /tools/bin/install: cannot remove '/usr/bin/find': Permission denied make[3]: *** [install-binPROGRAMS] Error 1 make[3]: Leaving directory `/mnt/lfs/sources/findutils-4.4.2/find' The error as such is logical: user lfs cannot delete files in the host. But because the install stops there, I don't know what I miss after that. Looking into the install-log I do not see very much installed before the error and I am not clever enough to analyze the makefile. I checked the logs from the paragraphs before, but I found no errors there, neither did I miss a paragraph. Any suggestions are welcome (and don't tell me I missed an erratum, because I checked that:)). Hans. -- 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.3: Kernel hang problem
rootdelay=rootwait=Those are two options you can use. 5 seconds is usually good for rootdelay.So you could pass rootdelay=5 to the kernel when using usb devices.rootdelay=5 was not enough for me. I had to use 10 seconds.Hans.-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Coreutils make error in ch.6.26
I was building LFS 7.2, but got stuck building Coreutils in ch.6.26., probably because of an incomplete build of Perl in ch.5.28. The problem could not be solved. My last idea was to build Perl 5.16.2 instead of Perl 5.16.1, but to no avail. So I have decided to start from scratch with LFS 7.3. I want to thank Ken Moffat for accompanying me on the last part of my journey: without your attention and kind advice I would have left LFS in despair a week ago. Now I am back on the road again. Thanks a lot. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Coreutils make error in ch.6.26
Op Tue, 25 Jun 2013 21:54:07 +0200 schreef Bruce Dubbs bruce.du...@gmail.com: Just to note that the packages in Chapter 5 and Chapter 6 do not have to be identical: http://www.linuxfromscratch.org/~bdubbs/files/updating-lfs.html Thanks for the tip. At first glance an interesting piece; I will study it and try to use it. Maybe I can use my old LFS 6.4 for chapter 5 !? On the other hand, starting from scratch adds to my experience (and helps avoiding mistakes as I must have done somewhere in LFS 7.2). Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Coreutils make error in ch.6.26
Op Sat, 22 Jun 2013 22:38:11 +0200 schreef Ken Moffat zarniwh...@ntlworld.com: Odd. I don't see that in mine. Perhaps your perl tarball became corrupted. Does its md5sum match the book ? I just checked that: yes, the md5sum matches. It looks as if your build of perl in chapter 5 was incomplete. If the perl tarball wasn't damaged, something odd is going on. Anything uncommon about your host system, or the machine itself ? I'm struggling to get a grip on this ;) I scrupulously checked the commands between the book and the scriptfile I use, but they match exactly. My host system is quite normal, although a bit old: Dell dimension-8300, cpu Intel(R) Pentium(R) 4 CPU 2.60GHz, 32 bits, memory 2560MiB. I am building lfs on a external usb diskdrive on which I built lfs 6.4 succesfully a few years ago. I think I will try to use Perl-5.16.2 instead of 5.16.1. They will not differ that much. If that fails, I think I will start from scratch with LFS 7.3. Changing my scriptfiles to the latest version is not that much work. But that will not be today. Anyway, I am very grateful for your efforts to solve the problem. Hans -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Coreutils make error in ch.6.26
Op Fri, 21 Jun 2013 21:52:50 +0200 schreef William Harrington kb0...@berzerkula.org:On Jun 21, 2013, at 2:11 PM, hans kaper wrote:Can't locate unicore/Heavy.pl in @INC (@INC contains: /tools/lib/perl5/site_perl/5.16.1/i686-linux /tools/lib/perl5/site_perl/5.16.1 /tools/lib/perl5/5.16.1/i686-linux /tools/lib/perl5/5.16.1 .) at /tools/lib/perl5/5.16.1/utf8_heavy.pl line 176.This may be the problem.I suppose so too, but why? I recompiled Perl following the instructions in ch.5.28 to see if all thePerl-files were copied to /tools/; they were.It looks as if the errors were generated by Perl.I put a marker (print $unicore_dir;) above the above-mentioned line 176, but that did not generate any output,nor in my log-file, nor on screen.Have you changed any of the commands in the book?Or have you updated any package versions?I did not change any of the commands from the book; copy-pasted them in my scripts,but I can have made a mistake, but where?I did not use any updated packages, just downloaded them for LFS 7.2 with: wget -i wget-list -P $LFS/sourcesSincerely,William HarringtonI am out of further ideas for now.Hans.-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Coreutils make error in ch.6.26
I am building LFS 7.2 bij copy-pasting the commands from the book in scripts. In chapter 6.26 building Coreutils 8.19 I get an error: Making all in man make[2]: Entering directory `/sources/coreutils-8.19/man' GEN cut.1 Can't locate unicore/Heavy.pl in @INC (@INC contains: /tools/lib/perl5/site_perl/5.16.1/i686-linux /tools/lib/perl5/site_perl/5.16.1 /tools/lib/perl5/5.16.1/i686-linux /tools/lib/perl5/5.16.1 .) at /tools/lib/perl5/5.16.1/utf8_heavy.pl line 176. BEGIN failed--compilation aborted at /tools/lib/perl5/5.16.1/constant.pm line 45. Compilation failed in require at /tools/lib/perl5/5.16.1/Getopt/Long.pm line 208. BEGIN failed--compilation aborted at /tools/lib/perl5/5.16.1/Getopt/Long.pm line 208. Compilation failed in require at ./help2man line 24. BEGIN failed--compilation aborted at ./help2man line 24. make[2]: *** [cut.1] Error 2 make[2]: Leaving directory `/sources/coreutils-8.19/man' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/sources/coreutils-8.19' make: *** [all] Error 2 Knowing the thoroughness of the LFS-team I am certain I made a mistake somewhere, but where? Looking through the logs, I found the same line (Can't locate unicore/Heavy.pl in @INC ...) in the glibc-tests, but that did not result in any ERROR. I better know it before I have to restart with chapter 6 (or even ch.5) and make the same mistake again. Anybody any idea? Thanks in advance, Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Coreutils make error in ch.6.26
Op Sat, 22 Jun 2013 18:01:23 +0200 schreef Ken Moffat zarniwh...@ntlworld.com: On Sat, Jun 22, 2013 at 04:58:52PM +0200, hans kaper wrote: Op Fri, 21 Jun 2013 21:52:50 +0200 schreef William Harrington kb0...@berzerkula.org: . I see that you've re-posted your original query - please don't do that, if we have anything useful to suggest we can do it in the existing thread. Sometimes, particularly at weekends, it can take a couple of days before everyone reads the list. I am sorry. It was not the complete original post, but the part that William Harrington sent me. I thought it was easier reading that way, but I will trim more in the future. I appreciate your advice. Perl cannot find 'Heavy.pl' I'm fairly sure you do NOT have that file You are right: it is not in /tools, neither is it in the newly built perl-15.6.1-tree in /sources. So I assume the file is not built. Apart from that: the error-log of configuring perl contained a (non-fatal) error (Can't locate File/Glob.pm) and the configure-log has somewhere in the middle: try.c:4:25: fatal error: mach-o/dyld.h: No such file or directory compilation terminated. I'm unable to compile the test program. Let's step back a little... Your problem started in a man/ directory. Let's try a different question: did you miss the line cp -v perl cpan/podlators/pod2man /tools/bin in perl ? No, both files are there. ĸen -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Coreutils make error in ch.6.26
I am building LFS 7.2 bij copy-pasting the commands from the book in scripts. In chapter 6.26 building Coreutils 8.19 I get an error: Making all in man make[2]: Entering directory `/sources/coreutils-8.19/man' GEN cut.1 Can't locate unicore/Heavy.pl in @INC (@INC contains: /tools/lib/perl5/site_perl/5.16.1/i686-linux /tools/lib/perl5/site_perl/5.16.1 /tools/lib/perl5/5.16.1/i686-linux /tools/lib/perl5/5.16.1 .) at /tools/lib/perl5/5.16.1/utf8_heavy.pl line 176. BEGIN failed--compilation aborted at /tools/lib/perl5/5.16.1/constant.pm line 45. Compilation failed in require at /tools/lib/perl5/5.16.1/Getopt/Long.pm line 208. BEGIN failed--compilation aborted at /tools/lib/perl5/5.16.1/Getopt/Long.pm line 208. Compilation failed in require at ./help2man line 24. BEGIN failed--compilation aborted at ./help2man line 24. make[2]: *** [cut.1] Error 2 make[2]: Leaving directory `/sources/coreutils-8.19/man' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/sources/coreutils-8.19' make: *** [all] Error 2 Knowing the thoroughness of the LFS-team I am certain I made a mistake somewhere, but where? Looking through the logs, I found the same line (Can't locate unicore/Heavy.pl in @INC ...) in the glibc-tests, but that did not result in any ERROR. I better know it before I have to restart with chapter 6 (or even ch.5) and make the same mistake again. Anybody any idea? Thanks in advance, Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Support archives
I cannot reach the LFS Support Archives:Page not found. Something wrong? Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] No to rewrite the wheel but I'm scripting the LFS Book...
Op Sun, 01 Jan 2012 10:03:05 +0100 schreef jasonps...@jegas.com:
I know there is ALFS and JALFS or whatever and I might refer and or use
those but for me, I personally
like the book layout, so I'm making scripts for each CHUNK along the
way.
HAPPY NEW YEAR FOLKS!
--Jason P Sage
Have you read the Hint More Control and Package Management using Package
Users (v1.2)
(www.linuxfromscratch.org/hints/read.html).? Also look into the enclosed
script; somebody send it to me,
but I don't remember who. There was also a discussion about this topic
last year or the year before
on this support-site.
Hans.
# Begin Build for PACKAGE
# The basis for this script, and actually the meat of it, came from
# Matthias Benkman's More Control and Package Users package management
# system. The hint for this is found at the Linux From Scratch Hints
# web page.
# This version came from a CLFS build, by Dan McGhee in September of
# using CLFS-SVN-snapshot date-x86_64-Multilib book. I owe a large
# debt of gratitude to Ken Moffat, a LFS developer, from whom I took
# a large portion of the start_commands.
# Run this script from the packag users home directory by invoking it with
# the package name--ex. vim-7.2. It will find the tarball in $PACKAGES,
# untar it, change to the created directory and configure, make install.
# Then it will clean up by creating a list of the installed files and
# remove the source tree.
# NOTE: There are sections in this script that must be uncommented to
# accomplish various things: 32 bit builds, 64 bit builds and
# running a test suite. Scroll through and you will find them.
# It will create 6 log files in the $HOME directory:
# configure.log: All messages output during configure
# configure.err: Just the errors output during configure
# make.log: All messages output during make
# make.err: Just the errors output during make
# install.log: All messages output during make install
# install.err: Just the errors output during make install
# variables
package=$@
logdir=$package-32bit-logs
PACKAGES=/sources
CURRENT=$package
# Begin function definitions
start_commands () {
# Make a log directory
mkdir -v $logdir
# determine type of tar, and name of its directory
# enter with current set to version name
# returns with current set with tar/type,
# directory set, and tarcmd set
if [ -r ${PACKAGES}/${CURRENT}.tar.bz2 ]; then
CURRENT=${CURRENT}.tar.bz2
TARCMD='-j'
elif [ -r ${PACKAGES}/${CURRENT}.tar.gz ]; then
CURRENT=${CURRENT}.tar.gz
TARCMD='-z'
elif [ -r ${PACKAGES}/${CURRENT}.tgz ]; then
CURRENT=${CURRENT}.tgz
TARCMD='-z'
elif [ -r ${PACKAGES}/${CURRENT}.tar ]; then
CURRENT=${CURRENT}.tar
TARCMD=
elif [ -r ${PACKAGES}/${CURRENT}.tbz2 ]; then
CURRENT=${CURRENT}.tbz2
TARCMD='-j'
elif [ -r ${PACKAGES}/${CURRENT}.tar.xz ]; then
CURRENT=${CURRENT}.tar.xz
TARCMD='-J'
else
echo identify: unable to identify tar for $CURRENT
exit 1
fi
echo testing ${CURRENT}
# /dev/null may not exist at start of ch6
# changed to test for character special file instead of file
#if [ -c /dev/null ]; then
# NUL='2/dev/null'
#fi
# util-linux uses ./ at start of directory names
#DIRECTORY=`tar -tv $TARCMD -f ${PACKAGES}/${CURRENT} $NUL | head -n 1
| awk '{ print $6}' | sed s'@^./@@' | \
# making NUL defined causes tar to try to look for 2/dev/null in the
tarball.
DIRECTORY=`tar -tv $TARCMD -f ${PACKAGES}/${CURRENT} | head -n 1 | awk
'{ print $6}' | sed s'@^./@@' | \
cut -d '/' -f 1`
if [ -z $DIRECTORY ]; then
echo indentify: error in trying to determine directory name
exit 1
fi
echo identify: directory is $DIRECTORY
# Untar
echo Untarring $CURRENT
tar -x $TARCMD -f $PACKAGES/$CURRENT
echo Entering source tree
cd $DIRECTORY
packagedir=$DIRECTORY
echo $packagedir
}
configure_commands()
{ :
CC=gcc ${BUILD32} ./configure --prefix=/usr
}
make_commands()
{ :
make
}
install_commands()
{ :
make install
}
test_pipe()
{
for i in ${PIPESTATUS[@]}
do
test $i != 0 { echo FAILED! ; exit 1 ; }
done
echo successful!
return 0
}
# End Functions
# Begin tests and function calls for fresh and failed builds.
# This one recovers from failed make.
if [ -e $logdir/make-`echo $package`.err ] \
[ ! -e $logdir/install-`echo $package`.err ]; then #Now build
cd $HOME/$packagedir
echo -n Building `echo $package`...
{ make_commands 31 12 23 | tee $Home/$logdir/make-`echo
$package`.err ;} $HOME/$logdir/make-`echo $package`.log
test_pipe echo -n Installing
Re: Book bug?
Does this happen with any other PDF readers, or is it just evince? I have not got any problem with copy-paste from the PDF-book. Hans. David Shaw - -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Shadow's su using Package Users will not switch
Op Thu, 23 Jun 2011 00:18:45 +0200 schreef William Immendorf will.immend...@gmail.com: On Wed, Jun 22, 2011 at 3:14 PM, jpkaper spaky...@xs4all.nl wrote: After installing Shadow from chapter 6.55, switching as root to a new user with su gave the error:Setgid: Operation not permitted. I was able to work around this problem by replacing Shadows's su with su(-tools) from the tools-directory, but I like to know where the problem comes from. Has it to do with the Package Users system? Experience tells me that you need to make su setuid in order for it to work. To do this, run chown root /bin/su chmod 4755 /bin/su William, That works. Thanks a lot. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Grub with Windows XP on a separate disk
Op Wed, 15 Dec 2010 18:08:14 +0100 schreef Andrew Benton
b3n...@gmail.com:
Hello World!
In order to make room for more games (the only reason I run Windows) I
recently reinstalled Windows XP on a separate hard disk. If I go into
the BIOS boot menu and get the BIOS to boot that disk then Windows
boots fine. However, I can't get grub to boot it. The screen goes blank
and I get a cursor blinking in the top left corner. The relevant entry
in grub.cfg looks like this:
menuentry Windows {
set root=(hd1,1)
chainloader +1
}
I get the same result if I try this:
menuentry Windows {
set root=(hd0,1)
chainloader +1
}
/dev/sda1 is currently blank. Windows is installed on /dev/sdb1.
andy:~$ cat /boot/grub/device.map
(hd0) /dev/sda
(hd1) /dev/sdb
andy:~$
I've a feeling this is because I have grub installed on the MBR of my
linux disk and in the BIOS boot order the windows disk is the second
one. I think windows XP likes to be on the first partition of the first
disk.
I do not think so. I have three XP-installations on two harddisks and they
all boot fine.
I have Grub 2 on the first harddisk (hd0) and it boots XP on the 2nd
harddisk with:
menuentry Windows NT/2000/XP (loader) (on /dev/sdb1) {
insmod fat
set root=(hd1,1)
search --no-floppy --fs-uuid --set 14bf-ed52
drivemap -s (hd0) ${root}
chainloader +1
(result of update-grub and grub-install in Linux Mint on the 1st harddisk)
It does not boot XP on the 1st harddisk, but I have not had the time to
figure out why.
If I know more, I let you know, but I give priority to building LFS 6.7
(problem building gcc;
did something wrong in the toolchain, I presume).
Maybe also this site can help you:
http://kubuntuforums.net/forums/index.php?topic=3106368.0
See under the heading The Quick-and-Dirty Solution.
Hans.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: Grub2 and ext4
Op Tue, 19 Oct 2010 23:32:59 +0200 schreef linux fan linuxscra...@gmail.com: I am always afraid of touching MBR and would almost never do so No problem if you have two or more harddisks, USB-sticks or USB-drives to boot Linux from. Just make a copy of the MBR in danger with dd and put it back after booting from another drive if something goes wrong. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS on USB?
Op Mon, 08 Mar 2010 02:09:15 +0100 schreef littlebat dashing.m...@gmail.com: On Sun, 07 Mar 2010 21:08:18 +0100 Hans Kaper spaky...@xs4all.nl wrote: My grub entry for my LFS6.4 stick is: title Linux From Scratch 6.4 Kernel 2.6.30.2 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/uba1 Omit the root=/dev/uba1-option. root (hd0,0) points already to the device you want to boot from. It should can't be omited, root (hd0,0) is the prefix location of your kernel or image file, and root=/dev/* indicates your device that / directory on it. For example, when your kernel file is (hd0,0)/boot/kernelfile, your root directory / can be root=/dev/hdc2 . You are right, but most people install the kernel and root on the same device and then it is better to omit the root=-option, because the device-identifier changes depending on which computer you plug in the USB-device, as Bahot Utot points out in another post in this thread. Hans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS on USB?
My grub entry for my LFS6.4 stick is: title Linux From Scratch 6.4 Kernel 2.6.30.2 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/uba1 Omit the root=/dev/uba1-option. root (hd0,0) points already to the device you want to boot from. On all my builds the root= part always points to /dev/uba1 Hope this helps. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS-6.6 booting USB grub
Op Thu, 25 Feb 2010 17:23:58 +0100 schreef Baho Utot baho-u...@columbus.rr.com: I would like to boot LFS-6.5 on USB I have it working except that when I change from my desktop computer which has 3 drives to my laptop that only has one drive I must edit grub and change the kernel line to point to the prober /dev/sdx drive I would like to boot grub on the USB drive and have it come up without editing the kernel line for the drive I have searched the web looking for fixes and tried using UUID and Labels. I have used e2label to set the label on the USB drive to LFS-6.5 # The first entry is for LFS. title LFS 6.5-SDD1 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 rootdelay=10 It surprises me that this works on your laptop with only one drive. Why should your USB-device on the laptop also be named sdd1 as it is on your desktop? title LFS 6.5-UUID root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=UUID=6cb4887-1eb2-4180-9566-391a8b3f7b45 ro rootdelay=10 title LFS 6.5-LABEL root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=LABEL=LFS-6.5 ro rootdelay=10 I tried these too, but did not succeed either. The succesful advice I got was to delete the root= option altogether when booting from the USB-device because the bootpartition is already defined with the root(hd0,0) Grub-entry. I am curious to know what the experts have to say about why the UUID- and LABEL-options don't work. Hans Kaper. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Unable to boot from usb harddisk
Op Thu, 21 Jan 2010 22:48:42 +0100 schreef Hans Kaper spaky...@xs4all.nl: Last september I posted a problem about not being able to boot from an USB Harddisk. That problem was solved by: - inserting a kernel bootoption rootdelay=10, - deleting a root= kernel bootoption, because the kernel starts looking for initialisation info by default in its own partition first. Recently I split the partition in front of the LFS-partition. I changed Grub's menu.lst and fstab accordingly. But then my problems returned. First the kernel panicked, because it could not find its init. That was solved by inserting a root=sdc9 kernel-option anyway (although I thought that was unnecessary)(sdc9 is my LFS-partition). A little later in the boot-proces the old kernel-panic - not syncing: VFS: Unable to mount root fs on unknown-block (2,0), returned. I increased the rootdelay to 20, but that made no difference (although I did not see the 10 seconds extra on the screen, but that can have something to do with the fact that information is buffered first before it goes to the monitor) Before this error occurs, the kernel enumerates the available partitions. There I see something like sdc9 sdc4 (sdc9 is my LFS-partition). sdc4 is an ext2-partition that is empty. It looks as though the kernel is looking somewhere else for its information than in its own partition. Is there anywere else partition-information that the kernel uses? If yes, where is it stored? Have I overlooked something? It's a pity that nobody cared to react to my post. The problem is still there, although I was able to boot into LFS just by removing one of the partitions in front of my LFS-partition, so that the LFS-partition had the same number as before the splitting. But the question still remains: why does the kernel panic when the partitionnumber of its rootdevice changes? -- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Unable to boot from usb harddisk
Last september I posted a problem about not being able to boot from an USB Harddisk. That problem was solved by: - inserting a kernel bootoption rootdelay=10, - deleting a root= kernel bootoption, because the kernel starts looking for initialisation info by default in its own partition first. Recently I split the partition in front of the LFS-partition. I changed Grub's menu.lst and fstab accordingly. But then my problems returned. First the kernel panicked, because it could not find its init. That was solved by inserting a root=sdc9 kernel-option anyway (although I thought that was unnecessary)(sdc9 is my LFS-partition). A little later in the boot-proces the old kernel-panic - not syncing: VFS: Unable to mount root fs on unknown-block (2,0), returned. I increased the rootdelay to 20, but that made no difference (although I did not see the 10 seconds extra on the screen, but that can have something to do with the fact that information is buffered first before it goes to the monitor) Before this error occurs, the kernel enumerates the available partitions. There I see something like sdc9 sdc4 (sdc9 is my LFS-partition). sdc4 is an ext2-partition that is empty. It looks as though the kernel is looking somewhere else for its information than in its own partition. Is there anywere else partition-information that the kernel uses? If yes, where is it stored? Have I overlooked something? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Errors in compiling glibc
Op Thu, 08 Oct 2009 14:23:36 +0200 schreef Martijn van Duren martijn...@gmail.com: Hello, I'm trying to compile LFS by the book (SVN-20090929), using the LFS-liveCD, but I get errors in chapter 6.9 when doing the check. I have not seen a reaction on your post yet, but, inexperienced as I am, I fear that I cannot be of much help to you. But on what I have seen in other posts I have got the impression that many errors are caused by not following the book in detail. So maybe it helps to post the commands you used in chapter 6.9 up until the errors so somebody else can have a look at it and find the culprit. Hans Kaper. -- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Valid Group Names
Op Sat, 03 Oct 2009 17:57:14 +0200 schreef Dan McGhee beesn...@grm.net: When I build I use the More control and Package Users management system. Each time I have built an LFS system, after I install Shadow, I cannot use the actual package name for a user or group. For example, rsyslog-4.4.1. This has not been important to me until this build during which I have written a script for all my builds. It's highly dependent on $(whoami). I use the same package-management system in building form LFS 6.4, but I don't have that problem. I use install_package 'Packagename' packagename packagename, as suggested by the package-management system. install_package 'Test.1.2' test.1.2 test.1.2 works fine with me. That the problem arises after the installation of Shadow does not surprise me. After the installation groupadd from LFS-Shadow takes over from Shadow of your hostsystem. But why do you use the details in the first place? I use the suggestions from the package-management system and strip the details, only keeping the name of the package. Hans Kaper -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Kernel panic - booting from USB harddisk
Op Fri, 02 Oct 2009 01:38:29 +0200 schreef Baho Utot baho-u...@columbus.rr.com: Hans Kaper wrote: Op Thu, 01 Oct 2009 00:19:29 +0200 schreef Baho Utot baho-u...@columbus.rr.com: J.P.Kaper wrote: I am building LFS from book 6.4 on an ext3 logical partition of an external USB harddisk. My host system is SUSE 10.3 on one of my two internal harddisks. Booting from the USB disk fails with [4.410067] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (2,0) I have done some more research on your problem. Try this in /etc/fstab for the USB disk UUID=6342a6b5-25cf-4d01-a318-68309d12ab5b / ext3 defaults 1 1 change the blkid to the correct value based on $ blkid /dev/sdxx Are you trying to boot with grub on the USB drive? If so try changing /boot/grub/menu.lst kernel line like this kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 rootdelay=15 ro quite change the /dev/sdd1 to the correct value for your USB drive If you have success then try to use UUID in the menu.lst file like this kernel /boot/lfskernel-2.6.30.2 root=UUID=6342a6b5-25cf-4d01-a318-68309d12ab5b rootdelay=15 ro quite It looks like grub or the kernel can give the kernel panic about not syncing. I like to use UUID or LABEL in grubs menu.lst file. Grub can process UUID of LABELs and it makes sure that the drive/partition that you are trying to boot doesn't change or get mixed up. ( It keeps me from getting mixed up trying to keep whos bootin from here to where ? straight ) But. After you can successfully load/execute the kernel, and grubs done it's work I think the kernel can not locate its root file system and barfs giving the kernel panic. I have found that UUID or LABELs in /etc/fstab gives you the kernel panic because the kernel can not process UUID or LABELs without using a initrd as udev has not been started. So you need to use /dev/sdx there. example: title LFS 6.5 - USB root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 rootdelay=15 ro quite That makes the USB tied to that PC :( If you need it to boot on another PC you need to edit the grub line from the menu when grubs starts up or use an initrd. Hope this helps. You are right. root=/dev/sdc8 works fine. root=UUID=. fails with a Grub-error 11: Unrecognized device string. My intention was indeed to use LFS on the usb-disk on different computers. Maybe I will try to build an initrd sometime, just as an exercise; changing the Grub-line every time I change computers looks not very neat to me. But as you have seen in the post from Danny Engelbarts, leaving out the root= altogether is an even simpler solution. I think we can close this thread now. I am very grateful for your interest; your suggestions have brought me a good step further in understanding the workings of Linux. Hans Kaper. -- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Kernel panic - booting from USB harddisk
Op Wed, 30 Sep 2009 01:56:40 +0200 schreef Baho Utot baho-u...@columbus.rr.com: J.P.Kaper wrote: I am building LFS from book 6.4 on an ext3 logical partition of an external USB harddisk. My host system is SUSE 10.3 on one of my two internal harddisks. Booting from the USB disk fails with [4.410067] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (2,0) From devices.txt 2 blockFloppy disks 0 = /dev/fd0Controller 0, drive 0, autodetect 1 = /dev/fd1Controller 0, drive 1, autodetect 2 = /dev/fd2Controller 0, drive 2, autodetect 3 = /dev/fd3Controller 0, drive 3, autodetect 128 = /dev/fd4Controller 1, drive 0, autodetect 129 = /dev/fd5Controller 1, drive 1, autodetect 130 = /dev/fd6Controller 1, drive 2, autodetect 131 = /dev/fd7Controller 1, drive 3, autodetect Some one correct me if I am wrong but It looks to me that it is trying to boot/read/sync the floppy disk I don't recognize the former text from my problem. But that problem is solved now, as you can see from another post by me. But nevertheless I am very grateful for your help. Hans Kaper. -- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Kernel panic - booting from USB harddisk
Op Wed, 30 Sep 2009 02:42:09 +0200 schreef Mike McCarty mike.mcca...@sbcglobal.net: Baho Utot wrote: J.P.Kaper wrote: I am building LFS from book 6.4 on an ext3 logical partition of an external USB harddisk. My host system is SUSE 10.3 on one of my two internal harddisks. Booting from the USB disk fails with [4.410067] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (2,0) From devices.txt 2 blockFloppy disks 0 = /dev/fd0Controller 0, drive 0, autodetect 1 = /dev/fd1Controller 0, drive 1, autodetect 2 = /dev/fd2Controller 0, drive 2, autodetect 3 = /dev/fd3Controller 0, drive 3, autodetect 128 = /dev/fd4Controller 1, drive 0, autodetect 129 = /dev/fd5Controller 1, drive 1, autodetect 130 = /dev/fd6Controller 1, drive 2, autodetect 131 = /dev/fd7Controller 1, drive 3, autodetect Some one correct me if I am wrong but It looks to me that it is trying to boot/read/sync the floppy disk It is, but that's likely just that it's trying one thing after another, and failing, then producing a report on the last thing it tried. Mike See my reply to Baho Utot. Problem solved now. Thanks for your attention, Mike. Hans Kaper. -- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Kernel panic - booting from USB harddisk
Op Wed, 30 Sep 2009 00:05:52 +0200 schreef Danny Engelbarts d.engelba...@gmail.com: On Tuesday 29 September 2009 22:19:24 Hans Kaper wrote: Good suggestion. So once again I made an entry in Grub's menu.lst, carefully copying the disk/by-id-field from the SUSE-entry that boots allright from the usb-disk (and checked it with the udevinfo information), trying the partition-numbers 7,8 and 9, but to no avail. The kernel-suggestions for valid partition device nodes includes the partitions of the usb-disk, including number 8, which, I think, is the right number. I believe I see the problem here, I wouldn't be surprised if the UUID label when booting from the USB is different to the UUID when booting Suse. Actually I would be surprised if they were! I don't exactly understand what you mean. I have two Suse-instances: one on an internal harddisk, one on the usb-disk. Both instances give the same UUID's. Anyway, it looks like you are not using an initrd image. That means the root= part probably isn't necessary, by default the kernel will use the partition it is booted from as the root device which is what you'd want in this case. That is a clever work-around!!! And it worked!! After changing an error in fstab (/mnt/lfs had to be /) and remembering my password, I was able to log in. The LFS-book suggests a root= entry for LFS and I wonder whether it should better be left out there. On the other hand, it should work in that way too. As a former researcher I want to know how and, if not, why not. I will further try out the suggestions from Baho Utot. Anyway, Danny, I am very grateful to you for supplying the solution to my problem. And of course to all the others on the forum who took notice of my question, took the trouble of looking into it and gave suggestions for an answer. I was pleasantly surprised by all the reactions. I hope to gather more experience in the future and be able to help others in the same way. Hans Kaper. -- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Kernel panic - booting from USB harddisk
Op Thu, 01 Oct 2009 00:19:29 +0200 schreef Baho Utot baho-u...@columbus.rr.com: J.P.Kaper wrote: I am building LFS from book 6.4 on an ext3 logical partition of an external USB harddisk. My host system is SUSE 10.3 on one of my two internal harddisks. Booting from the USB disk fails with [4.410067] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (2,0) I have done some more research on your problem. Try this in /etc/fstab for the USB disk UUID=6342a6b5-25cf-4d01-a318-68309d12ab5b / ext3 defaults 1 1 change the blkid to the correct value based on $ blkid /dev/sdxx Are you trying to boot with grub on the USB drive? If so try changing /boot/grub/menu.lst kernel line like this kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 rootdelay=15 ro quite change the /dev/sdd1 to the correct value for your USB drive If you have success then try to use UUID in the menu.lst file like this kernel /boot/lfskernel-2.6.30.2 root=UUID=6342a6b5-25cf-4d01-a318-68309d12ab5b rootdelay=15 ro quite As I said in another post, I am able to boot now by way of a work-around. But I am still interested to know why my former way did not work, so I will try your suggestions (if the forum-moderator allows us to carry on the thread). Hans Kaper. -- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Kernel panic - booting from USB harddisk
Op Tue, 29 Sep 2009 04:32:17 +0200 schreef Spahn, Daniel dsp...@cuh2a.com: Booting from the USB disk fails with [4.410067] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (2,0) Have you tried changing the partition number up or down by one? Yes, I have, but without result. I have a SUSE 10.3-installation on a primary partition of the same USB-disk and that boots fine. But from the SUSE kerel-configuration I have not been able to figure out the relevant difference with the LFS-kernel-configuration. I tend not to use a configuration across distros, unless I had built the first from a pure kernel source from kernel.org or similar. In fact, most of my kernel configurations are done from scratch, because I have had trouble in the past in areas where the flavor customized the kernel for the sub-version of the distribution. Of course you are right. I only tried to figure out what was missing or wrong in the LFS-kernel by comparing it with a kernel on the same drive that did boot. Try re-partitioning, setting the boot flag, and swap partition type. I prefer cfdisk. I will certainly try that, but my first callenge now is to be able to boot from the USB-disk and understand why it does not now. It took me a long time with LFS to come as far as this (and I enjoyed it very much and learned a lot from it), so I hope somebody can help me with the last hurdle. As much as I like LFS, it's not great for a production OS. Without distancing yourself from the OS too much, Gentoo automates the tedious end of things, but specific customizations can be applied relatively easily. Maybe you are right. I like LFS because it gives the opportunity to build a system from scratch and by doing that learning a lot about the details of Linux. I also like the support forum with people that will try to help you when you got stuck. But I will have a look into Gentoo sometime! Thanks a lot. Hans. -- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Kernel panic - booting from USB harddisk
Op Sat, 26 Sep 2009 21:29:08 +0200 schreef Baho Utot baho-u...@columbus.rr.com: Ken Moffat wrote: 2009/9/26 J.P.Kaper spaky...@xs4all.nl: Maybe somebody else can find the right suggestion to let me solve my problem. Hans Kaper. One of the problems with usb drives is that they can take a long time to appear. I've never tried to boot from usb, but ISTR that there is a command-line argument to wait for the drive. A quick look in the kernel's Documentation/kernel-parameters.txt (you can read it from the tarball in 'view' if you don't have the kernel source tree handy) suggests boot_delay= might be what I'm thinking of. Perhaps try boot_delay=15 which should be a ridiculously long wait. If it works like that, cut it down until you've reduced it too far, then back off a bit. I expect you've already seen the following guides, but just in case: http://www.damnsmalllinux.org/wiki/index.php/USB_Booting and http://wiki.debian.org/BootUsb ĸen I think you may be looking for rootdelay=seconds from Documentation/kernel-parameters.txt rootdelay=[KNL] Delay (in seconds) to pause before attempting to mount the root filesystem Others to try: boot_delay=Milliseconds to delay each printk during boot. Values larger than 10 seconds (1) are changed to no delay (0). Format: integer usb-storage.delay_use= [UMS] The delay in seconds before a new device is scanned for Logical Units (default 5). The above hints were a step forward for my problem, but not the ultimate solution. Adding the kernel-parameter boot_delay=9000 and/or usb-storage.delay_use=15 changed nothing. But adding rootdelay=10 made a difference: the kernel still would not boot, but in the suggestions by the kernel of partitions to boot from, my usb-disk appeared! Adding boot_delay=9000 made no difference. So the kernel recognizes my usb-disk, but why it will not boot from there is still a puzzle to me. Copying the whole LFS-installation from a logical to a primary partition on the usb-drive made no difference. Any further ideas are very wellcome!! -- -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
