Language Selection

English French German Italian Portuguese Spanish

Linux From Scratch 6.1 - Part 2 - BLFS

Filed under
Linux
Reviews
-s

Apparently BLFS-6.1 was released well over a week ago but I didn't notice it until recently. I'd been checking back every few days since my original Linux From Scratch 6.1 article on July 11, ...I thought. Had it really been that long since I checked? Well, no matter, I have it now and unlike the LFS-html docbook, it's not lain out exactly in a linear manner. I had the basic LFS 6.1 install in place and I was hoping I only needed to pick up from there. The BLFS docbook lists such topics as security, filesystems, shells, editors, differing networking configurations, and my main goal here: X and window managers.

First thing I did in preparation to resume the install of the LFS system was to mount the lfs partition and chroot into it. I started with the "After LFS Configuraton Issues," where one is instructed on how to handle a few things under the hood like adding new users, compressing man and info pages, and setting up some user startup files. This section is straight forward and easy to follow.

The next section deals with security. I wasn't too concerned with that portion at this time and as such, most of that section was skipped. If you choose to install BLFS, you may wish to complete much more than I. I really only chose to use the PAM portion of this section, and it went without a hitch and I found the docs very informative.

The next goal was networking. As I wouldn't be using dial-up or pppoe, I just opted for dhcpcd. Again, the procedure in this section was fully explained and the task was easily accomplished. Some of the utilities and programs I chose to install were links, wget, net-tools, ntp, and fetchmail. No problems with this section, but X was next. <shudder>

Despite my trepidation, I was successful this go around. I was quite pleased with the instructions in the section to build X. It listed all dependencies and gave the commands that worked without a hitch. Other instructions included how to setup a xorg.conf, some ttf directories, and keyboard/mice devices. Next I worked on some graphic libraries that a desktop environment or window manager might need. These included qt, gtk, lesstif, and much more (and associated dependencies). All downloaded, compiled and installed with no issue. The docbook is working quite well so far.

The next course of action was get a window manager installed. KDE was once the only window manager (excuse me, desktop environment) for me. However last 6 months or so, since my Month with Fluxbox actually, I've grown quite fond of Fluxbox. This was my choice for my lfs install. Of course all went well with the fluxbox install. The blfs book didn't include feh that I felt I needed, so I had to stray off on my own for that, as well as torsmo, fbpanel and idesk.

Next I needed some internet applications. Without KDE, I was going to need a stand alone browser, email and newgroup applications. ...or I could just use mozilla or opera. That's what I decided to do. Upon booting into my LFS system I installed the nvidia graphic drivers and loaded up some modules and started X with fluxbox. Then I ran the mozilla-installer and was surfing the internet in no time at all.

I still have a lot of work to do in finding and installing other needed applications and configure torsmo and such. I also need to work extensively on the eye candy by installing some icons, more fonts and themes. ...generally make it more useful. But in so much as this is might be considered a review of sorts, I must say the authors at BLFS did a mighty remarkable job. Their instructions pick right up where LFS left off and allows one to build a homemade system without any issue. The added explanations were not only informative, but quite interesting. I found them complete without being boring. I encourage everyone who wishes to learn more how a linux system functions to give it a try. Everyone needs to do it at least once. Big Grin

Download LFS

Download BLFS

One Note: Use the nochunk version (all on one html page) as the multiple-page version isn't quite fully updated as of this writing.

Stay tuned for Part 3.

More in Tux Machines

Speeding up the Debian installer using eatmydata and dpkg-divert

The Debian installer could be a lot quicker. When we install more than 2000 packages in Skolelinux / Debian Edu using tasksel in the installer, unpacking the binary packages take forever. A part of the slow I/O issue was discussed in bug #613428 about too much file system sync-ing done by dpkg, which is the package responsible for unpacking the binary packages. Other parts (like code executed by postinst scripts) might also sync to disk during installation. All this sync-ing to disk do not really make sense to me. If the machine crash half-way through, I start over, I do not try to salvage the half installed system. So the failure sync-ing is supposed to protect against, hardware or system crash, is not really relevant while the installer is running. Read more

Samsung's first open-source conference kicks off, with Tizen on its mind

The inaugural Samsung Open-Source Conference opens Tuesday morning in Seoul, with keynotes from well-known figures in the open source world and a hackathon focused on Tizen, the company’s in-house mobile operating system. The event kicks off with a speech from Jono Bacon, the former community manager for Ubuntu, who recently moved to the XPrize Foundation, and also includes talks from Linux kernel developer Tejun Heo and Carsten Heitzler, the principal creator of the Enlightenment desktop environment for Linux. Read more Also: Samsung Electronics to host first open-source conference

Flockport Rivals Docker with Open Source Container Virtualization

Is there more to container-based open source virtualization than Docker? A startup named Flockport thinks so, and has launched a website for sharing and deploying virtual apps using Linux Containers (LXC), an alternative to Docker. Read more

OpenDaylight executive director spells out where this open source SDN efforts stand

So if I compare it to Linux. Linux is in my computer, in my car, it’s in a million things outside of the server room. In the same way I think a large percentage of OpenDaylight will be used and leveraged that way. You will have a few people who grab the code, compile it themselves and deploy it in their environment, but mostly for a proof of concept (POC). If an end user hears about SDN and thinks it’s great, they might find themselves needing to POC 15 different solutions. Do I need an overlay? Well, you’ve got to look at three or four overlays out there because they all do things differently. And if you want to figure out how to use OpenFlow, well there are different flavors of OpenFlow, so you’re going to pull a couple of different ones. Read more