Language Selection

English French German Italian Portuguese Spanish

Free and Proprietary Software: FAI.me, Aptdaemon, Justmd, TeamViewer, Vivaldi

Filed under
Software
  • FAI.me build server improvements

    Only one week ago, I've announced the FAI.me build service for creating your own installation images.

  • Aptdaemon

    I am glad to announce aptdaemon: It is a DBus controlled and PolicyKit using package management daemon build on python-apt.

    If the above description reminds you of PackageKit you won't be completely wrong. Aptdaemon reuses some design concepts and code from PackageKit. As the author of the PackageKit apt backend I run into some policy problems: PackageKit only allows non-interactive actions. So there is no support for debconf, CDROMs and configuration conflict handling. Nevertheless thanks to Richard Hughes for his efforts on making package management less of a pain.

  • Justmd – A Lightweight Cross-Platform Markdown Editor

    We have written on a couple of Markdown editors so far but not on this one, and I don’t think you have heard about it yet because it is pretty much a new project so read on.

    Justmd is a simple, lightweight, cross-platform, and electron-based application with a focus on creating and managing smart documents. Its best features include its live preview mode which comes along with synchronized scrolling as well as smart copying and pasting of images, words and HTML.

  • TeamViewer 13 Now Available For Linux As A Native 64-bit Port

    -
    The latest version of the TeamViewer remote control / desktop sharing / web conferencing software is now available for Linux with a number of improvements.

    TeamViewer 13 is now available for Linux, currently in preview form. Besides the iOS screen sharing with remote support, better file transfer abilities, and other key improvements, there are also a number of Linux-specific improvements too.

    This Linux build of TeamViewer 13 is now "native" for Linux in that it no longer depends upon Wine. TeamViewer 13 for Linux is also now a native 64-bit package without requiring 32-bit dependencies. Additionally, TeamViewer for Linux is now available in DEB and RPM package form.

  • Vivaldi Browser Now Available For Raspberry Pi And ARM Based Linux Hardware

    Raspberry Pi enthusiasts and those of you using ARM based Linux devices, may be interested to know that Vivaldi has this week released an experimental build of the Vivaldi browser which is now available to download for Linux on ARM devices, including the awesome Pi mini PC. In addition to the Windows, macOS and Linux (x86/x86-64), operating systems. The Vivaldi browser is now available for a range of ARM based Linux devices and is now supported by the Raspberry Pi Zero, Raspberry Pi 2 and Raspberry Pi 3 systems as well as CubieBoard, ASUS Tinker Board and more. Jon von Tetzchner, CEO at Vivaldi Technologies explains :

  • Vivaldi Web Browser Now Available For Linux ARM / Raspberry Pi

    Are you still using the Vivaldi web browser? If so, you can now use it on ARM devices like the Raspberry Pi.

    Vivaldi certainly hasn't been generating the attention these days like it did when it was first released last year to much fanfare by former Opera users and developers. This Blink-powered browser is now available for Linux on ARM as the project's latest news.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

KDE4 and Plasma 5 for Slackware

  • 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.

Programming: GCC, LLVM, Rust, Ruby and Python

  • GCC 9 Guts Out The PowerPC SPE Support
    It should come as no surprise since it was deprecated in this year's GCC 8 release, but the PowerPC SPE code has been removed. This isn't to be confused with conventional POWER/PowerPC but rather PowerPC SPE that is for the "Signal Processing Engine" on older FreeScale/IBM cores like the e500. It's not all that important these days and doesn't affect newer versions of the 64-bit Power support.
  • LLVM's OpenMP Runtime Picks Up DragonFlyBSD & OpenBSD Support
    Good news for those using the LLVM Clang compiler on OpenBSD or DragonFlyBSD: the OpenMP run-time should now be supported with the latest development code.
  • Nick Cameron: Rust in 2022
    In case you missed it, we released our second edition of Rust this year! An edition is an opportunity to make backwards incompatible changes, but more than that it's an opportunity to bring attention to how programming in Rust has changed. With the 2018 edition out of the door, now is the time to think about the next edition: how do we want programming in Rust in 2022 to be different to programming in Rust today? Once we've worked that out, lets work backwards to what should be done in 2019. Without thinking about the details, lets think about the timescale and cadence it gives us. It was three years from Rust 1.0 to Rust 2018 and I expect it will be three years until the next edition. Although I think the edition process went quite well, I think that if we'd planned in advance then it could have gone better. In particular, it felt like there were a lot of late changes which could have happened earlier so that we could get more experience with them. In order to avoid that I propose that we aim to avoid breaking changes and large new features landing after the end of 2020. That gives 2021 for finishing, polishing, and marketing with a release late that year. Working backwards, 2020 should be an 'impl year' - focussing on designing and implementing the things we know we want in place for the 2021 edition. 2019 should be a year to invest while we don't have any release pressure. To me, investing means paying down technical debt, looking at our processes, infrastructure, tooling, governance, and overheads to see where we can be more efficient in the long run, and working on 'quality of life' improvements for users, the kind that don't make headlines but will make using Rust a better experience. It's also the time to investigate some high-risk, high-reward ideas that will need years of iteration to be user-ready; 2019 should be an exciting year!
  • A Java Developer Walks Into A Ruby Conference: Charles Nutter’s Open Source Journey
    As a Java developer, Nutter began looking for an existing way to run Ruby within a Java runtime environment, specifically a Java virtual machine (JVM). This would let Ruby programs run on any hardware or software platform supported by a JVM, and would facilitate writing polyglot applications that used some Java and some Ruby, with developers free to choose whichever language was best for a particular task.
  • Good ciphers in OpenJDK
  • Don’t delete the same file in its own directory
  • Create a home button on the pause scene

Audiocasts/Shows: Going Linux, Linux Thursday and More

  • Going Linux #358 · Listener Feedback
    This month we have voice feedback from Paul, suggestions on alternatives for G+, a question on OpenVPN, feedback and problems moving to Linux. Troy provides a Going Linux story on software for Linux users.
  • Linux Thursday - Dec 6, 2018
  • Gnocchi: A Scalable Time Series Database For Your Metrics with Julien Danjou - Episode 189
    Do you know what your servers are doing? If you have a metrics system in place then the answer should be “yes”. One critical aspect of that platform is the timeseries database that allows you to store, aggregate, analyze, and query the various signals generated by your software and hardware. As the size and complexity of your systems scale, so does the volume of data that you need to manage which can put a strain on your metrics stack. Julien Danjou built Gnocchi during his time on the OpenStack project to provide a time oriented data store that would scale horizontally and still provide fast queries. In this episode he explains how the project got started, how it works, how it compares to the other options on the market, and how you can start using it today to get better visibility into your operations.

Best Lightweight Linux Distros for Older Computers

Don’t throw away that old Pentium III tower and CRT monitor just yet! While that old laptop in the closet may not be able to run Windows 10 or macOS Mojave, it doesn’t mean it’s destined for the dump. Many Linux distributions are made specifically for utilizing the ancient, underpowered hardware found in older machines. By installing these lightweight distros, you can breathe new life into an old PC thought to be long past its prime. Here are the best lightweight Linux distros that we’ve picked out from the pile. Read more