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

Security Leftovers

  • Security updates for Monday
  • Recursive DNS Server Fingerprint Problem

    Our goal is to identify hijacked resolvers by analyzing their fingerprints, in order to increase safety of Internet users. To do that, we utilize data collected via RIPE Atlas (atlas.ripe.net).

  • Online developer tutorials are spreading XSS and SQL injection flaws

    The researchers, from across three universities in Germany and Trend Micro, checked the PHP code bases of more than 64,000 projects on Github and uncovered more than 100 vulnerabilities that they believe might have been introduced as a result of developers picking up the code that they used from online tutorials.

  • BrickerBot, the permanent denial-of-service botnet, is back with a vengeance

    BrickerBot, the botnet that permanently incapacitates poorly secured Internet of Things devices before they can be conscripted into Internet-crippling denial-of-service armies, is back with a new squadron of foot soldiers armed with a meaner arsenal of weapons.

  • Reproducible Builds: week 104 in Stretch cycle
  • Webroot antivirus goes bananas, starts trashing Windows system files
    Webroot's security tools went berserk today, mislabeling key Microsoft Windows system files as malicious and temporarily removing them – knackering PCs in the process. Not only were people's individual copies of the antivirus suite going haywire, but also business editions and installations run by managed service providers (MSPs), meaning companies and organizations relying on the software were hit by the cockup. Between 1200 and 1500 MST (1800 and 2100 UTC) today, Webroot's gear labeled Windows operating system data as W32.Trojan.Gen – generic-Trojan-infected files, in other words – and moved them into quarantine, rendering affected computers unstable. Files digitally signed by Microsoft were whisked away – but, luckily, not all of them, leaving enough of the OS behind to reboot and restore the quarantined resources.
  • How The Update Framework Improves Security of Software Updates
    Updating software is one of the most important ways to keep users and organizations secure. But how can software be updated securely? That's the challenge that The Update Framework (TUF) aims to solve. Justin Cappos, assistant professor at New York University, detailed how TUF works and what's coming to further improve the secure updating approach in a session at last week's DockerCon 17 conference in Austin, Texas. Simply using HTTPS and Transport Layer Security (TLS) to secure a download isn't enough as there have been many publicly reported instances of software repositories that have been tampered with, Cappos said.
  • Security Updates for Ubuntu Phone to End in June
    Security updates for Ubuntu phone and tablet will end this June, Canonical has confirmed. Current OTA updates are currently limited to critical fixes and security updates — a decision we were first to tell you back in January. But after June 2017 Canonical “will no longer deliver any further updates”.
  • Canonical to stop supporting Ubuntu Phone in June
    Canonical had already announced development of its Ubuntu Phone software was ending. Now we know when the final nail goes in the coffin: June.
  • Malware Hunts And Kills Poorly Secured Internet Of Things Devices Before They Can Be Integrated Into Botnets
    Researchers say they've discovered a new wave of malware with one purpose: to disable poorly secured routers and internet of things devices before they can be compromised and integrated into botnets. We've often noted how internet-of-broken-things devices ("smart" doorbells, fridges, video cameras, etc.) have such flimsy security that they're often hacked and integrated into botnets in just a matter of seconds after being connected to the internet. These devices are then quickly integrated into botnets that have been responsible for some of the worst DDoS attacks we've ever seen (including last October's attack on DYN).

GNOME/GTK News

  • The Way GNOME Handles Wallpapers Really Annoys Me
    I love GNOME Shell — and no, not just because I’ve little choice now that is Ubuntu’s default desktop! But the more I use GNOME the more I learn that the desktop environment, like every other, has its own share of quirks, bugs and inconsistencies. Like the following appreciably niche niggle in the the way GNOME handles desktop wallpapers.
  • Drag-and-drop in lists
    I’ve recently had an occasion to implement reordering of a GtkListBox via drag-and-drop (DND). It was not that complicated. Since I haven’t seen drag-and-drop used much with list boxes, here is a quick summary of what is needed to get the basics working.

Containers News

  • How Kubernetes is making contributing easy
    As the program manager of the Kubernetes community at Google, Sarah Novotny has years of experience in open source communities including MySQL and NGINX. Sarah sat down with me at CloudNativeCon in Berlin at the end of March to discuss both the Kubernetes community and open source communities more broadly. Among the topics we covered in the podcast were the challenges inherent in shifting from a company-led project to a community-led one, principles that can lead to more successful communities, and how to structure decision-making.
  • How Microsoft helped Docker with LinuxKit and Moby Project [Ed: Microsoft 'helped'... embrace, extend, coerce; haven't Docker employees learned from history?]
    Today, supporting Linux is as critical to Microsoft as it is to Red Hat and SUSE.
  • How to make branding decisions in an open community
    On April 18, Docker founder Solomon Hykes made a big announcement via a pull request in the main Docker repo: "Docker is transitioning all of its open source collaborations to the Moby project going forward." The docker/docker repo now redirects to moby/moby, and Solomon's pull request updates the README and logo for the project to match. Reaction from the Docker community has been overwhelmingly negative. As of this writing, the Moby pull request has garnered 7 upvotes and 110 downvotes on GitHub. The Docker community is understandably frustrated by this opaque announcement of a fait accompli, an important decision that a hidden inner circle made behind closed doors. It's a textbook case of "Why wasn't I consulted?"

Ubuntu 17.04: Unity's swan song?

For the most part, not much has changed on Ubuntu's Desktop edition in the past year. Unity 7 has more or less remained the same while work was progressing on the next version of the desktop, Unity 8. However, now that both desktops are being retired in favour of the GNOME desktop, running Ubuntu 17.04 feels a bit strange. This week I was running software that has probably reached the end of its life and this version of Ubuntu will only be supported for nine months. I could probably get the same desktop experience and most of the same hardware support running Ubuntu 16.04 and get security updates through to 2021 in the bargain. In short, I don't think Ubuntu 17.04 offers users anything significant over last year's 16.04 LTS release and it will be retired sooner. That being said, I could not help but be a little wistful about using Unity 7 again. Even though it has been about a year since I last used Unity, I quickly fell back into the routine and I was once more reminded how pleasant it can be to use Unity. The desktop is geared almost perfectly to my workflow and the controls are set up in a way that reduces my mouse usage to almost nothing. I find Unity a very comfortable desktop to use, especially when application menus have been moved from the top panel to inside their own windows. While there are some projects trying to carry on development of Unity, this release of Ubuntu feels like Unity's swan song and I have greatly enjoyed using the desktop this week. While there is not much new in Ubuntu 17.04, the release is pretty solid. Apart from the confusion that may arise from having three different package managers, I found Ubuntu to be capable, fairly newcomer friendly and stable. Everything worked well for me, at least on physical hardware. Unity is a bit slow to use in a virtual machine, but the distribution worked smoothly on my desktop computer. Read more