Language Selection

English French German Italian Portuguese Spanish

Linux From Scratch 6.1 (part 1?)

Filed under
Linux
Reviews
-s

Linux From Scratch 6.1 was released on July 10 and I thought I'd take a look. This will be my third attempt at installing LFS. My first attempt was way back when I still ran Mandrake everyday (ie. - about 3 years ago) and I got as far as setting up the filesystem directories when I decided this was too much like work and abandoned the quest. My second was not so long ago when 6.0 was the latest and greatest version. I got a base installed and booted, but could not get xorg (blfs) to build. The project was put on the back burner until it simmered away. Today I begin again. Will I have the time and inclination to complete it this time? You know what they say, "third time's a charm!" ... or it is "three strikes, your out?" We'll see.

The first thing I did was untar/uncompress the LFS-Book-6.1-html. Yep, that's how this unique distro is distributed - not by iso or stage tarball, but by instructions. I fired up Konqueror and navigated to the index.html where I read the prerequisites telling me if I didn't know about linux, read "some links to newbie's guides". Then next the system requirements.

I wanted to build from my gentoo install, and I knew that I was using a 2.6.12 kernel with gcc 3.4.4. The system requirements stated that "the host must be running at least a 2.6.2 kernel compiled with GCC-3.0 or higher." So, I guess I'm good.

I recall reading their "book" from cover to cover, or at least until the building of xorg last time, so I refreshed my memory some by reading the preface and introduction. I was a little anxious to get compiling, but I knew if I skipped this step - I'd be sorry later. One of the subheadings is called Errata, and they recommend clicking on the link and checking for any pressing issues prior to building. Yippee - none were listed yet - this version was only just released today. I'll be one of their guinea pigs. I could just follow the guide.

Heyyyy, Chapter 1.1 - How to Build an LFS System states that "As an alternative to installing an entire separate distribution onto your machine, you may wish to use the Linux From Scratch LiveCD. The CD works well as a host system, providing all the tools you need to successfully follow the instructions in this book. Additionally, it contains all the source packages, patches and a copy of this book. So once you have the CD, no network connection or additional downloads are necessary. For more information about the LFS LiveCD or to download a copy, visit http://www.linuxfromscratch.org/livecd/." augh well.... Skipping to Chapter 2... Big Grin

I already had a partition set up and a filesystem created, so... whoops, it's reiser and they recommend ext2 or 3. I guess I'll mke2fs /dev/hda13 and tune2fs -j /dev/hda13. Next, mount it. I still had my /mnt/lfs from the last attempt, so I export LFS=/mnt/lfs as instructed as well as mount /dev/hda13 $LFS and mkdir $LFS/sources. Thus begins the tendious task of downloading all the recommended packages and patches. One bit of advice for ya here: download all tar.gz packages. In my infinite wisdom, I chose as many tar.bz2 packages as possible, but not all are available in bunzip2. Later it would make for more delays when having to check if the package was gunzip'd or bunzip'd and issueing the correct command to decompress.

Next was setting up some further environmental variables and stuff, followed by binutils. LFS offers a suggestion to keep a time on this first compile so that you may be able to estimate how long the remaining packages take to compile - measured in BSUs. My BSU for binutils was:
real 2m26.874s
user 1m44.221s
sys 0m29.469s

As the first pass of gcc builds, I can report the problems encountered so far with book. Root directory owned by root and package sources and directory owned by host system user, causing permission problems when we got to the mkdir ../binutils and ../gcc build directories. Also, no /home/lfs instruction which caused the su - lfs to fail the first attempt. I mkdir /home/lfs and chown lfs:lfs /home/lfs and then as root from host system, just chowned lfs:lfs /mnt/lfs. I hope this is okay and doesn't cause problems later on. But with everything being built and installed by the lfs user, that is of course the permissions on all the files and executables. It only stand to reason the initial directory permissions should be the same. We'll see.

At this point I was just more or less highlighting and pasting the given commands into the virtual environmental shell. All went well and it was time to chroot into lfs and continue with chapter 6. The permissions issue mentioned in the previous paragraph are addressed here. A root group/user is added and directory permissions are changed.

From that point on I just followed the guide through the package recompiles. It was as they say "by the book". I configured the kernel and skipped the grub portion. I set up some of the config files "the book" suggested - some I copied from gentoo, like my /etc/resolv.conf. I copied the boot kernel and files to /boot, then mv'd that to /boot.bak. I then mounted my hda5 as /boot and copied all the files from /boot.bak to /boot. I set up an entry in my gentoo's lilo.conf, ran lilo and rebooted.

The system rebooted into my fresh LFS install without issue. All the included configuration instructions seemed fairly complete and accurate enough given the users' input and ability to know small details about their machines. Overall I found the instructions in the book easy to follow and accurate. I think anyone with basic commandline experience could have a successful install and with just a few more hints (for example: delete previous gcc-build directory/sources and untar/compress fresh), a newbie might too. Tho LFS is designed to be just your basic system ready for your customizations and additions, the book really needs to include at least a console web browser (links or lynx) and wget. It took me about 10 hours or so to go from clicking on the html book to logging into my new system (bearing in mind I had to break from time to time to eat, watch some movies, and fight with my boyfellar). So for anyone wanting their own homemade system or to learn more how a Linux operating system is put together and works (if one pays attention to valuable information/explanations included as opposed to <cough>mindlessly <cough>copying and pasting), I can recommend LFS-6.1.

Now on to BLFS. Unfortunately Beyond Linux From Scratch is always a book behind it seems. To me it's not a real install until one can log into a window manager. Hopefully by next weekend BLFS will be caught up and we can possibly have a part 2. But I have a base ready and waiting for it. Big Grin

I remember...

Within my first year of linux, back under RH 7 or Mandrake.
I seem to remember I had a nice LFS install on a smaller partition (500Mb), the biggest problem I had was adding it to my host lilo config.
I remember I was able to boot to bash in under 5sec due to the lack of what some people would consider 'functionality' and under 10sec for a minimal X session with mplayer fired up waiting for me to play a dvd.
I even got as far as installing KDE 3.5 on that sucker a few weeks before it became available under Mandrake (that was a mission with dial-up) I ended up buying a source cd from somewhere Big Grin

I ended up down this route after finding I had to keep rebuilding my kernel for a winmodem which had a working driver which wouldn't be accepted into the mainline kernel or the distro ones either.

Reiser is available under LFS provided kernel support and reiserfsprogs (see BLFS) are built and installed in the minimal system (stage 2 i seem to remember).

I eventually gave up with this as I like living on the cutting edge too much (escpecially with KDE4) and my laptop is not capable of rolling it's own gentoo weekly which requires less personal input into the configuration and dependency managemnet than LFS which is quite intensive for watching dependencies (although there's no circular dependencies which makes sence).

Speaking of which I installed paco as a text based package manager which I still grab again for my SuSE install when I have to compile that all-so-important package from source. I find it's quicker than me generating my own rpm, which (I suppose) would be easier to upgrade...

At the moment I have a chroot jail on my system which I copied loosley from LFS which allows me to do any work with the latest compilers etc without polluting my main system.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Graphics: Vulkan and Vega M

  • Vulkan Virgl Has Kicked Off For Supporting This Graphics/Compute API Within VMs
    Of the hundreds of projects for this year's Google Summer of Code, there are many interesting GSoC 2018 projects but one of those that I am most excited for is Vulkan-Virgl for getting this modern API supported with hardware acceleration by guest virtual machines. As implied by the name, this effort is based upon the Virgl project started by David Airlie and originally tasked with getting OpenGL acceleration to guest VMs using a fully open-source Linux driver stack. Virgl has been in good shape for a while now with OpenGL, while this summer the hope is to get the Vulkan API support going for opening up VMs to using this high-performance graphics and compute API.
  • AMDVLK Driver Lands Half-Float Additions, Many Other Improvements
    There's been another weekly-ish public code push to the AMDVLK open-source AMD Vulkan Linux driver stack and this time around it's heavy on feature work. There has been a fair amount of changes pertaining to half-float (FP16) support including support for the AMD_gpu_shader_half_float extension, prepping for VK_AMD_gpu_shader_half_float_fetch, FP16 interpolation intrinsics and register settings, and more.
  • Vega M Graphics On Intel Kabylake G CPUs Are Beginning To Work Under Linux
    We have been covering the Linux driver upbringing of "Vega M" for the Vega/Polaris graphics found in select newer Intel "Kabylake G" processors. The code is still in flight before it will work in all released versions of the Linux driver components, but for those willing to build the code or rely upon third party repositories, Vega M is now working on Linux. As I have covered in various past articles, the open-source driver support for Radeon Vega M is queued into DRM-Next for the upcoming Linux 4.18 kernel cycle, Mesa 18.1 albeit with new hardware I always recommend using the latest Git (current Mesa 18.2), and there are also binary GPU microcode files needed too.

Plasma 5.13 – Amazing Tux, How Sweet Plasma

Plasma 5.13 is (going to be) a very nice release. It builds on the solid foundation that is the LTS edition, and adds cool, smart touches. The emphasis is on seamless integration of elements, which is what separates professionals from amateurs. It’s all around how the WHOLE desktop behaves, and not individual programs in isolation. And Plasma is making great strides, offering a polished version of an already mature and handsome product, with extra focus on fonts, media and browser connectivity and good performance. There are some rough patches. Apart from the obvious beta issues, those goes without saying, KDE Connect ought to be a true multi-phone product, the network stack really needs to be spotless, and that means full Microsoft Windows inter-operability, Spectacle should allow for configurable shadows and alpha channel, and I want to see if the decorative backend has been cleaned up, i.e. can you search and install new themes and icons without encountering useless errors and inconsistencies. But all in all, I’m quite impressed. The changes are big and noticeable, and above all, meaningful. You don’t just get features for the sake of it, you get things that improve the quality and consistency of the desktop, that maximize fun and productivity, and there’s deep thought in orchestrating it all together. It ain’t just a random bunch of options that happen to work. I like seeing patterns in things, and I’m happy when there’s functional harmony. This spring season of distro testing hasn’t been fun, and Plasma 5.13 is balm for my weary wrists, so hurting from all that angry typing. More than worth a spin, and highly recommended. Full steam on, Tuxers. Read more Also: This week in Usability & Productivity, part 20

Sad News! Development Stopped for Korora and BackSlash Linux

It seems more and more small distributions are facing a had time. Recently we saw the crisis at Void Linux. Now we have two more small Linux distributions calling it quit, albeit temporarily. Read more

Android Leftovers