Language Selection

English French German Italian Portuguese Spanish

Fresh Gentoo Install

Filed under
Gentoo

Recently I decided that it was time I picked up some flavor of Linux and give it a try. I’ve installed Gentoo in the past, with some difficulty, but never stuck with it for long. I finally got tired of it and put Windows back on the unit. I have since felt that Linux should be part of my knowledge-base, especially with the work-field I’m going into.

The second time around with Gentoo wasn’t as bad as the first. I had very few problems, and had to ask for help only a handful of times. I mainly went along with the Handbook, and the recommended install, as I’m still uncomfortable with Linux. I might go back and do a custom install at a later date when I learn more, but for now the recommended install fit my needs. I was careful this time to pay close attention to everything I did in the install, including the commands used. I’m more of a learn by doing person, so this would be my one chance to really learn a lot of the commands used.

All in all the basic install of Gentoo took me about a good 38 hours. Once the install was finished, it was time to do some emerging.

More Here




Also:

I recently saw the announcement of the ‘fork’ of Gentoo, Exherbo. Its not really a fork, because there isn’t any shared stuff. The package manager used is Paludis, one of the alternatives to Portage in Gentoo. Several of the developers on Exherbo are from Gentoo, and they profess similar goals. I’m a bit wary, though, because their webpage is pretty dickish. Thats fine, Gentoo never claimed to be a everyman’s distro, but I kind of wish they’d waited to announce their project until after they wanted people to start using it.

I shouldn’t be surprised, though, since Gentoo dev and author of Paludis, Ciaran McCreesh, is one of the Exherbo devs. I once tried to use Paludis about a year ago, when portage was in one of its broken states ( one of the reasons I’m moving on, more on that later…) I read the install page for Paludis, got it installed, but couldn’t get it working. I fiddled with it for awhile, read some conflicting documentation on the Paludis website, and finally hopped on the IRC channel to ask for help. I was informed that the documentation was out of date, and when I asked what I needed to do, showing them my error messages and everything, I was told by Mr. McCreesh to just wait a few weeks. That’s a crazy way to treat your users and potential contributors. Maybe I’m just used to the Ruby community, where everyone is helpful and supportive.

Moving on from Gentoo…

And: Gentoo Software that never made it Sad

More in Tux Machines

Security Leftovers

10 hot Android smartphones that got price cuts recently

With numerous smartphone getting launched each month, brands always adjust prices to give slightly competitive edge to older smartphone models and also to clear inventories. Here are 10 smartphones that got price cuts recently. Read more

Debian and Ubuntu News

  • Debian Project News - July 29th, 2016
    Welcome to this year's third issue of DPN, the newsletter for the Debian community.
  • SteamOS Brewmaster 2.87 Released With NVIDIA Pascal Support
  • Snap interfaces for sandboxed applications
    Last week, we took a look at the initial release of the "portal" framework developed for Flatpak, the application-packaging format currently being developed in GNOME. For comparison, we will also explore the corresponding resource-control framework available in the Snap format developed in Ubuntu. The two packaging projects have broadly similar end goals, as many have observed, but they tend to vary quite a bit in the implementation details. Naturally, those differences are of particular importance to the intended audience: application developers. There is some common ground between the projects. Both use some combination of techniques (namespaces, control groups, seccomp filters, etc.) to restrict what a packaged application can do. Moreover, both implement a "deny by default" sandbox, then provide a supplemental means for applications to access certain useful system resources on a restricted or mediated basis. As we will see, there is also some overlap in what interfaces are offered, although the implementations differ. Snap has been available since 2014, so its sandboxing and resource-control implementations have already seen real-world usage. That said, the design of Snap originated in the Ubuntu Touch project aimed at smartphones, so some of its assumptions are undergoing revision as Snap comes to desktop systems. In the Snap framework, the interfaces that are defined to provide access to system resources are called, simply, "interfaces." As we will see, they cover similar territory to the recently unveiled "portals" for Flatpak, but there are some key distinctions. Two classes of Snap interfaces are defined: one for the standard resources expected to be of use to end-user applications, and one designed for use by system utilities. Snap packages using the standard interfaces can be installed with the snap command-line tool (which is the equivalent of apt for .deb packages). Packages using the advanced interfaces require a separate management tool.
  • Ubuntu 15.10 (Wily Werewolf) Reaches End Of Life Today (July 28)
  • Ubuntu MATE 16.10 Yakkety Yak Gets A Unity HUD-Like Searchable Menu
    MATE HUD, a Unity HUD-like tool that allows searching through an application's menu, was recently uploaded to the official Yakkety Yak repositories, and is available (but not enabled) by default in Ubuntu MATE 16.10.

Tablet review: BQ Aquaris M10 Ubuntu Edition

As employees have become more and more flexible in recent years thanks to the power and performance of mobile devices, the way we work has changed dramatically. We frequently chop and change between smartphones, tablets and laptops for different tasks, which has led to the growth of the hybrid market – devices such as Microsoft’s Surface Pro 3 and Apple’s iPad Pro – that provide the power and functionality of a laptop with the mobility and convenience of a tablet. Read more