Language Selection

English French German Italian Portuguese Spanish

KDE netbook desktop: My guide to configuring and using it

Filed under
KDE

It is important to note that the KDE netbook desktop is included in every KDE 4 installation — but it is not the default, so you have to activate it if you want it. It works brilliantly on every netbook I have tested, with complete support out of the box for all the hardware including Intel Atom, AMD C-50, C-60, E-350 and E-450 CPUs, Intel and AMD/ATI graphics, Intel, Broadcom, Atheros and Ralink network and Wi-Fi adapters, and as little as 1GB to as much as 4GB of memory.

Although I have chosen openSuSE 12.1 for the screenshots here, I could have done the same thing on Mint 13 KDE, Mageia, or any other current KDE 4 distribution.

rest here




More in Tux Machines

KDevelop 5.0.0 release

Almost two years after the release of KDevelop 4.7, we are happy to announce the immediate availability of KDevelop 5.0. KDevelop is an integrated development environment focusing on support of the C++, Python, PHP and JavaScript/QML programming languages. Many important changes and refactorings were done for version 5.0, ensuring that KDevelop remains maintainable and easy to extend and improve over the next years. Highlights include much improved new C/C++ language support, as well as polishing for Python, PHP and QML/JS. Read more

CoreOS 1068.10.0 Released with Many systemd Fixes, Still Using Linux Kernel 4.6

Today, August 23, 2016, the development team behind the CoreOS security-oriented GNU/Linux operating system have released the CoreOS 1068.10.0 stable update, along with new ISO images for all supported platforms. Read more

SUSE Linux and openSUSE Leap to Offer Better Support for ARM Systems Using EFI

The YaST development team at openSUSE and SUSE is reporting on the latest improvements that should be available in the upcoming openSUSE Leap 42.2 and SUSE Linux Enterprise 12 Service Pack 2 operating systems. Read more

Create modular server-side Java apps direct from mvn modules with diet4j instead of an app server

In the latest release, the diet4j module framework for Java has learned to run modular Java apps using the Apache jsvc daemon (best known from running Tomcat on many Linux distros). If org.example.mydaemon is your top Maven project, all you do is specify it as the root module for your jsvc invocation, and diet4j figures out the dependencies when jsvc starts. An example systemd.service file is available.