Here is what I did to install KaOSx Linux in VirtualBox. KaOS is a an rolling distribution, fully focused on KDE/Qt. It uses pacman as package-manager and is based on Arch Linux. KaOS uses pacman as package-manager for this rolling distribution, It was decided it waas the best fit for package management. Does using pacman mean a distribution is based on Arch? What about the other tools and packages used from a variety of distributions? First thing you see when booting a KaOS ISO is gfxboot, a tool from OpenSuse. Other important packages used from OpenSuse are hwinfo and imagewriter, does this make KaOS based on OpenSuse? Or the hardware database, a package from the Gentoo developers, systemd came originally from Fedora. As KaOS sees it, try to find the best available tools for this distribution and keep evaluating what comes available, and the best for this distribution will come forward.
When stating a distribution is based on another, that means in 99% of the cases, that distribution uses the repositories of the distribution it is based on (mostly 90% plus is from upstream then, added with some repositories for specific settings). KaOS does not use any upstream repositories, every package in every repository is build from scratch by and for KaOS.
To quote the website: "The idea behind KaOS is to create a tightly integrated rolling and transparent distribution for the modern desktop, build from scratch with a very specific focus. Focus on one DE (KDE), one toolkit (Qt), one architecture (x86_64) plus a focus on evaluating and selecting the most suitable tools and applications. Moving away from proprietary Operating Systems to open source options (Linux-based, BSD based, Solaris based) is about wanting freedom and choice in almost all cases. KaOS has made the choice to use the Linux kernel as a base (though the Illumos kernel is under constant evaluation, and a future switch is a wish). After that choice, the best available package manager, most flexible way of package building, repository maintenance is pacman/makepkg for a rolling distro like KaOS. As for the Desktop Environment, there will never be a change, whether it is Linux or Illumos based, KDE will be the choice, Qt the Toolkit. With those choices in place, April 2013 package building for this independent distribution was started. KaOS is a build from scratch distribution, every package in every repository is build by and for KaOS. By July 2013 the initial goal of about 1500 packages was reached."
Hardware requirements?
KDE is a modern Desktop Environment which can make use of most of any graphics or sound card capabilities. This does not mean KDE can’t be made to run on very low-end hardware, but in general there are better options available for such systems (OpenBox for example). The very minimal needed for hard-drive space is 8 Gb, but 25 Gb is recommended as minimal. KaOS will install with 1 Gb of RAM available, though a much better experience will start with 2 Gb of RAM. Since only x86_64 packages are available, a 64 bit capable cpu is needed.
I added 2 Gigs to the VM, and enabled 3D acceleration and PAE/NX.
Boot up menu.Start KaOS Live with or without nVidia Drivers, Boot from first hard disk, preform and hardware detection or memory test. F1 is Help, F2 sets the default laungage, F3 sets the video mode, and F4 allows you to adjust the kernel paramiters at boot.
Booting the kernel, no errors.
First Installation screen. Welcome!
Select your time zone.
Configure your keyboard.
Default desktop with a few widgets added, clock, battery status, a K-menu, USB mounter, Media player, and a desktop lock.
