Re: [lfs-support] Status of Systemd and UEFI Bios Stuff
On 8/21/2014 12:27 AM, Bruce Dubbs wrote: Alan Feuerbacher wrote: On 8/20/2014 9:48 PM, Armin K. wrote: On 21.8.2014 1:49, Alan Feuerbacher wrote: Howdy, Last I had posted here, and to the BLFS list, was that I had successfully installed an LFS system and a boatload of BLFS stuff. Been using it with good success -- no surprise. Last I looked, you LFS guys kind of frowned on using systemd, but the few things I've read on the newest help pages indicates that at least some people have been trying to install LFS using systemd. What is the status of systemd and LFS at this time? We have a systemd based LFS book, currently 7.5 stable with systemd-208 release and a development version with systemd-216 release. Ok, so the development version uses systemd. I take it that all earlier reservations have been resolved to the satisfaction of the LFS staff? No. There are two branches. One system V and one systemd. http://www.linuxfromscratch.org/lfs/read.html BLFS has also got systemd counterpart recently, but that one strictly follows the development book. Could you please expand on that? http://www.linuxfromscratch.org/blfs/read.html As for getting a UEFI bootloader working, I researched the matter extensively online late last fall, without any real resolution. I concluded that a lot of UEFI stuff was being kept secret by various players, from Fedora to ASUS to pretty much everyone else who had actually got UEFI bootloaders to work. I know that some companies such as Fedora have agreements with BIOS makers to do stuff that the average hacker like me can't do. At least, not easily. I don't remember finding a specific reason for the secrecy. I finally decided that it was due to a combination of key players really not knowing what they're doing in terms of the UEFI standard, along with a reluctance to admit that to their customers. Well you could just disable UEFI. That's what I did. The only OS that really needs it is Windows. -- Bruce Thanks! It's almost sounding like UEFI is a big nothing, except for Windows. No? Alan -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Status of Systemd and UEFI Bios Stuff
On 21 August 2014 08:28, Alan Feuerbacher alan...@comcast.net wrote: It's almost sounding like UEFI is a big nothing, except for Windows. No? Alan It's a big except, if you want to dual-boot. I solved my UEFI headaches with rEFInd, and its site has all the info about UEFI you could ever want: http://www.rodsbooks.com/refind/ http://www.rodsbooks.com/linux-uefi/ -- Emanuele Rusconi -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Status of Systemd and UEFI Bios Stuff
On 21 August 2014 10:08, Emanuele Rusconi ema...@gmail.com wrote: On 21 August 2014 08:28, Alan Feuerbacher alan...@comcast.net wrote: It's almost sounding like UEFI is a big nothing, except for Windows. No? Alan It's a big except, if you want to dual-boot. I solved my UEFI headaches with rEFInd, and its site has all the info about UEFI you could ever want: http://www.rodsbooks.com/refind/ http://www.rodsbooks.com/linux-uefi/ Yes, an excellent website with all the info one needs regarding UEFI, but rEFInd didn't work for me despite my BIOS claiming support for UEFI. As all BIOSs are proprietary, unless replaced with coreboot, it's always a case of try-it-and-see with no guarantee of success or remedies available. Richard -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[lfs-support] Booting my LFS for the first time
Okay, it crashed and burned gloriously, and I botched the grub to boot. ;-) After some studies on grub, I can now boot my distro Debian from the primary hard drive via grub commands...very cool. I can also attempt to boot my LFS from auxiliary hard drive, and it starts to boot up, and I see four penguins, a screen's worth of boot messages, and then it freezes up. Questions: Firstly, there is /dev, but it only has console and null in it, which was created earlier per the book. Is that sufficient? Is /dev populated more as the boot progresses? Seems deficient. Secondly, I don't see any initrd.img file. Do I need one? Here's what I see in /boot: config-3.13.3 grub System-map-3.13.3 vmlinuz-3.13.3-lfs-7.5 I just did make defconfig when building the kernel. I figure that would be the easiest way to test...and just to see if it works. Maybe I need to load a better driver for auxiliary USB hard drives, etc., and somehow make that apart of the kernel building, but I would need to study more on that aspect. Any ideas on how best to proceed and troubleshoot? Thanks. ~Patrick -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Booting my LFS for the first time
Oh! On Thu, Aug 21, 2014 at 10:24 PM, Hazel Russman hazeldeb...@googlemail.com wrote: On Thu, 21 Aug 2014 21:59:08 +0800 Patrick Kennedy kenned...@gmail.com wrote: Okay, it crashed and burned gloriously, and I botched the grub to boot. ;-) After some studies on grub, I can now boot my distro Debian from the primary hard drive via grub commands...very cool. I can also attempt to boot my LFS from auxiliary hard drive, and it starts to boot up, and I see four penguins, a screen's worth of boot messages, and then it freezes up. Questions: Firstly, there is /dev, but it only has console and null in it, which was created earlier per the book. Is that sufficient? Is /dev populated more as the boot progresses? Seems deficient. No, that should be sufficient. udev should make the other devices as the kernel detects the hardware. But you need the kernel's DEVTMPFS to be set to y. Secondly, I don't see any initrd.img file. Do I need one? Here's what I see in /boot: config-3.13.3 grub System-map-3.13.3 vmlinuz-3.13.3-lfs-7.5 Normally you only need an initrd for a stock kernel. When you build your own, you should compile in the necessary disk drivers rather than building them as modules, so that nothing needs to be loaded at boot. I just did make defconfig when building the kernel. I figure that would be the easiest way to test...and just to see if it works. Maybe I need to load a better driver for auxiliary USB hard drives, etc., and somehow make that apart of the kernel building, but I would need to study more on that aspect. The defconfig kernel should contain all the drivers you need but I don't know which ones it compiles in. You can check by looking in the config file in /boot. The SATA and ext4 drivers should definitely be compiled in, not as modules. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[lfs-support] 6.52
I am in section 6.52 and I get a host of failures that don't seem to have been queried of before so searching the archives didn't help. root:/sources/kmod-16# cat make.fail|grep -i fail Makefile:1041: recipe for target 'libkmod/libkmod.la' failed Makefile:1520: recipe for target 'all-recursive' failed Makefile:895: recipe for target 'all' failed Makefile:1041: recipe for target 'libkmod/libkmod.la' failed Makefile:1520: recipe for target 'all-recursive' failed Makefile:895: recipe for target 'all' failed root:/sources/kmod-16# cat check.fail|grep -i fail Makefile:1041: recipe for target 'libkmod/libkmod.la' failed Makefile:1520: recipe for target 'check-recursive' failed Makefile:1041: recipe for target 'libkmod/libkmod.la' failed Makefile:1520: recipe for target 'check-recursive' failed root:/sources/kmod-16# cat install.fail|grep -i fail Makefile:1041: recipe for target 'libkmod/libkmod.la' failed Makefile:1520: recipe for target 'install-recursive' failed root:/sources/kmod-16# tail check.fail Making check in . CCLD libkmod/libkmod.la Makefile:1041: recipe for target 'libkmod/libkmod.la' failed Makefile:1520: recipe for target 'check-recursive' failed Making check in . CCLD libkmod/libkmod.la Makefile:1041: recipe for target 'libkmod/libkmod.la' failed Makefile:1520: recipe for target 'check-recursive' failed Here are the commands I entered: #erase #Extra instructions go here #no erase ./configure --prefix=/usr \ --bindir=/bin \ --sysconfdir=/etc \ --with-rootlibdir=/lib \ --disable-manpages \ --with-xz \ --with-zlib #erase #Extra instructions go here #no erase makemake.fail #erase #Extra instructions go here #no erase make checkcheck.fail #erase #Extra instructions go here #no erase make install make -C man install for target in depmod insmod modinfo modprobe rmmod; do ln -sv ../bin/kmod /sbin/$target done ln -sv kmod /bin/lsmod #erase #Extra instructions go here #no erase cat make.fail|grep -i fail cat check.fail|grep -i fail cat install.fail|grep -i fail tail check.fail -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
