Language Selection

English French German Italian Portuguese Spanish

grrrrrr-rr4

Filed under
Gentoo
Reviews
-s

In my continuing search to find a binary gentoo installer, one that will install a complete working system in much the same manner as SuSE, Mdv, or PCLOS from a graphical environment that I can then rebuild for my arch/system/requirements at my leisure, I tried RR4-2.65.1 this morning. RR4 is a livedvd "designed to transform a computer into a powerful Gentoo Linux system in less than 5 minutes," according to description provided to DistroWatch.

I've been a loyal gentoo user for little over two years now and have installed per stage 1 about 4 or 5 times. My server on which this site is run is one example. But I've been looking for a graphical environment from which to install gentoo, a way to encourage others to install gentoo without having to read pages and pages of documentation. I've tried several distros/methods lately, and none have yet to equal the functionality I found in Litrix.

The system starts out really impressive. I booted the livedvd and was given the option of just hitting enter or perusing several booting options. Then the silent boot features a lovely splash that utilizes a kde-like progress of highlighting icons rather than a progress bar and all accented by the lovely gentoo purple color scheme. The verbose boot looks just like my everyday gentoo system booting - a variation on the regular linux boot you've all probably seen many many times. A beautiful desktop greets you and lulls you into a sense of confidence. The desktop appears so polished and refined. The menus are chocked full of useful applications and tools. The fonts are great looking and performance is amazing (considering it appears built for i386). It features a 2.6.14-r2 kernel and uses a 6.99 of Xorg. The crowning jewel is the installer. It's the whole point.

        


Yes, it's a mighty fine livedvd and if that's your desire, then they have you covered. I don't recall when I've seen such full menus. But at 2.4 gigs, the iso should be complete. It contains not only KDE 3.4, but also gnome and some other lighter window environments.

However, ...you knew there was going to be a "however" didn't you, however, the installer bombs out here. It's a beautiful piece of software. It features a lovely windec and exquisite widgets. The fonts are gorgeous. Options seem insightful and complete. I was quite impressed. Too bad it don't work.

The installer begins with a graphical configuration which walks one through all the options. Partitioning if needed, naming / partition, networking, type of install, use flags and chost options, root passwd and useradd are just some of the steps. Among the choices for type of system are the standard stage 1, stage 2, stage 3 and install the livedvd. If you chose any of the stages you can choose your USE flags, arch and chost. It defaults to stage 3, but I chose install the livedvd my first attempt, figuring this would be the fastest and easiest. After configuration and clicking "install," the installer outputs root password is setup, then stops. I waited quite a while before checking with top to make sure it wasn't doing anything. I waited some more to make sure even though the hard drive light was still not blinking. Eventually I decided "welp, I guess that didn't work."

        


My second attempt was to use its default of stage 3. I restarted the installer and chose that and proceded to spend about an hour choosing my USE flags, chost and arch. When I clicked on athlon-xp the X server crashed and sent me back to the login. That's when I said, "pffffttt, I ain't trying no more!"

I visited the forum before my first attempt for help in deciding which type of install to use. No real information was found on that topic, but I did see some reports of successful installs, mostly using the "almost gentoo method," and even some posts about destroyed partition tables. No damage was inflicted here, but no system resulted either.

Second thought, I wasn't quite ready to give up yet as it turned out. Upon typing the text for this article, I became aware that I really hate having to state that a distro doesn't work, but I must obey my journalist integrity. So, I decided to give RR4 one more chance. I went through the whole shebang again, spending not quite the same amount of time considering the USE flags. It still just stopped at setting the passwords. I was bummed.

        


So, in the end I'm left to state that the RR4 gentoo-installer is still non-functional. It states clearly on their homepage that rr4 is still alpha so one can't really complain too much. It is impressive at this point and one to keep an eye on. If anyone has a "it works for me" story, I encourage you to please share your comments or, even better, your own blogged review.

So, my quest continues...

More in Tux Machines

Docker 1.13, Containers, and DevOps

  • Introducing Docker 1.13
    Today we’re releasing Docker 1.13 with lots of new features, improvements and fixes to help Docker users with New Year’s resolutions to build more and better container apps. Docker 1.13 builds on and improves Docker swarm mode introduced in Docker 1.12 and has lots of other fixes. Read on for Docker 1.13 highlights.
  • Docker 1.13 Officially Released, Docker for AWS and Azure Ready for Production
    Docker announced today the general availability of Docker 1.13, the third major update of the open-source application container engine for GNU/Linux, macOS, and Microsoft Windows operating systems. Docker 1.13 has been in development for the past couple of months, during which it received no less than seven RC (Release Candidate) versions that implemented numerous improvements for the new Swarm Mode introduced in Docker 1.12, a few security features, as well as a new Remote API (version 1.25) and Client.
  • Distributed Fabric: A New Architecture for Container-Based Applications
    There’s a palpable sense of excitement in the application development world around container technology. Containers bring a new level of agility and speed to app development, giving developers the ability to break large monolithic apps into small, manageable microservices that can talk to one another, be more easily tested and deployed, and operate more efficiently as a full application. However, containers also demand a new architecture for the application services managing these microservices and apps, particularly in regards to service discovery — locating and consuming the services of those microservices.
  • DevOps trends emerging for 2017 and beyond
    Finally, one of the biggest trends for 2017 will not be just a focus on engaging and implementing some of these DevOps best practices into your enterprise, but a sweeping adoption of the DevOps/agile culture. This is because one of the most important – if not the absolute most key –tenets to a successful DevOps organization is culture. The enterprises that most espouse the shared responsibility, the empowered autonomous teams, the can-do attitudes, and the continuous learning environment in which DevOps thrives will see the biggest benefits.

Kernel Space/Linux

  • Optimizing Linux for Slow Computers
    It’s interesting, to consider what constitutes a power user of an operating system. For most people in the wider world a power user is someone who knows their way around Windows and Microsoft Office a lot, and can help them get their print jobs to come out right. For those of us in our community, and in particular Linux users though it’s a more difficult thing to nail down. If you’re a LibreOffice power user like your Windows counterpart, you’ve only really scratched the surface. Even if you’ve made your Raspberry Pi do all sorts of tricks in Python from the command line, or spent a career shepherding websites onto virtual Linux machines loaded with Apache and MySQL, are you then a power user compared to the person who knows their way around the system at the lower level and has an understanding of the kernel? Probably not. It’s like climbing a mountain with false summits, there are so many layers to power usership. So while some of you readers will be au fait with your OS at its very lowest level, most of us will be somewhere intermediate. We’ll know our way around our OS in terms of the things we do with it, and while those things might be quite advanced we’ll rely on our distribution packager to take care of the vast majority of the hard work.
  • Long-Term Maintenance, or How to (Mis-)Manage Embedded Systems for 10+ Years
    In this presentation, kernel hacker Jan Lübbe will explain why apparently reasonable approaches to long-term maintenance fail and how to establish a sustainable workflow instead.
  • Linux 4.9 Is the Next Long-Term Supported Kernel Branch, Says Greg Kroah-Hartman
    Linux kernel maintainer Greg Kroah-Hartman confirmed today, January 19, 2017, in a short message, on his Google+ page, that the Linux 4.9 branch is now marked as "longterm," or as some of you know as LTS (Long-Term Support). The story behind Linux kernel 4.9 becoming the next long-term supported series dates from way before it's launch last month, on December 11, when Linus Torvalds officially announced the new branch. It all started back on August 12, 2016, when Greg Kroah-Hartman dropped a quick Google+ post to say "4.9 == next LTS kernel."
  • Maintainers Don't Scale
    First let’s look at how the kernel community works, and how a change gets merged into Linus Torvalds’ repository. Changes are submitted as patches to mailing list, then get some review and eventually get applied by a maintainer to that maintainer’s git tree. Each maintainer then sends pull request, often directly to Linus. With a few big subsystems (networking, graphics and ARM-SoC are the major ones) there’s a second or third level of sub-maintainers in. 80% of the patches get merged this way, only 20% are committed by a maintainer directly. Most maintainers are just that, a single person, and often responsible for a bunch of different areas in the kernel with corresponding different git branches and repositories. To my knowledge there are only three subsystems that have embraced group maintainership models of different kinds: TIP (x86 and core kernel), ARM-SoC and the graphics subsystem (DRM).

Graphics in Linux

  • RADV Vulkan Driver Has Geometry Shader Support For Testing
    David Airlie has published a set of 31 patches for testing that provide initial support for geometry shaders within the RADV Radeon Vulkan driver. While RadeonSI has long supported geometry shaders, it's been a bigger work item bringing it to this open-source Radeon Vulkan driver within Mesa. The patches are enough for Vulkan geometry shaders to get working on RADV, but Airlie explains that the support isn't gold: "This is a first pass at geometry shader support on radv, all the code should be here in reviewable pieces, it seems to mostly pass CTS tests but triggers some llvm 3.9 bugs around kill, and there might still be a GPU hang in here, but this should still be a good place to start reviewing."
  • libinput 1.6.0
    This release fixes the slow touchpad acceleration on touchpads with less than 1000dpi, a missing call to normalized the deltas was the source of the issue.
  • Libinput 1.6 Released With New Touchpad Acceleration
    Libinput 1.6.0 was announced a short time ago on wayland-devel.
  • Mesa 17 Gets a First Release Candidate, Final Planned for Early February 2017
    Collabora's Emil Velikov announced today, January 19, 2017, the availability of the first of many Release Candidate (RC) development versions of the upcoming and highly anticipated Mesa 17.0.0 3D Graphics Library. Mesa 17 is shaping up to be a huge milestone that should dramatically improve the performance of the bundled open-source graphics drivers for Intel, AMD Radeon, Nvidia graphics cards on a Linux-based operating system. Just the other day it enabled OpenGL 4.5 support for Intel Haswell GPUs, which is already a big achievement.

Android Leftovers

  • Donald Trump has surrendered his Android phone
    Donald Trump has given up his beloved Android phone ahead of today’s inauguration, the Associated Press reports, though it is unclear what type of device he will use in the White House. According to The New York Times, Trump is now using a more secure, encrypted handset that was approved by the Secret Service. He also has a different phone number, the Times reports, citing people close to the president-elect. Trump doesn’t use email, but he does use his Android phone to tweet. He’s also been very accessible throughout the presidential campaign and transition, taking calls from reporters, politicians, and world leaders. Malcolm Turnbull, the prime minister of Australia, called Trump to congratulate him on his electoral victory after getting his cellphone number from professional golfer Greg Norman.
  • Best affordable Android smartphones you can buy [January 2017]
    There are new smartphones hitting the market constantly, but which is the best to pick up when you’re trying to save a buck or two? We’ve seen some great launches this summer and we’re only expecting more over the coming months, but for now, let’s go over the best affordable Android smartphones you can go pick up today…
  • A list of every Samsung phone getting Android 7.0 Nougat this year
  • WatchMaker to support Gear S2 & Gear S3, 1000s of watchfaces incoming
    WatchMaker, a popular Android and Android Wear watchface platform, has some good news for our readers. They are currently in the process of expanding their supported platforms and will be targeting Tizen and its latest wearable smartwatches, the Samsung Gear S2 and Gear S3.