Language Selection

English French German Italian Portuguese Spanish

Slack

Calculate Linux Desktop 17 Cinnamon released

Filed under
GNU
Linux
Slack

Meet the new Calculate Linux Desktop with Cinnamon flavour!

Calculate Linux Desktop Cinnamon (CLDC) features a collection of Gnome 3 applications combined with the classic CL design and the OpenRC init system.

Read more

liveslak 1.1.6 released

Filed under
Slack

It has been a while since I released the last ‘liveslak‘. Usually these releases seem to co-incide with Plasma5 releases in my ‘ktown’ repository.
Today is no different, and liveslak 1.1.6 has been released to produce a new set of Live ISO images.

You will find the usual versions of Slackware Live Edition based on liveslak 1.1.6 and using Slackware-current dated “Thu Jan 26 21:33:41 UTC 2017“. There are variants for a full Slackware (in 64bit and 32bit), Plasma5, MATE and Dlackware (a newcomer). Also the 700MB small XFCE variant (in 32bit and 64bit).

Read more

Absolute Linux Caters to the Slackware Crowd

Filed under
Reviews
Slack

Absolute Linux is a distro that raises the question: Is it really worth the bother?

Any version of this Slackware-based Linux OS is just that -- a really big bother -- unless you love Unix-like systems that give you total control. It likely would be especially bothersome for less experienced users and for folks comfortable with Debian distros such as Ubuntu, Linux Mint and such.

Some Slackware-based distros are easier than others to use -- but the text-based installation and mostly manual operating routine makes using Absolute Linux a challenge. Once you get beyond the configuration steps, you still face a considerable learning curve to keep it running smoothly.

Clearly, I am not overly impressed with the Absolute flavor of Slackware Linux. I see it as the equivalent of driving a stick shift automobile with a crank-to-start mechanism instead of an automatic model with keyless ignition. That said, once you have the engine purring, it drives fast and furious along the highway.

I like to offer unique computing options in these weekly Linux Picks and Pans reviews, so I set my comfort zone aside and rolled up my sleeves to get my hands a little scraped reaching under Absolute Linux's hood.

Read more

Slackware-Based Porteus 3.2.2 Portable Distro Released with Linux Kernel 4.9

Filed under
Slack

Today, December 29, 2016, the development team behind the Porteus (formerly Slax Remix) Linux-based operating system series proudly announced the final release of Porteus 3.2.2.

Read more

Linux Kernel 4.9 Now Unofficially Available for Slackware 14.2 and Derivatives

Filed under
Linux
Slack

After announcing the availability of a remix of Raspberry Pi Foundation's Raspbian PIXEL Linux OS that features Refracta Tools, GNU/Linux developer Arne Exton informed us about the availability of a custom Linux 4.9 kernel build for Slackware 14.2, Zenwalk, Slax, SlackEX, or other distro based on them.

Read more

Based on Slackware 14.2, Absolute 14.2.2 Linux Is Out with Updated Kernel, X.Org

Filed under
Slack

Paul Sherman, the developer of the Absolute Linux distribution based on Slackware, has announced the availability of the second point release to the stable Absolute 14.2 series.

Read more

Salix Xfce 14.2 Live Edition Released, It's Based on Xfce 4.12 & Slackware 14.2

Filed under
Slack

After two Betas and three RC (Release Candidate) versions, the final release of the Salix Live Xfce 14.2 edition is now available for download, allowing users to take the Slackware-based OS for a test drive before installing it.

Read more

Slackware News

Filed under
Slack
  • More Flash fixes in November
  • Q4 2016 fixes for Java 8 (openjdk)
  • LibreOffice 5.2.3 for Slackware-current

    I wanted the latest LibreOffice in the upcoming Slackware Live Edition 1.1.4 (PLASMA 5 variant) so I have built and uploaded a set of packages for LibreOffice 5.2.3. They are for Slackware-current only.

  • Slackware Live Edition 1.1.4 – based on slackware-current of 4 Nov 2016

    Today I conclude my packaging frenzy with a new release of ‘liveslak‘. Version 1.1.4 is ready with only some minor tweaks. Users of the “iso2usb.sh” script on non-Slackware distros should be happy that the script finds all the required programs now.
    I made a set of ISO images for several variants of the 64bit version of Slackware Live Edition based on liveslak 1.1.4 and using Slackware-current dated “Fri Nov 4 03:31:38 UTC 2016”. These ISO images have been uploaded and are available on the primary server ‘bear‘. You will find ISO images for a full Slackware, Plasma5 and MATE variants and the 700MB small XFCE variant.

First post-8.0 Zenwalk Current

Filed under
Slack

Here's the first post-8.0 "current" ISO. Along with many packages updates from upstream and Zenwalk, you'll get the MPV media player out of the box, some improvements in the setup (new disk partitioning dialog) and the ZenENCFS privacy folder encrypting tool (so that you won't have to put your hardware into the microwave oven any more to remain anonymous).

Read more

Salix Live Xfce 14.2 Beta 2 Released, Supports Booting on 64-bit UEFI Systems

Filed under
Slack

The Salix development team announced the release of the second Beta build of the upcoming Live Edition of the Salix Xfce 14.2 GNU/Linux distribution based on the Slackware 14.2 operating system.

Read more

Syndicate content

More in Tux Machines

Red Hat's "DevOps" Hype Again and Analysis of last Night's Financial Results

OSS Leftovers

  • Deutsche Telekom and Aricent Create Open Source Edge Software Framework
    Deutsche Telekom and Aricent today announced the creation of an Open Source, Low Latency Edge Compute Platform available to operators, to enable them to develop and launch 5G mobile applications and services faster. The cost-effective Edge platform is built for software-defined data centers (SDDC) and is decentralized, to accelerate the deployment of ultra-low latency applications. The joint solution will include a software framework with key capabilities for developers, delivered as a platform-as-a-service (PaaS) and will incorporate cloud-native Multi-access edge computing (MEC) technologies.
  • A Deeper Look at Sigma Prime's Lighthouse: An Open-Source Ethereum 2.0 Client
  • Notable moments in Firefox for Android UA string history
  • Dweb: Creating Decentralized Organizations with Aragon
    With Aragon, developers can create new apps, such as voting mechanisms, that use smart contracts to leverage decentralized governance and allow peers to control resources like funds, membership, and code repos. Aragon is built on Ethereum, which is a blockchain for smart contracts. Smart contracts are software that is executed in a trust-less and transparent way, without having to rely on a third-party server or any single point of failure. Aragon is at the intersection of social, app platform, and blockchain.
  • LLVM 7.0.0 released
  • Parabola GNU/Linux-libre: Boot problems with Linux-libre 4.18 on older CPUs
    Due to a known bug in upstream Linux 4.18, users with older multi-core x86 CPUs (Core 2 Duo and earlier?) may not correctly boot up with linux-libre 4.18 when using the default clocksource.
  • Visual Schematic Diffs in KiCAD Help Find Changes
    In the high(er)-end world of EDA tools like OrCAD and Altium there is a tight integration between the version control system and the design tools, with the VCS is sold as a product to improve the design workflow. But KiCAD doesn’t try to force a version control system on the user so it doesn’t really make sense to bake VCS related tools in directly. You can manage changes in KiCAD projects with git but as [jean-noël] notes reading Git’s textual description of changed X/Y coordinates and paths to library files is much more useful for a computer than for a human. It basically sucks to use. What you really need is a diff tool that can show the user what changed between two versions instead of describe it. And that’s what plotgitsch provides.

LWN's Latest (Today Outside Paywall) Articles About the Kernel, Linux

  • Toward better handling of hardware vulnerabilities
    From the kernel development community's point of view, hardware vulnerabilities are not much different from the software variety: either way, there is a bug that must be fixed in software. But hardware vendors tend to take a different view of things. This divergence has been reflected in the response to vulnerabilities like Meltdown and Spectre which was seen by many as being severely mismanaged. A recent discussion on the Kernel Summit discussion list has shed some more light on how things went wrong, and what the development community would like to see happen when the next hardware vulnerability comes around. The definitive story of the response to Meltdown and Spectre has not yet been written, but a fair amount of information has shown up in bits and pieces. Intel was first notified of the problem in July 2017, but didn't get around to telling anybody in the the Linux community about it until the end of October. When that disclosure happened, Intel did not allow the community to work together to fix it; instead each distributor (or other vendor) was mostly left on its own and not allowed to talk to the others. Only at the end of December, right before the disclosure (and the year-end holidays), were members of the community allowed to talk to each other. The results of this approach were many, and few were good. The developers charged with responding to these problems were isolated and under heavy stress for two months; they still have not been adequately thanked for the effort they put in. Many important stakeholders, including distributions like Debian and the "tier-two" cloud providers, were not informed at all prior to the general disclosure and found themselves scrambling. Different distributors shipped different fixes, many of which had to be massively revised before entry into the mainline kernel. When the dust settled, there was a lot of anger left simmering in its wake.
  • Writing network flow dissectors in BPF
    Network packet headers contain a great deal of information, but the kernel often only needs a subset of that information to be able to perform filtering or associate any given packet with a flow. The piece of code that follows the different layers of packet encapsulation to find the important data is called a flow dissector. In current Linux kernels, the flow dissector is written in C. A patch set has been proposed recently to implement it in BPF with the clear goal of improving security, flexibility, and maybe even performance.
  • Coscheduling: simultaneous scheduling in control groups
    The kernel's CPU scheduler must, as its primary task, determine which process should be executing in each of a system's processors at any given time. Making an optimal decision involves juggling a number of factors, including the priority (and scheduling classes) of the runnable processes, NUMA locality, cache locality, latency minimization, control-group policies, power management, overall fairness, and more. One might think that throwing another variable into the mix — and a complex one at that — would not be something anybody would want to attempt. The recent coscheduling patch set from Jan Schönherr does exactly that, though, by introducing the concept of processes that should be run simultaneously. The core idea behind coscheduling is the marking of one or more control groups as containing processes that should be run together. If one process in a coscheduled group is running on a specific set of CPUs (more on that below), only processes from that group will be allowed to run on those CPUs. This rule holds even to the point of forcing some of the CPUs to go idle if the given control group lacks runnable processes, regardless of whether processes outside the group are runnable. Why might one want to do such a thing? Schönherr lists four motivations for this work, the first of which is virtualization. That may indeed be the primary motivation, given that Schönherr is posting from an Amazon address, and Amazon is rumored to be running a virtualized workload or two. A virtual machine usually contains multiple processes that interact with each other; these machines will run more efficiently (and with lower latencies) if those processes can run simultaneously. Coscheduling would ensure that all of a virtual machine's processes are run together, maximizing locality and minimizing the latencies of the interactions between them.
  • Machine learning and stable kernels
    There are ways to get fixes into the stable kernel trees, but they require humans to identify which patches should go there. Sasha Levin and Julia Lawall have taken a different approach: use machine learning to distinguish patches that fix bugs from others. That way, all bug-fix patches could potentially make their way into the stable kernels. Levin and Lawall gave a talk describing their work at the 2018 Open Source Summit North America in Vancouver, Canada. Levin began with a quick introduction to the stable tree and how patches get into it. When a developer fixes a bug in a patch they can add a "stable tag" to the commit or send a mail to the stable mailing list; Greg Kroah-Hartman will then pick up the fix, evaluate it, and add it to the stable tree. But that means that the stable tree is only getting the fixes that are pointed out to the stable maintainers. No one has time to check all of the commits to the kernel for bug fixes but, in an ideal world, all of the bug fixes would go into the stable kernels. Missing out on some fixes means that the stable trees will have more security vulnerabilities because the fixes often close those holes—even if the fixer doesn't realize it.
  • Trying to get STACKLEAK into the kernel
    The STACKLEAK kernel security feature has been in the works for quite some time now, but has not, as yet, made its way into the mainline. That is not for lack of trying, as Alexander Popov has posted 15 separate versions of the patch set since May 2017. He described STACKLEAK and its tortuous path toward the mainline in a talk [YouTube video] at the 2018 Linux Security Summit. STACKLEAK is "an awesome security feature" that was originally developed by The PaX Team as part of the PaX/grsecurity patches. The last public version of the patch set was released in April 2017 for the 4.9 kernel. Popov set himself on the goal of getting STACKLEAK into the kernel shortly after that; he thanked both his employer (Positive Technologies) and his family for giving him working and free time to push STACKLEAK. The first step was to extract STACKLEAK from the more than 200K lines of code in the grsecurity/PaX patch set. He then "carefully learned" about the patch and what it does "bit by bit". He followed the usual path: post the patch, get feedback, update the patch based on the feedback, and then post it again. He has posted 15 versions and "it is still in progress", he said.

PostgreSQL 11: something for everyone

PostgreSQL 11 had its third beta release on August 9; a fourth beta (or possibly a release candidate) is scheduled for mid-September. While the final release of the relational database-management system (currently slated for late September) will have something new for many users, its development cycle was notable for being a period when the community hit its stride in two strategic areas: partitioning and parallelism. Partitioning and parallelism are touchstones for major relational database systems. Proprietary database vendors manage to extract a premium from a minority of users by upselling features in these areas. While PostgreSQL has had some of these "high-tier" items for many years (e.g., CREATE INDEX CONCURRENTLY, advanced replication functionality), the upcoming release expands the number considerably. I may be biased as a PostgreSQL major contributor and committer, but it seems to me that the belief that community-run database system projects are not competitive with their proprietary cousins when it comes to scaling enterprise workloads has become just about untenable. Read more