[lfs-support] Perl-5.18.1 fails one test. Does it matter? LFS 7.4
Hi all, Perl fails one test in the test suite. The output form: $ ./perl -MTestInit dist/IO/t/io_udp.t is: ==snip 1..7 ok 1 ok 2 ok 3 ok 4 not ok 5 # Failed test 5 - at dist/IO/t/io_udp.t line 64 ok 6 ok 7 ==snip I after running make -k test, I ran all the tests in the t directory as suggested by the output firm the test suite. Again only this test failed. But I didn't get any information that would explain why. The test appears to be testing whether localhost handles udp packets correctly. AFAIK the network is working normally.[1] So I have two questions. What is going on here? and: Does it matter? I am building LFS on Debian Wheesy but I suspect that isn't an important consideration. Thanks for takning the trouble to read this! Kind Regards, Bernard Footnotes: [1] /etc/hosts is set up. Moreover LFS can see my dns server and utilities such as traceroute and ping appear to be working normally, including pinging localhost. -- Your fortune cookie for today: Think big. Pollute the Mississippi. ** Fortune cookies are brought to you by GNU/Linux fortunes ** -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Configuring and Installing GRUB for {,U}EFI
On 11/06/2013 09:15 PM, Bruce Dubbs wrote: Dan McGhee wrote: On 10/28/2013 10:55 AM, Bruce Dubbs wrote: Dan McGhee wrote: When all this is successful, I could write the procedure up and post it. Then, if anyone wanted to, it could be put in the book somewhere. I could also write a hint if that were more practical. For now, just let us know your results. -- Bruce So far my results are just learning. I really haven't done anything yet, but some people may be interested in what I have found to date. This is long. Booting Linux in general, or LFS specifically *can be* as straightforward as it always has been. But if someone wants to make use of their UEFI--formerly EFI--firmware, then it is not so straightforward and can be down right complex. The first thing to note, in the current milieu, is that if you want to use *secure boot*--which is an add-on to and not synonymous with UEFI--you can install GRUB like you always have, but you will never see it boot anything because, if you're doing it in a pre-UEFI fashion, it's irrelevant to secure boot and won't be seen. Secure boot is an option in Linux right now if and only if you are using Ubuntu12.10, Fedora, OpenSuse--I don't know the version numbers--or if you have paid Microsoft $95 to let you write a key that you can use with your firmware and then figure out how to write a file that will check with the firmware to make sure all is OK and then check with the bootloader to make sure it's not vicious or malicious. (Sorry for the sarcasm). All of this means that you must turn off secure boot in your firmware setup. So far the only thing we have done in our preparation to boot LFS is turn off secure boot. Onward! The next option is to turn turn on legacy mode or CMS in the firmware. This is vendor specific so there are probably a number of things this is called. It just means going back to the way things used to be.--a bootloader in the first sector of the disk. In days of yore this was the way all computers shipped. We are all familiar with it--one bootloader, chain-linking and four primary partitions. Except if you have a GPT partition table. To insure backwards compatibility GPT partition tables now have an area at the beginning of the disk called the Protective MBR Layer. This is the place where GRUB would go on a GPT disk. This is also the place at which things start to muddy a bit. BIOS based firmware could handle only one bootloader, because it was limited to one physical spot on a fixed disk. UEFI overcomes that by using a Boot Manager to select the boot loader, and there can be, theoretically, any number of boot loaders, because these loaders now reside in a partition and not an actual physical spot on the disk. The following is the snipped results of my running parted -l /dev/sda Number Start End Size File system Name Flags 1 1049kB 420MB 419MB ntfs Basic data partition hidden, diag 2 420MB 693MB 273MB fat32 EFI system partition boot If someone has this partition, chances are they've been booting in EFI Mode. What I've read so far is that the EFI partition is usually the first partition of the disk, but it's not on mine. Another vendor thing I think. This partition contains two directories: boot and EFI. I've discovered that it's standard in Linux to mount it at /boot/efi--that's the way it is in my Ubuntu system and it's listed in /etc/fstab. Here are the results of ls /boot/efi/EFI using Ubuntu on my HP-Envy: Boot HP Microsoft ubuntu I've put this in here because the Boot Manager--whether written by HP or Microsoft I don't know--reads this directory and gives, as choices, the names of the directories--Boot comes across as Recovery for an option. You can access the Boot Manager by interrupting the boot process. On my machine it's done by holding the ESC key during boot and then selecting what I want. This is what I had to do to get to Ubuntu after I first installed it. The problem is in getting the Boot Manager to have a different default selection other than Microsoft. The solution to that is not trivial and I don't want to write about it until I study the process some more and, possibly, try it. But at this point let me show you the magic. Since version 3.3, the Linux kernel has had efi hooks. So--and I think it's this simple--you could create a directory in /boot/efi/EFi--let's call it LFS-7.4--and put the kernel in it. Then LFS-7.4 would appear as option in the EFI Boot Manager, you select it and Holy shiny boots, Batman, there's my new LFS system and I didn't even use GRUB! What I've tried to do is describe the easy ways to boot LFS now. If you want the computer to default to Grub2 with all the selections on it, then there's more. I've found two interesting articles on the nuts and bolts of all of this. Managing EFI Bootloaders for Linux http://www.rodsbooks.com/efi-bootloaders/installation.html gives a lot of good detail about EFI, elilo, Grub2 and
Re: [lfs-support] Configuring and Installing GRUB for {,U}EFI
Dan McGhee wrote: I got exuberant last night and presented the ability to boot without GRUB2 slightly simplified. You are absolutely right in a program that does the copy. I haven't researched the options yet, but I think it can be as simple as a script. I think that the main technical issue is passing boot options to the kernel. I think that can be done by building them into the kernel, but that's not very convenient. If all of this is going to somehow and sometime and someway go in the Book, I want to be able to speak from experience and not untried knowledge. I ultimately want my laptop to default to the GRUB screen so that I can choose an option. Yes, I know that if I hold down the ESC key I'll be able to do that once I have things set up, but I'm getting lazy in my old age. :) But, as an intermediate step, I could set up to boot this way. Currently, I have some technical questions about GRUB2 build options and grub-install options. I hesitate to experiment because I want to be able to boot my computer. It's easy to back-up Ubuntu and LFS, but that other bloated, leaky operating system is the problem. I don't even have a copy of that any more. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Perl-5.18.1 fails one test. Does it matter? LFS 7.4
Bernard Hurley wrote: Hi all, Perl fails one test in the test suite. The output form: $ ./perl -MTestInit dist/IO/t/io_udp.t is: ==snip 1..7 ok 1 ok 2 ok 3 ok 4 not ok 5 # Failed test 5 - at dist/IO/t/io_udp.t line 64 ok 6 ok 7 ==snip I after running make -k test, I ran all the tests in the t directory as suggested by the output firm the test suite. Again only this test failed. But I didn't get any information that would explain why. The test appears to be testing whether localhost handles udp packets correctly. AFAIK the network is working normally.[1] You need to look at the source to see what it's doing. My system passes all tests. So I have two questions. What is going on here? and: Does it matter? I suspect not. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Configuring and Installing GRUB for {,U}EFI
On 11/07/2013 11:10 AM, Bruce Dubbs wrote: Dan McGhee wrote: But, as an intermediate step, I could set up to boot this way. Currently, I have some technical questions about GRUB2 build options and grub-install options. I hesitate to experiment because I want to be able to boot my computer. It's easy to back-up Ubuntu and LFS, but that other bloated, leaky operating system is the problem. I don't even have a copy of that any more. -- Bruce I would love to be in that position, but until Apple writes a Linux version of iTunes, I'm stuck. I know, I know I could use iCloud for my phone and iPad, but I'm to cheap, er frugal, to buy more space. :) Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] GRUB2 Nuts and Bolts
This is not a rant or finger pointing session, I have a statement and
some questions about GRUB2 options both in building it and installing it.
I have found no real useful information describing how to configure
GRUB2 or in using grub-install. Anything I've been able to try or
further research comes from ./configure --help, grub-install --help
and grub-mkimage --help. I've also opened grub-install and read it to
find out some of what I want to know. The currently available GRUB
Manual goes only so far as grub-2.00-rc-1 and was written in Jun 2012.
I don't know how many rc's there were, but I know that there's more
capability in GRUB2 now than the manual covers.
Before I start into the specifics of my discoveries and questions, I
want to say that I have not found any, useful or not, descriptions of
the grub modules. Oh, I know that many are self-explanatory by their
name, like chainload, but what does efiemu do? Either I haven't
researched enough or there's nothing. If anyone knows a place where
this information exists, I would love to hear about it.
Configuring GRUB2 for an efi install means varying from the Book.
Using This document https://help.ubuntu.com/community/UEFIBooting I
learned about the option --with-platform= and the only thing that
./configure --help indicated was
--with-platform=PLATFORM
select the host platform [[guessed]]
and I didn't know whether or not this was something that I should know
because I use Linux or whether it was something specific to the GRUB2
build. Anyway, the referenced article had this command for configuring
GRUB2 for a 64-bit {,U}EFI build.
export EFI_ARCH=x86_64
./configure --with-platform=efi --target=${EFI_ARCH} --program-prefix=
Now, to backtrack a little, when I built GRUB2 during my LFS-7.4 build,
I used the configure options just as stated in the book. The message I
got at the end of configuring included the statement Platform: i386
and the installed directory in /usr/lib/grub was i386-pc.
I can't remember where I read this in my research, but something to the
effect that if grub installed its files as *-pc then it would have led
to a GRUB2 situation of writing to the MSDOS MBR of a non-GPT disk or
the MBR Protected Layer of a GPT disk. I didn't want that.
So, I did a DESTDIR install of GRUB2, with the same configure options
of the book with the addition of --with-platform=efi Then the
configure message said, Platform: x86_64-efi and efiemu runtime: No
(not available on efi. And the directory in /usr/lib/grub was
x86_64-efi. I think this is significant to those who want to ultimately
get grub on the EFI partition.
I found it also interesting that efiemu was not available. Since I
couldn't find any description of that module, I have concluded that it
does something when grub is read from the MBR Protected Layer of a GPT
disk. I really don't know, though.
Now it comes to actually installing the grub files somewhere. I know
that grub-install utilizes grub-mkimage and grub-setup to
accomplish its task. I know what grub-mkimage does, but I don't know
exactly what grub-setup does. Does it just look at a disk to see
what's there? Or does it look to see what device a particular path
refers to?
I can try to use grub-install for all of this or I can do it manually as
in the article. This is the point at which the options for grub-install
become important. And this statement from grub-install --help has me
concerned.
grub-install copies GRUB images into /boot/grub, and uses grub-setup
to install grub into the boot sector.
I don't want to install grub to the boot sector because there is none on
my disk. Just the EFI partition. And I just discovered that grub-setup
doesn't exist on my LFS build now. I'm wondering if that didn't happen
because of the configure option --with-platform=efi. Based on this
info, I'm thinking of using
$ grub-install --bootloader-id=GRUB2-LFS-7.4 --efi-directory=$my EFI
partition mount point
The manual install involves this command:
cd grub2_compiled_source_dir/grub-core
../grub-mkimage -O ${EFI_ARCH}-efi -d . -o grub.efi -p part_gpt part_msdos
ntfs ntfscomp hfsplus fat ext2
normal chain boot configfile linux multiboot
Obviously the author didn't install the compiled grub binaries so I
would be working as root in some directory and using those binaries.
${EFI_ARCH} for me is x86_64. What I don't know is why those particular
modules and should there be any more or any less. Anybody?
This is much, much longer than I intended it to be, but I think the
detail was necessary so others can understand my questions, what I'm
trying to do and how I'm trying to accomplish my goal.
Thanks,
Dan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
