Language Selection

English French German Italian Portuguese Spanish

Best lightweight Linux distro of 2019

Filed under
GNU
Linux

Modern Linux distros are designed to appeal to a large number of users who run modern hardware.

As a result, they have become too bloated for older machines, even if you manually delete files. Without a healthy dollop of system memory and an extra core or two, these distros may not deliver the best performance.

Thankfully, there are many lightweight distros, trimmed and tweaked by expert hands, which can be used to breathe new life into older hardware.

But there's one caveat to bear in mind when working with lightweight distros – they usually manage to support ancient kit by cutting away just about everything you take for granted, such as wizards and scripts which make everyday tasks easier.

That said, these lightweight distros are fully capable of reviving older hardware and can even function as a replacement of your current operating system, if you're willing to adjust to their way of working and install extra programs as necessary.

Read more

More in Tux Machines

today's howtos

KDE Frameworks 5.61, Applications 19.08 in FreeBSD

Recent releases were KDE Frameworks 5.61 and KDE Applications 19.08. These have both landed in the official FreeBSD ports tree, after Tobias did most of the work and I pushed the big red button. Your FreeBSD machine will need to be following current ports – not the quarterly release branches, since we don’t backport to those. All the modern bits have arrived, maintaining the KDE-FreeBSD team’s commitment to up-to-date software for the FreeBSD desktop. The one thing we’re currently lagging on is Qt 5.13. There’s a FreeBSD problem report tracking that update. Read more

Dev branch moving towards Qt 6

As you know, Qt 5.14 will be branched pretty soon. After that I would expect that most new development work would start to be aimed towards Qt 6. As it looks right now, 5.15 will be a smaller release where we polish what we have in 5.14, and prepare some things for Qt 6. To reflect that and help us all understand that the development focus is now towards Qt 6, I would like to propose that dev becomes the Qt 6 branch after we branched away 5.14 (and we merge wip/qt6 back into dev). We can then either create a 5.15 branch at the same time, or slightly later, once 5.14 has stabilised a bit more (e.g. after the beta or RC). Read more Also: Qt's Development Branch To Begin Forming Qt 6

Today in Techrights