Linux Blimp

It appears that Ikey Doherty, the founder and lead dev of Solus, has left the project.

But don’t worry Solus is in good hands.

Some Background

If you have never heard of Ikey before, no worries. I’ll provide some background information about him.

Ikey made his marks on Linux over the years by contributing to a variety of projects (not limited to the Brisk Menu and Linux Steam Integration). He worked on Linux Mint for while before starting his own Ubuntu based distro. After running into development limitations, Ikey created his own Linux distro from scratch. He did this all while working for Intel on their Linux distro. Last June, Ikey took the huge step of leaving his job at Intel to work full time on Solus.

Besides being involved with Solus full-time, Ikey joined the Late Night Linux podcast. In August of 17, the show covered a news story about the Krita project running into problems with the tax man. In that episode, Ikey revealed that he intended to make sure that Solus would not suffer a similar situation. In fact, he wanted to make sure that if something happened to him, the project would survive. Kinda prophetic.

The Current Situation

In July of this year, Ikey had to move from Ireland to England for personal reasons. During this time, he began making sure that the other Solus devs (Joshua and Bryan) had access to the Solus infrastructure. The plan was to continue the following day, but scheduling conflicts delayed it. Matters were complicated further when Ikey discovered his new location had a poor internet connection and he was unable to contribute much to Solus. On top of that, he got sick with the flu.

Towards the end of August, the Solus servers encountered several outages. The Solus team was unable to contact Ikey, partly because he had either deleted or withdrawn from his social media accounts. The hosting company was initially evasive, but later revealed that the service had not been paid. Without access to the server control panel or the PayPal account, Joshua and Bryan decided to move the whole thing to a new URL (getsol.us), which Joshua had purchased for direct downloads. During the mammoth task of moving all the required services to new hosting, Ikey contacted the team on September 7th: “and i am very very sick atm. all will be paid up for the next 30 days and gives me time to get back out and transfer to you. ill speak with you tomorrow afternoon/evening”. Ikey never followed up on this message.

In the wake of the server outages, the Solus team decided to check to see what services they had access to. The list looks something like this:

1. Dediserve provided the Solus domain name and DNS. They refused to hand over control to the Solus team.
2. Fastly is a CDN service that made the Solus packages available worldwide. They provided the Solus team with the necessary access.
3. Google Apps for Business was used to provide email and document collaboration. Google did not respond.
4. OVH hosted the Solus build, repo, and web servers. The team only had partial access via SSH. OVH did not hand over control but kept the servers up so the Solus team could migrate to a new hosting service.
5. Patreon was used to raise money to pay Ikey to work on Solus full-time. At first, Patreon refused to hand control of the account over to the Solus team. However, that has since changed. Currently, the Solus Patreon campaign is frozen. The Solus team has decided to stop accepting donations for the time being.
6. Money withdrawn from Patreon was stored in PayPal. They are still working to “recover this account”. Until they do, they won’t know how much money is actually available to the project.
7. SendGrid was used as the mail delivery service for Phabricator and the Forums. SendGrid did not respond to the Solus team, but they created a new account.

As I mentioned above, the Solus team is no longer accepting donations. It appears that even though Ikey intended to put some legal protections in place for the project, he never got around to it. The Solus team is planning to fix that:

“Going forward, we will continue to not accept any monetary donations until decided otherwise, or we have a legal entity such as the Software Freedom Conservancy handling legal and financial matters for Solus. I want to thank everyone that has continued to offer their support for Solus, whether that be financial or otherwise. We look forward to providing more means of donating to the project in the future once we’ve returned to more normal development operations and have a legal entity working on behalf of the project.”

The Future

The current Solus Devs (Joshua, Bryan, Peter) plan to continue the Solus project. They are already planning the next release of Solus: Solus 4. Solus 4 will focus on finalizing Budgie 10.5. The Software Center will also receive work in the 4.x branch. They will also be working to improve “build tooling, including continued improvements and updates to cuppa and eopkg-deps”. They also plan to make other changes that may include “sol, a new Installer, a power management replacement for TLP, and yes even a GTK4-based Budgie 11”.

Even though Ikey is no longer at the head, the team is very much led by his vision:

“Ikey’s vision for Solus is one that all of us on the Core Team share. Solus is a selfish, pragmatic obsession with building a technically excellent linux distribution. This vision is what attracted us all to the project in the first place. We each bring our own unique experiences and expertise to the table, with Ikey’s phenomenal mentoring over the years giving us an incredible foundation to build on.”

Ikey Speaks

The same day that the Solus team posted their second message about the transition, Phoronix published a message from Ikey. Right off the bat, he wants to set the record straight, “I’d like to start out by thanking the Solus team for all their hard work and passion over the years. By way of response to their recent blog post, I in no way see what they’ve done as a “hostile takeover”, rather, a natural evolution of the project.”

In fact, he seems to hand over all ownership of the Solus Project. “If one is to look at the timeline analysis from the Solus team, it is crystal clear that they are more passionate about the project than anyone, and will survive anything. For this reason I happily condone their leadership in the project, and assign any and all intellectual, naming and branding rights relating to the ownership of Solus to their collective with immediate and permanent effect, acknowledging them as the official owners and leadership of the project. “

Ikey does not come out and say what happened to him while he was out of touch with everyone else. Nor does he explain what made him disappear from social media, though this might point in the right direction, “I ask that they stay strong to their cause, and rise above the toxicity and politics that plague the Linux desktop world”.

It does appear that Ikey has started a family. “it’s unlikely I’ll be seeking personal project involvement of any description – as a new parent I must plan to father my child and support my family through work, instead of fathering my work and rely on my family supporting me.”

Final Thoughts

I was drawn to Solus in part by Ikey. He always seemed to look at some part of current computing wisdom and say, “Why are we doing that when this would work so much better? Why didn’t we do this before?” I also liked the fact that Solus was the little distro that wanted to succeed in a field full of almost carbon copies. On the other hand, Ikey always made sure that his innovations helped all Linux not just Solus.

I wish the team at Solus well. They have big shoes to fill, but they sound like they are cut from the same cloth as Ikey. I will keep Solus as one of my main distros for the foreseeable future.

I would like to address my final comment to Ikey (though I doubt he will ever see it). Ikey, my prayers are with you and your new family. I pray that you find happiness and peace on your new path. You may have encountered toxicity in the Linux community, but remember that you also helped a great number of people through your efforts. Always remember, the time that you spent working on Solus was not wasted.

Have you ever used Solus? What do you think of these recent events? Let us know in the comments below.

If you found this article interesting, please take a minute to share it on social media, Hacker News or Reddit.
Source

Fedora Design Suite Live is an open source and free operating system based on the latest Fedora technologies and built around the stylish and compelling GNOME desktop environment. Intially developed for the Fedora Design Team, the distribution aims to help artists of all kind to freely express their artistic visions.

Availability, boot options and supported platforms

It can be downloaded from the dedicated download section (see above) as two Live DVD ISO images of approximately 1.5GB in size, allowing users to deploy them on USB flash drives of 2GB or higher capacity, or burn them onto blank DVD discs.

The most important feature of a Live CD is that users can try the operating system without installing anything on their computers. In addition, it is also possible to start an existing OS from the first disk or run a memory diagnostic test.

The only Live CD tailored for designers

The Live CD comes with many useful and open source applications, which can be used for multimedia production and publishing. An interesting feature is that all applications are organized into categories, such as Accessories, Games, Graphics, Internet, Office, Programming, Sound & Video, Sundry, System Tools, Utilities, and Other.

Among the pre-installed graphical applications, we can mention GIMP image editor, Inkscape vector graphics editor, Scribus desktop publishing software, Synfig Studio 2D animation software, Phatch batch image processor, Dia diagram creator, Blender 3D animation renderer, Darktable RAW image editor, Entangle tethered shooting utility, and the entire Hugin suite.

Default applications include the FileZilla file transfer client, Mozilla Firefox web browser, Bluefish HTML editor, Empathy instant messenger, LibreOffice office suite, Evolution email and calendar client, Totem video player, Brasero CD/DVD burning software, Cheese webcam viewer, Audacity audio editor, PiTiVi video editor, and Rhythmbox music player.

Bottom line

No matter if you want to create CD sleeves, design websites, build GUIs (Graphical User Interfaces) for applications, create desktop backgrounds, flyers and posters, the Fedora Design Suite Live CD is here to help you achieve all this and much more with minimum effort and without having to pay for expensive products.

Source

The AGL Unified Code Base has been selected in the Software and Mobile Apps category

SAN FRANCISCO, CA, November 9, 2018 – Automotive Grade Linux (AGL), a collaborative cross-industry effort developing an open platform for the connected car, today announced that it has been named a CES® 2019 Innovation Awards Honoree for its Unified Code Base (UCB) platform. As an open source project hosted at The Linux Foundation, AGL is bringing together automakers, suppliers and technology companies to accelerate the development and adoption of a fully open software stack for all technology in the vehicle.

“We are very excited to be recognized as a CES 2019 Innovation Award Honoree, and it’s a testament to the power of open source software and industry collaboration,” said Dan Cauchy, Executive Director of Automotive Grade Linux at The Linux Foundation. “The credit really goes to all of the members who support AGL, and the developers who have invested the time and effort to build a robust platform that has quickly become the de facto industry standard.”

Developed through a joint effort by dozens of member companies, the AGL Unified Code Base (UCB) is an open source software platform for infotainment, telematics and instrument cluster applications. Sharing a single software platform across the industry reduces fragmentation and accelerates time-to-market by encouraging the growth of a global ecosystem of developers and application providers that can build a product once and have it work for multiple automakers.

Many AGL members have already started integrating the UCB into their production plans. Mercedes-Benz Vans is using AGL as a foundation for a new onboard operating system for its commercial vehicles, and Toyota’s AGL-based infotainment system is now in Toyota and Lexus vehicles globally.

The AGL UCB platform will be on display at CES 2019, January 8-11, 2019 in Las Vegas, in the Automotive Grade Linux booth in the Westgate Hotel Pavilion, booth 1614. To schedule a demo or meeting to learn more about joining AGL, please contact pr@automotivelinux.org.

About Automotive Grade Linux (AGL)

Automotive Grade Linux is a collaborative open source project that is bringing together automakers, suppliers and technology companies to accelerate the development and adoption of a fully open software stack for the connected car. With Linux at its core, AGL is developing an open platform from the ground up that can serve as the de facto industry standard to enable rapid development of new features and technologies. Although initially focused on In-Vehicle-Infotainment (IVI), AGL is the only organization planning to address all software in the vehicle, including instrument cluster, heads up display, telematics, advanced driver assistance systems (ADAS) and autonomous driving. The AGL platform is available to all, and anyone can participate in its development. Learn more: https://www.automotivelinux.org/

Automotive Grade Linux is a Collaborative Project at The Linux Foundation. Linux Foundation Collaborative Projects are independently funded software projects that harness the power of collaborative development to fuel innovation across industries and ecosystems. www.linuxfoundation.org

###

The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our trademark usage page: https://www.linuxfoundation.org/trademark-usage. Linux is a registered trademark of Linus Torvalds.

Source

Published: November 9, 2018
Source

We’re running out of time to tackle climate change. Could an open source, distributed approach build the necessary momentum? Executive director of LF Energy tells Techworld about the new initiative which already has some enterprises on board.

The prospects from the UN’s most recent climate report are bleak. There are less than two decades until the point of no return for the planet’s climate, and the leaders of major countries seem to be retracting political willingness to fix the existential threat.

But, the roadblocks might not be as daunting as they first appear. Shuli Goodman, executive director of the newly created LF Energy group, hopes to fundamentally transform the way energy is distributed, reduce waste, and build new models that could be scaled out with an open source framework.

Read more at TechWorld

Click Here!

Source

Basic Ingest optimizes data flow for high volume data ingestion workloads by removing the pub/sub Message Broker from the ingestion path. As a result, customers now have a more cost effective option to send device data to other AWS services while continuing to benefit from all the security and data processing features of AWS IoT Core.

Basic Ingest is now available in AWS GovCloud (US), US East (N Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), China (Beijing) operated by Sinnet, EU (Frankfurt), EU (Dublin), and EU (London) AWS regions.

Visit the Basic Ingest Documentation to learn more about this feature. For more information about AWS IoT Core, visit the product page.

Source

Search functions in Linux file managers aren’t all that great. Most are passable with minimal functionality and fairly slow search times, but there really aren’t any exceptional ones. Even KDE’s Baloo, that spends a ton of time indexing files, really doesn’t perform the way you’d hope a modern search would.

Thankfully, a better option has popped up in the form of FSearch. FSearch was created by a developer who was tired of the poor search performance in Linux file managers and decided to take matters into his own hands. While you might not feel that a standalone file search is necessary, you’ll probably change your mind pretty quickly after trying FSearch out.

Installation

FSearch is packaged and available in an Ubuntu PPA. That makes things a bit more complicated on other distributions, but it’s very simple on Ubuntu. Debian users can also take advantage of the PPA with a bit of extra work.

Ubuntu

The FSearch PPA is like any other. Import it with Apt, and update your sources.

sudo add-apt-repository ppa:christian-boxdoerfer/fsearch-daily
sudo apt update

Debian

If you’re on Debian, you can use the PPA, but it’ll just require a bit of extra work to get set up. First, open a terminal and create a new .list file with sudo.

sudo touch /etc/apt/sources.list.d/fsearch.list

Open the file with your text editor of choice, and add in the following two lines.

deb http://ppa.launchpad.net/christian-boxdoerfer/fsearch-daily/ubuntu cosmic main
deb-src http://ppa.launchpad.net/christian-boxdoerfer/fsearch-daily/ubuntu cosmic main

Now, import the keys for the repository.

sudo apt-key adv –keyserver keyserver.ubuntu.com –recv-keys 75555AFF5215AD9DBFD8CDB952B2FFB2DC496F40

The only thing left to do is update Apt.

You’re ready to start installing FSearch.

sudo apt install fsearch-trunk

Arch

FSearch is actually available in the AUR. You can use whichever AUR install process you’re most comfortable with to add it to your system. You can find the details on FSearch’s AUR page.

Fedora

Fedora users are going to need to build FSearch from its source. This method is officially supported, so you shouldn’t run into any hangups.

Start by installing the build requirements.

sudo dnf install automake autoconf intltool libtool autoconf-archive pkgconfig glib2-devel gtk3-devel git

Next, clone the source and change into the resulting directory.

git clone https://github.com/cboxdoerfer/fsearch.git
cd fsearch

Build FSearch and install it.

./autogen.sh
./configure
make
sudo make install

Now, you should have a working FSearch install that you can launch graphically.

Add Your Database

Open up FSearch. When the window first pops open, you’ll see a search field at the top, a big blank area with instructions to add a database, and not much else. FSearch is a search utility. It was built to do that one thing and do it well. In order to move as quickly as it does, FSearch relies on a database that it creates from the directories that you want to be able to search. The last step in getting set up is adding that directory.

Click on “Edit” on the menu along the top of your FSearch window. Pick “Preferences” in the resulting dropdown menu.

A new window will open with a series of tabs across the top. Click on the “Database” tab. The main body of the tab is occupied by a big white space.

To the left of that space are two tabs for “Include” and “Exclude.” They’re exactly what they sound like. The “Include” tab lists folders to include in your searches. The “Exclude” tab lists subfolders you want to exclude from the included folders.

On the right you’ll find two buttons to add or remove directories. Click the one to add a directory. It will open a file browser window. Choose a directory that you want searchable and confirm. You can absolutely just add your whole /home directory, which works pretty well.

When you’re done, FSearch will scan through the directory and build its database. This is surprisingly fast and actually won’t slow down your computer too much.

Searching with FSearch

You’ll notice that the big blank space on the main screen now has a magnifying glass icon faded into the background to signify that you’re ready to start searching. Start typing the name of a file or folder that you know you’ll find in your search directory. You’ll immediately see FSearch start populating the big empty space with possible results in order of accuracy.

Try a few more searches. You should also notice that FSearch gives you complete paths to your files in order to make it easy for you to access them after you’re done searching.

If you’re finding too many erroneous results coming from a cache folder or something similar, you can always return to the database tab under the Preferences menu and add the problem directory to the exclusion list.

There’s not much else to it. FSearch follows the Unix philosophy of “Do one thing and do it well,” and it really does do that one thing very well. FSearch is insanely fast, and it will find you your files without you needing to wait too long, or at all.

Is this article useful?

Source

Fedora is the next generation Linux distribution from Red Hat.

Fedora is now available from Red Hat and at distinguished mirror sites near you, and is also available in the torrent.

Fedora has expanded in this release to four binary ISO images and four source ISO images, and is available for both x86-64 and i386 and also PPC machines.

The Fedora Project is a Red-Hat-sponsored and community-supported open source project. It is also a proving ground for new technology that may eventually make its way into Red Hat products. It is not a supported product of Red Hat, Inc.

The goal of The Fedora Project is to work with the Linux community to build a complete, general purpose operating system exclusively from free software. Development will be done in a public forum. The project will produce time-based releases of Fedora Core about 2-3 times a year with a public release schedule.

The Red Hat engineering team will continue to participate in the building of Fedora Core and will invite and encourage more outside participation than was possible in Red Hat Linux.

By using this more open process, we hope to provide an operating system that uses free software development practices and is more appealing to the open source community.

Source

Many new gRPC users are surprised to find that Kubernetes’s default load balancing often doesn’t work out of the box with gRPC. For example, here’s what happens when you take a simple gRPC Node.js microservices app and deploy it on Kubernetes:

While the voting service displayed here has several pods, it’s clear from Kubernetes’s CPU graphs that only one of the pods is actually doing any work—because only one of the pods is receiving any traffic. Why?

In this blog post, we describe why this happens, and how you can easily fix it by adding gRPC load balancing to any Kubernetes app with Linkerd, a CNCF service mesh and service sidecar.

Read more at Kubernetes Blog

Click Here!

Source

The software packages in a Debian stable version is very old compare to other distributions like Arch Linux or even Ubuntu. Debian stable releases are very stable and secure as it only includes thoroughly tested software packages. To ensure stability and security, new software packages are not used in Debian stable versions as the Debian team needs time to test them and make sure these packages meets the stability and security requirements of Debian stable releases.

So using old version of software packages is good in a way. If you’re looking for bleeding edge software packages in Debian, then one alternative is Debian testing releases. Debian testing has more up to date software packages. But don’t expect it to be like Arch Linux.

Let’s say, you need the stability of Debian stable and still need some specific up to date software packages which is available in the Debian testing releases. Well, that’s when Debian Backports package repository comes in. According to the official website of Debian, the Debian Backports packages are packages from the Debian testing release (or the next version of Debian) adjusted and recompiled for using in Debian stable releases.

The official website of Debian also states that, if you use Debian Backports packages, then upgrade to the next Debian release (when it’s released) will not cause problems at all as the packages are already available there. There is a little bit problem with Debian Backports packages. The packages are not extensively tested as in Debian stable packages. Again, Debian Backports packages may conflict with your Debian stable packages. So you should be careful when using Debian Backports packages.

Debian recommends you use only the packages you need from the Debian Backports package repository. You should not use all the available Backports packages on Debian stable.

In this article, I will show you how to use Debian Backports package repository on your Debian stable release. I will be using Debian 9 Stretch (which is the latest version of Debian stable release at the time of this writing) in this article. So Let’s get started.

Debian Backports package repository contains a lot of Debian packages. You can search to find out whether the package of software version you’re looking for is available in the Debian Backports package repository from your web browser.

First, go to the official website of Debian Backports package repository at https://backports.debian.org/Packages/

Then, type in the package name and click on search. If the package is available in the backports package repository, it should show up.

Adding Debian Backports Package Repository to Debian 9 Stretch:

In this section, I will show you how to add the Debian Backports package repository on your Debian 9 Stretch stable release. First, open up a Terminal and run the following command:

$ echo “deb http://ftp.debian.org/debian stretch-backports main” |
sudo tee /etc/apt/sources.list.d/backports.list

The Debian backports package repository should be added to your Debian 9 Stretch machine.

Now, update the APT package repository cache with the following command:

As you can see, the APT package repository cache is updated and it included the Debian backports package repository as well.

Adding Debian Backports Package Repository to Debian 8 Jessie:

In this section, I will show you how to add the Debian Backports package repository on your Debian 8 Jessie stable release.

First, open up a Terminal and run the following command to add the Debian Jessie Backports package repository to your Debian 8 Jessie machine:

$ echo “deb http://ftp.debian.org/debian jessie-backports main” |
sudo tee /etc/apt/sources.list.d/backports.list

Debian Backports package repository should be added to your Debian 8 Jessie machine.

Now update the APT package repository cache of your Debian 8 Jessie machine with the following command:

As you can see, the APT package repository cache is updated and it also includes the Debian Backports package repository.

Installing Packages from Debian Backports Package Repository:

By default, all backports package repositories are disabled on Debian. If you want to install a package from Debian backports package repository, you have to tell the APT package manager that you really do want to install a package from Debian backports package repository specifically. That’s a great safeguard.

To search for a package (let’s say owncloud) in the Debian backports package repository, run the following command:
On Debian 9 Stretch:

$ sudo apt -t stretch-backports search owncloud

On Debian 8 Jessie:

$ sudo apt -t jessie-backports search owncloud

As you can see, the backports repository packages are listed.

To install a package (let’s say owncloud-client) from Debian backports package repository, run the following command:

On Debian 9 Stretch:

$ sudo apt -t stretch-backports install owncloud-client

On Debian 8 Jessie:

$ sudo apt -t jessie-backports install owncloud-client

Now, press y and then press <Enter>.

As you can see, the packages are being downloaded from the Debian Backports package repository.

As you can see, the owncloud-client is installed from the Debian backports package repository.

As you can see, the ownCloud GUI client I just installed from the Debian backports package repository runs just fine.

Removing Packages from Debian Backports Package Repository:

If you want to remove a package that you installed from the Debian backports package repository, then this section is for you. To remove a package (let’s say owncloud-client) that you installed from the Debian backports package repository, run the following command:

On Debian 9 Stretch:

$ sudo apt -t stretch-backports remove owncloud-client

On Debian 8 Jessie:

$ sudo apt -t jessie-backports remove owncloud-client

Now, press y and then press <Enter>.

The owncloud-client package should be removed.

Removing Debian Backports Package Repository:

If you’ve followed this article to add Debian backports package repository on your Debian 9 Stretch or Debian 8 Jessie machine, then you can remove it very easily with the following command:

$ sudo rm -v /etc/apt/sources.list.d/backports.list

Debian Backports package repository should be removed.

Now, update the APT package repository cache with the following command:

The APT package repository cache should be updated.

So, that’s how you use Debian backports package repository on Debian. Thanks for reading this article.

Source