Language Selection

English French German Italian Portuguese Spanish

Slack

Slackware Removal of Lumina Desktop and Additional New Packages/Versions

Filed under
Slack
  • Lumina Desktop will be removed from my -current repository

    The Lumina Desktop is part of the TrueOS project, a FreeBSD variant. I packaged version 1.4.0.p1 for Slackware and it is part of the Plasma5 variant of my Slackware Live Edition.

    I noticed a while ago that Lumina would no longer start but it was low on my priority list to try and fix it.

    Today I found the time to look into this, but a recompilation against the latest Qt5 and other libraries, altough error-free, would not make the Lumina Desktop start successfully: it will start to load, but then you’ll hear a beep and you’re dumped at the command prompt or at the graphical login screen without evidence of what happened.

  • Valentine present for Slackers

    Today is Valentine’s Day. A moment to give some extra attention to people that are dear to you.

    In my case, that’s everyone who loves, uses, supports, advocates or develops Slackware Linux. For all of you, I uploaded “KDE-5_19.02” to the ‘ktown‘ repository. There’s some updates in there that might interest you, see below.
    If you do not (want to) run or install Slackware-current, I will make sure that a new ISO of the Slackware Live Plasma5 Edition will be available around the weekend. That way, you can safely try it out without having to touch your hard drive.

    As always, these packages are meant to be installed on a Slackware-current which has had its KDE4 removed first. These packages will not work on Slackware 14.2.

Uploading 15 GB of new Slackware Live Edition ISO images

Filed under
Slack

The squashfs modules in the XFCE ISOs are compressed with ‘xz’ to keep them as small as possible (so they will fit on a CDROM medium). All of the other ISOs are compressed with ‘zstd’ which gives the Live OS a speed boost of ~20% at the cost of 10% increase in the ISO size.

Read more

KDE4 and Plasma 5 for Slackware

Filed under
KDE
Slack
  • KDE4 and Qt4 deprecation in FreeBSD

    This is a reminder — for those who don’t read all of the FreeBSD mailing lists — that KDE4 is marked deprecated in the official ports tree for FreeBSD, and will be removed at the end of this year (in about 20 days). Then Qt4 will be removed from the official ports tree in mid-march.

    Since both pieces of software are end-of-life and unmaintained upstream already for several years, the kde@ team at FreeBSD no longer can maintain them. Recent time-sinks were dealing with OpenSSL 1.1.1, libressl, C++17, .. the code is old, and there’s newer, nicer, better-maintained code available generally by replacing 4 with 5.

  • KDE Plasma 5 for Slackware – end of the year edition

    I just uploaded a whole new batch of packages containing KDE Plasma5 for Slackware. The previous batch, KDE 5_18.10 is already two months old and has some library compatibility issues. The new KDE 5_18.12 for Slackware consists of KDE Frameworks 5.53.0, Plasma 5.14.4 and Applications 18.08.3. All this on top of Qt 5.11.3.
    Compiled on the latest Slackware -current, it’s running smoothly here on my laptop.
    I decided against upgrading to QT 5.12.0. This is a new LTS release, but I will wait for the other distros to find bugs in this new software. Next week, KDE will release KDE Applications 18.12.0 and that too is something I want to check a bit before releasing Slackware packages. Therefore it’s likely that a new batch of packages containing Qt 5.12 and KDE Applications 18.12 will see the light shortly after the New Year.

Absolute Linux: Testing Snapshot/15.0 Based on Slackware Current

Filed under
Reviews
Slack

Patrick, next Slackware and moving forward with KDE Plasma5

Filed under
Slack

I assume that many of you will have been reading the recent Linux Questions thread “Donating to Slackware” and in particular Patrick Volkerding’s reply where he explains that the Slackware Store (an entity independent of Slackware with which he has a business arrangement involving a percentage of sales profit and medical insurance) has not been paying him any money for the last two years and that most likely all the PayPal donations through the Store have gone into the pockets of the Store owners. Read that thread if you have not done so yet.
Basically Pat is broke. That thread lists a PayPal address which Pat eventually shared and where donations can be sent directly to him, so that he can fix his roof, his airco, his crashing server and his wife’s car. That would be a start.

That LQ thread is also perused to discuss possible ways forward for Pat (setting up a Patreon account, or a business PayPal account, etc) so that he can support his family and continue working on Slackware. To me it looks like the Store will be a thing of the past unless they change their attitude. Switching from a business model where revenue is generated from optical media sales, to a model where supporters set up a recurring payment in exchange for the prolonged existence of their favorite distro, and possibly get Pat to write up some hands-on stories as a reward, may ultimately benefit Pat, and Slackware, more than the way things are handled at the moment. If you are doubting the financial impact of a recurring payment through Patreon or PayPal, look at it this way: if you donate one euro per month, you will probably not even notice that the money is shifted out. But with 2000 people donating one euro per month, Pat would have a basic income (pre-tax) already. Not a lot, but it’s a start. The 2000 people is a rough estimate of the people who ordered a DVD or CD through the store: the owners told Pat that the earnings of the 14.2 release were 100K (and Pat got 15K out of that, go figure!). Divide that through ~50 euro per DVD, results in 2000 people. Then there’s all these people who donated money through the Store or bought shirts, caps and stickers. I think the amounts of money even a small community (like us Slackware users) can contribute should enable Pat to shed his financial worries. The fact that the Slackware Store basically has been ripping off the hand that feeds them is enraging and inexcusable.
This is all about a community standing up to provide support for what (or who) bonds us together.

Read more

Slackware: Chromium and Flash, Helping Patrick and Slackware Linux

Filed under
Slack
  • July security updates: Chromium and Flash

    I have uploaded new packages for Chromium. The version 67.0.3396.99 was released a month ago but the source remained unavailable for a while and then I “went under” for a while. Now that I finally built and uploaded it, I noticed there’s a new version up today (68.0.3440.75) but I will wait a bit with that one and focus on Plasma5 next.

  • Helping Patrick and Slackware Linux

Slackware creator in strife, claims store has not paid him

Filed under
Slack

The creator of the second oldest Linux distribution, Patrick Volkerding, claims he is in financial strife after the store, with which he reached an agreement to sell his work, stopped paying him two years ago.

In a post to the Linux Questions website, Volkerding, a hero to many early adopters of Linux, said that the store was set up as a 60:40 venture.

"And 60% seemed fair, since the idea was that the company would be providing health insurance, paying for the production of the goods, and handling shipping and related customer service," he wrote.

Read more

Slax 9.5.0 released

Filed under
Slack

I am happy to announce that a next version of Slax Linux has been released. Slax is a minimalistic, fully modular operating system. As usual, this version incorporates all upstream improvements from Debian stable, and fixes few small known bugs.

I am also happy to announce that it is now possible to purchase Slax preinstalled on an USB flash drive with hardware-based AES encryption. This device is universally usable because the encryption is performed directly by the drive itself, there is no software to install needed. Once disconnected, the USB drive automatically locks itself again. Payment is possible only with Bitcoin, because I truly wish to see PayPal and credit card companies to cease to exist soon.

Read more

The LiveSlak Project: Running Slackware-Current Live Images With or Without Persistence and Installing Them

Filed under
Slack
HowTos

Eric Hameleers has unofficially contributed to Slackware for what feels like forever. He not only runs his blog Alien Pastures dedicated to Slackware and offers a huge selection of packages pre-compiled on his vanilla systems, readily available for our perusal. He also offers the Ktown repository with updated packages of KDE4 and the next generation Plasma desktop for both the stable and testing branches of Slackware. He also started the Slackware Live project based on his own LiveSlak scripts to give people an opportunity to run Slackware current without
committing to an install and to get an idea what the next version will be like.

On 25th June the latest line of images was released, one for each desktop. Live ISOs are offered in 32 and 64bit, although only the Xfce and KDE4 images are available for both architectures. The other two images with MATE or a Plasma 5 preview substituted for KDE4 are 64bit only. This 1.2.0 release mirrors Slackware current as of 23/06/2018. Initially there was also a version with the Cinnamon desktop but this seems to have fallen behind.

Apart from the desktop chosen there are some differences in the size of the images. The Xfce spin is just under 700MB, the standard desktop version with KDE which is just named slackware-live-current is 3.1/3.0 GB respectively, the MATE version 2.1GB and the Plasma 5 edition a hefty 4.3GB, also due to extra software onboard. Read more about how the project came about and an overview with tips on Eric's blog.

Read more

The oldest, active Linux distro, Slackware, turns 25

Filed under
Slack

For many early Linux users, Slackware was their introduction. One user told me her first Linux install was Slackware—and she had to use a hex editor to fix the partition tables so that Slackware would install. Support for her hardware was added in a later release. Another got his start building the data center that would power one of the first internet-enabled real estate sites. In the mid-1990s, Slackware was one of the easiest distributions to get and didn't require a lot of effort to get IP masquerading to work correctly. A third person mentioned going to sleep while a kernel compile job ran, only to find out it had failed when he woke up.

All of these anecdotes would suggest a hard-to-use operating system. But Slackware fans don't see it that way. The project's website says the two top priorities are "ease of use and stability." For Slackware, "ease of use" means simplicity. Slackware does not include a graphical installer. Its package manager does not perform any dependency resolution. This can be jarring for new users, particularly within the last few years, but it also enables a deeper understanding of the system.

The different take on ease of use isn't the only thing unique about Slackware. It also does not have a public bug tracker, code repository, or well-defined method of community contribution. Volkerding and a small team of contributors maintain the tree in a rolling release called "-current" and publish a release when it meets the feature and stability goals they've set.

Read more

Syndicate content

More in Tux Machines

Ubuntu-Centric Full Circle Magazine and Debian on the Raspberryscape

  • Full Circle Magazine: Full Circle Weekly News #121
  • Debian on the Raspberryscape: Great news!
    I already mentioned here having adopted and updated the Raspberry Pi 3 Debian Buster Unofficial Preview image generation project. As you might know, the hardware differences between the three families are quite deep ? The original Raspberry Pi (models A and B), as well as the Zero and Zero W, are ARMv6 (which, in Debian-speak, belong to the armel architecture, a.k.a. EABI / Embedded ABI). Raspberry Pi 2 is an ARMv7 (so, we call it armhf or ARM hard-float, as it does support floating point instructions). Finally, the Raspberry Pi 3 is an ARMv8-A (in Debian it corresponds to the ARM64 architecture). [...] As for the little guy, the Zero that sits atop them, I only have to upload a new version of raspberry3-firmware built also for armel. I will add to it the needed devicetree files. I have to check with the release-team members if it would be possible to rename the package to simply raspberry-firmware (as it's no longer v3-specific). Why is this relevant? Well, the Raspberry Pi is by far the most popular ARM machine ever. It is a board people love playing with. It is the base for many, many, many projects. And now, finally, it can run with straight Debian! And, of course, if you don't trust me providing clean images, you can prepare them by yourself, trusting the same distribution you have come to trust and love over the years.

OSS: SVT-AV1, LibreOffice, FSF and Software Freedom Conservancy

  • SVT-AV1 Already Seeing Nice Performance Improvements Since Open-Sourcing
    It was just a few weeks ago that Intel open-sourced the SVT-AV1 project as a CPU-based AV1 video encoder. In the short time since publishing it, there's already been some significant performance improvements.  Since the start of the month, SVT-AV1 has added multi-threaded CDEF search, more AVX optimizations, and other improvements to this fast evolving AV1 encoder. With having updated the test profile against the latest state as of today, here's a quick look at the performance of this Intel open-source AV1 video encoder.
  • Find a LibreOffice community member near you!
    Hundreds of people around the world contribute to each new version of LibreOffice, and we’ve interviewed many of them on this blog. Now we’ve collected them together on a map (thanks to OpenStreetMap), so you can see who’s near you, and find out more!
  • What I learned during my internship with the FSF tech team
    Hello everyone, I am Hrishikesh, and this is my follow-up blog post concluding my experiences and the work I did during my 3.5 month remote internship with the FSF. During my internship, I worked with the tech team to research and propose replacements for their network monitoring infrastructure. A few things did not go quite as planned, but a lot of good things that I did not plan happened along the way. For example, I planned to work on GNU LibreJS, but never could find enough time for it. On the other hand, I gained a lot of system administration experience by reading IRC conversations, and by working on my project. I even got to have a brief conversation with RMS! My mentors, Ian, Andrew, and Ruben, were extremely helpful and understanding throughout my internship. As someone who previously had not worked with a team, I learned a lot about teamwork. Aside from IRC, we interacted weekly in a conference call via phone, and used the FSF's Etherpad instance for live collaborative editing, to take notes. The first two months were mostly spent studying the FSF's existing Nagios- and Munin-based monitoring and alert system, to understand how it works. The tech team provided two VMs for experimenting with Prometheus and Nagios, which I used throughout the internship. During this time, I also spent a lot of time reading about licenses, and other posts about free software published by the FSF.
  • We're Hiring: Techie Bookkeeper
    Software Freedom Conservancy is looking for a new employee to help us with important work that supports our basic operations. Conservancy is a nonprofit charity that promotes and improves free and open source software projects. We are home to almost 50 projects, including Git, Inkscape, Etherpad, phpMyAdmin, and Selenium (to name a few). Conservancy is the home of Outreachy, an award winning diversity intiative, and we also work hard to improve software freedom generally. We are a small but dedicated staff, handling a very large number of financial transactions per year for us and our member projects.

Security: Back Doors Running Amok, Container Runtime Flaw Patched, Cisco Ships Exploit Inside Products

  • Here We Go Again: 127 Million Accounts Stolen From 8 More Websites
    Several days ago, a hacker put 617 million accounts from 16 different websites for sale on the dark web. Now, the same hacker is offering 127 million more records from another eight websites.
  • Hacker who stole 620 million records strikes again, stealing 127 million more
    A hacker who stole close to 620 million user records from 16 websites has stolen another 127 million records from eight more websites, TechCrunch has learned. The hacker, whose listing was the previously disclosed data for about $20,000 in bitcoin on a dark web marketplace, stole the data last year from several major sites — some that had already been disclosed, like more than 151 million records from MyFitnessPal and 25 million records from Animoto. But several other hacked sites on the marketplace listing didn’t know or hadn’t disclosed yet — such as 500px and Coffee Meets Bagel. The Register, which first reported the story, said the data included names, email addresses and scrambled passwords, and in some cases other login and account data — though no financial data was included.
  • Vendors Issue Patches for Linux Container Runtime Flaw Enabling Host Attacks
  • How did the Dirty COW exploit get shipped in software?
    An exploit code for Dirty COW was accidentally shipped by Cisco with product software. Learn how this code ended up in a software release and what this vulnerability can do.

10 Cool Software to Try from CORP Repo in Fedora

In this article, we will share 10 cool software projects to try in Fedora distribution. All the apps or tools covered here can be found in COPR repository. However, before we move any further, let’s briefly explain COPR. Read more