Language Selection

English French German Italian Portuguese Spanish

Kororaa - Revisited

Filed under
Linux
Reviews
-s

Almost a month ago I attempted an install of Gentoo using Kororaa and it didn't quite go as hoped. About a week ago Chris, of Kororaa, writes to mention that he released Beta2-r1. He stated that he was finally able to find a machine that would reproduce my error and thought he had fixed it. He asked if I could test it, and I apologize for the delay, but today I finally did. What happened this time?

Success! Yes! It went like clockwork and I am so pleased. If you read the former article mentioned above, you will get a rough rundown of the installation process. Only this time instead of the package installation prematurely exiting, we had a successfull install of 390 packages out of 390.

Upon boot we are presented with a similar setup screen as described previously, save for the prelink step. I've played around with prelink myself several times and have had mixed results. I'm not a true believer in prelinking anyway, so I didn't miss that step. The other steps went very well. Most hardware was automagically detected and setup, or setup during this step. Configuration files were written for most of the tedious tasks and a bootable gui resulted.

I'm just tickled pink. I finally have a nice fresh gentoo install, and all without the pains of reading the exhaustive documentation contained in the gentoo handbook. Not that I'm advocating skipping the documentation, it's just that I've been thru it about a 1/2 dozen times now and though not all of the install has been put to memory, most of the post-install configurations have. So, if you have never installed Gentoo before and even if you choose Kororaa as your install method, please read through the documentation for proper setup of your system.

As stated Kororaa sets up quite a bit of the little config files needed to get into your system. During the install phase you are asked for your root password and user setup. After boot the systemconfig sets up your sound, network and asks your resolution, but no xorg.conf file was written. I should have tried to see if X would start, but without a proper config file, I assumed it wouldn't. So, I took the route of /usr/X11R6/bin/xorgconfig to get a basic config written. Then I tested using the vesa drivers. Afterwhich I exited X and installed the nVidia drivers. From there I edited a few things in xorg.conf, modprobe nvidia, and was able to start x into KDE using nvidia graphic drivers. After reboot kdm started for a graphical login.

KDE is version 3.5 and it is wonderfully stable. It even includes support for xinerama. I first began desiring a fresh Gentoo install due to the ever-growing size of my current install. I deleted the usual recommended directories and uninstalled this and that, however, I still could not get it below 6.5 gigs. Then lately, I have to admit, things have become a little unstable. I had poked and prodded, installed and uninstalled, deleted this directory and that file, tweaked and config'd, updated and patched kernels, installed some things from source and other's from ebuilds, all under almost borderline insane c & ldflags and unstable arch, ...to the point that I had a mess. I was beginning to suffer crashes. I had begun to blame hardware, cuz I sure couldn't blame my beloved Gentoo or (heaven forbid) myself! Big Grin


Kororaa comes with some great compromises (good general all around default config for a majority of users I mean) in its make.conf. It is compiled using march=pentium3 and chost i686-pc-linux-gnu. It has as its default cflags "-pipe -O3 -fweb -frename-registers -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer" and ldflags of " -Wl,-O2 -Wl,--enable-new-dtags -Wl,--sort-common -s." This is all using the arch of x86 (which means stable). I might be changing my march to athlon-xp, but I'll probably leave the rest. I'll think I'll stay in the stable branch from now on, or at least for now. I might need to add to the USE flags as well, but basically I'm satisfied with this setup.


Kororaa comes with a Linux-2.6.14 kernel unamed 2.6.14-kororaa-r6. It utilized gcc 3.4.4 and Xorg 6.8.2. It also comes with mozilla-firebird/thunderbird 1.0.7, openoffice 2.0.0, and gimp 2.2.8-r1. Besides KDE, the default install includes fluxbox-0.9.14-r1 as well. Once you sync up you can install anything from portage just as any other Gentoo install. In fact if you change the USE flags very much in your /etc/make.conf, you should emerge --newuse world before adding to the default packages. If you change the march or other cflags, perhaps you should emerge -e world. Don't change the chost. (Consult the documentation for definitive answers/advice in this area please.)


As you can see from the following screenshot, Kororaa comes to you fairly up-to-date. There are but a handful of apps that have been updated since Kororaa has been released.


Well, sorry to cut this short, but I do have a new system to tweak and make pretty. Big Grin Kororaa is a wonderful shortcut and I am very pleased with the results. Good job Chris and thanks for everything. Woohoooo!...

Kororaa Home Page.
Download Page.
Forums.
Documentation Handbook.



Linux Training UK.

xorg.conf issue

I think was due to lspci not being in the right place. This is easily fixed and a howto is on the forums.

I'd like to know for sure though, cause on all my tests xorg.conf was created just fine Thinking

-c

Comment viewing options

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

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.