Language Selection

English French German Italian Portuguese Spanish

Linux Journal

Syndicate content
Updated: 3 hours 49 min ago

Kernel 5.2 Is Out, Tutanota Launches a Fully Encrypted Calendar, ISPA UK Announces Internet Hero and Villain Nominations, Tesla to Start Providing a Free Self-Driving Chip, and System76's Thelio Desktop Now Available with Third-Gen AMD Rizen Processors

Monday 8th of July 2019 01:57:33 PM

News briefs for July 8, 2019.

Kernel 5.2 has been released. Linus Torvalds writes, "...there really doesn't seem to be any reason for another rc, since it's been very quiet. Yes, I had a few pull requests since rc7, but they were all small, and I had many more that are for the upcoming merge window. Part of it may be due to the July 4th week, of course, but whatever - I'll take the quiet week as a good sign."

Tutanota has just launched a fully encrypted free calendar. Matthias Pfau, co-founder and developer of Tutanota, says this of the new calendar: "With our encryption expertise, we have not only made sure that all data people enter is encrypted, we are also encrypting the notifications for upcoming events. In contrast to other calendar services (e.g. Google), we do not know when, where, and with whom people have an appointment. Basically, we as the provider remain completely blind to people's daily habits." See the Tutanota Blog for more information.

The Internet Services Provides' Association (ISPA) UK has announced this year's nominations for Internet Hero and Villain. In the running for ISPA Internet Hero are Sir Tim Berners-Lee; Andrew Ferguson OBE, Editor Thinkbroadband; and Oscar Tapp-Scotting and Paul Blaker, Global Internet Governance Team, DCMS. Nominated for villain are Mozilla; Article 13 Copyright Directive; and Donald Trump. The winners will be chosen by the ISPA Council and announced on July 11, 2019. See ispa.org for the reasons behind the nominations.

Elon Musk says Tesla will "most likely" start providing a free self-driving chip upgrade to those with older Teslas later this year. The Verge reports that "The new FSD chip is the first to have been designed in-house. Tesla says it offers 21 times the performance of the Nvidia chips it replaces—a claim Nvidia disputes. The new chip has been shipping in Model S, X, and 3 cars since before its announcement, but soon it will be offered as a free upgrade to half a million Tesla owners." In addition, The Verge article notes that Musk claims the new chip "has enough power to eventually allow for fully self-driving cars, if and when the software catches up."

System76's Thelio desktop now available with third generation AMD Ryzen processors. According to BetaNews, "The base model, which is priced at $999, still comes with a 2nd gen Ryzen 5 2400G (quad-core). This is still a very capable chip, but not the latest and greatest. For only about $200 more, however, you can opt for a super-new 3rd gen Ryzen 5 3600X (hexa-core). For even more money, you can also choose a Ryzen 7 3800X (octa-core) or the insanely powerful 12-core Ryzen 9 3900X. That 3900X is notable for rivaling Intel's much pricier Core i9 chips." Go here to design and buy your own.

News kernel Tutanota Security Privacy Tesla System76

Contributor Agreements Considered Harmful

Monday 8th of July 2019 11:30:00 AM
by Eric S. Raymond

Why attempts to protect your project with legal voodoo are likely to backfire on you.

I have a little list (they never will be missed) of stupid things that open-source projects should stop doing. High on this list are CLAs (Contributor License Agreements) and their cousin the mandatory CA (Copyright Assignment).

In this article, I explain why CLAs and CAs are bad ideas and what we ought to be doing instead. In obedience to custom, at this point I issue the ritual disclaimer "I am not a lawyer", but one does not have to be a lawyer to understand the law and game out the ways CLAs and CAs fail to achieve their intended purpose. And, I have researched these failure modes with both lawyers and executives that have literally billions of dollars at stake around IP violations.

I've made a distinction between CAs and CLAs; we can make a further one between ICLAs (Individual Contributor License Agreements) and CCLAs (Corporate Contributor License Agreements). While all are about equally useless, they have slightly differing failure modes.

First, let's consider the ICLA. Some projects require that you sign one before being allowed to submit changes to their repository. Typically, it requires you to assert that (a) you affirmatively choose to license your contributions to the project, and (b) you have the right to do that.

Here's the problem. If you are employed, you almost certainly cannot make claim (b), and the project you are probably trying to help is only setting itself up for trouble if it behaves as though you can. The problem is that most employment contracts define any software you write on working hours or even off hours in connection with your job as "work for hire", and you don't own the rights to work for hire—your employer does.

CAs, such as the Free Software Foundation requires, have exactly the same problem. You don't own the copyright on a work for hire either. Therefore, you can't assign it. I'll get to the case of individual developers not in a work-for-hire situation in a bit.

The CCLA exists as an attempt to address the problems with ICLAs. It's not an agreement that you sign, it's an agreement your employer has to have pre-negotiated with the project to which you want to contribute. You then have to offer the project an identity that it can associate with that CCLA so it knows your contributions are covered.

That at least sounds like it might be useful. Why isn't it? To understand this, we need to do a bit more threat modeling. What is it that open-source projects hope to prevent using CCLAs?

Go to Full Article

Debian 10 "Buster" Coming Tomorrow, GRUB 2.04 Released, PineBook Pro Laptop Available for Pre-Order Soon, Raspberry Pi Sticker Give-Away and IPFire 2.23 Core Update 134 to Fix Security Issue

Friday 5th of July 2019 01:50:46 PM

News briefs for July 5, 2019.

Debian 10 "Buster" is coming tomorrow. You can follow the live coverage of the release here or @debian on Twitter. You also can join a release party or celebrate online at the Debian Party Line.

GRUB 2.04 has been released. According to Phoronix, this version, which has been two years in the making, includes RISC-V architecture support, native UEFI Secure Boot support, support for the F2FS filesystem and more. You can download it from GNU Savannah.

The PineBook Pro laptop will be available for pre-order July 25, 2019. OMG! Ubuntu! reports that the $199 PineBook Pro will now include privacy switches to disable the internal Bluetooth and WiFi module, the webcam and the microphone at the hardware level. Go to Pine64.org for specs and more details.

RaspberryPi.org is giving away stickers. All you need to do is leave a comment on their site or tweet them @Raspberry_Pi, with the hashtag #GimmeRaspberryPiStickers by midnight (BST) Monday, July 8th. They have ten packs to give away and winners will be chosen at random.

IPFire 2.23 Core Update 134 was released this week. This release contains security fixes in the kernel for the "SACK Panic" attack and some other smaller fixes. SACK Panic refers to CVE-2019-11477 and CVE-2019-11478, which are DoS attacks against the kernel's TCP stack. The IPFire blog post notes that "The first one made it possible for a remote attacker to panic the kernel and a second one could trick the system into transmitting very small packets so that a data transfer would have used the whole bandwidth but filled mainly with packet overhead. The IPFire kernel is now based on Linux 4.14.129, which fixes this vulnerability and fixes various other bugs." Go here to download.

News Debian GRUB PineBook Pro Pine64 Laptops Raspberry Pi IPFire Security

Lessons in Vendor Lock-in: Google and Huawei

Friday 5th of July 2019 11:00:00 AM
by Kyle Rankin

What happens when you're locked in to a vendor that's too big to fail, but is on the opposite end of a trade war?

The story of Google no longer giving Huawei access to Android updates is still developing, so by the time you read this, the situation may have changed. At the moment, Google has granted Huawei a 90-day window whereby it will have access to Android OS updates, the Google Play store and other Google-owned Android assets. After that point, due to trade negotiations between the US and China, Huawei no longer will have that access.

Whether or not this new policy between Google and Huawei is still in place when this article is published, this article isn't about trade policy or politics. Instead, I'm going to examine this as a new lesson in vendor lock-in that I don't think many have considered before: what happens when the vendor you rely on is forced by its government to stop you from being a customer?

Too Big to Fail

Vendor lock-in isn't new, but until the last decade or so, it generally was thought of by engineers as a bad thing. Companies would take advantage the fact that you used one of their products that was legitimately good to use the rest of their products that may or may not be as good as those from their competitors. People felt the pain of being stuck with inferior products and rebelled.

These days, a lot of engineers have entered the industry in a world where the new giants of lock-in are still growing and have only flexed their lock-in powers a bit. Many engineers shrug off worries about choosing a solution that requires you to use only products from one vendor, in particular if that vendor is a large enough company. There is an assumption that those companies are too big ever to fail, so why would it matter that you rely on them (as many companies in the cloud do) for every aspect of their technology stack?

Many people who justify lock-in with companies who are too big to fail point to all of the even more important companies who use that vendor who would have even bigger problems should that vendor have a major bug, outage or go out of business. It would take so much effort to use cross-platform technologies, the thinking goes, when the risk of going all-in with a single vendor seems so small.

Huawei also probably figured (rightly) that Google and Android were too big to fail. Why worry about the risks of being beholden to a single vendor for your OS when that vendor was used by other large companies and would have even bigger problems if the vendor went away?

Go to Full Article

Finishing Up the Bash Mail Merge Script

Thursday 4th of July 2019 12:00:00 PM
by Dave Taylor

Finally, I'm going to finish the mail merge script, just in time for Replicant Day.

Remember the mail merge script I started writing a while back? Yeah, that was quite some time ago. I got sidetracked with the Linux Journal Anniversary special issue (see my article "Back in the Day: UNIX, Minix and Linux"), and then I spun off on a completely different tangent for my last article ("Breaking Up Apache Log Files for Analysis"). I blame it on...

SQUIRREL!

Oh, sorry, back to topic here. I was developing a shell script that would let you specify a text document with embedded field names that could be substituted iteratively across a file containing lots of field values.

Each field was denoted by #fieldname#, and I identified two categories of fieldnames: fixed and dynamic. A fixed value might be #name#, which would come directly out of the data file, while a dynamic value could be #date#, which would be the current date.

More interesting, I also proposed calculated values, specifically #suggested#, which would be a value calculated based on #donation#, and #date#, which would be replaced by the current date. The super-fancy version would have a simple language where you could define the relationship between variables, but let's get real. Mail merge. It's just mail merge.

Reading and Assigning Values

It turns out that the additions needed for this script aren't too difficult. The basic data file has comma-separated field names, then subsequent lines have the values associated with those fields.

Here's that core code:

if [ $lines -eq 1 ] ; then # field names # grab variable names declare -a varname=($f1 $f2 $f3 $f4 $f5 $f6 $f7) else # process fields # grab values for this line (can contain spaces) declare -a value=("$f1" "$f2" "$f3" "$f4" "$f5" "$f6" "$f7")

The declare function turns out to be ideal for this, allowing you to create an array varname based on the contents of the first line, then keep replacing the values of the array value, so that varname[1] = value[1], and so on.

To add the additional variables #date# and #suggested#, you simply can append them to the varname and value arrays. The first one is easy, but it did highlight a weakness in the original code that I had to fix by adding quotes as shown:

Go to Full Article

Linux Mint Announces MintBox 3, NVIDIA Open-Sources Its TensorRT Library, Ubuntu's Wallpaper Competition for Eoan Ermine Open for Submissions, Google Released Its Android Security Patch for July and Whonix 15 Now Available

Wednesday 3rd of July 2019 01:50:32 PM

News briefs for July 3, 2019.

The Linux Mint folks yesterday announced that they're working with Compulab again on the next MintBox mini, the most powerful MintBox ever. MintBox 3 will be based on Airtop 3. The release date has yet to be announced. The unfinalized specs are listed as: "1. Basic configuration: $1543 with a Core i5 (6 cores), 16 GB RAM, 256 GB EVO 970, Wi-Fi and FM-AT3 FACE Module. 2. High end: $2698 with Core i9, GTX 1660 Ti, 32 GB RAM, 1TB EVO 970, WiFi and FM-AT3 FACE Module."

NVIDIA yesterday announced it has open-sourced its TensorRT Library and associated plugins. From Phoronix: "Included via NVIDIA/TensorRT on GitHub are indeed sources to this C++ library though limited to the plug-ins and Caffe/ONNX parsers and sample code. Building the open-source TensorRT code still depends upon the proprietary CUDA as well as other common build dependencies. But nice at least seeing the TensorRT code more open now than previously."

Ubuntu announces its wallpaper competition for Eoan Ermine is now open for submissions. To enter, post your image to the thread here. The competition will close in early September. Go here for more information.

Google released its Android Security Patch for July 2019 this week for all supported Pixel devices. Softpedia News reports that the patch "address a total of 33 security vulnerabilities affecting Android devices, which were discovered in the Android system, framework, library, media framework, as well as Qualcomm components, including closed-source ones. The most critical flaw was discovered in Android's Media framework." See the Security Bulletin for details.

Whonix 15 has been released. This new version of the desktop OS designed for advanced security and privacy is based on Debian Buster and includes many major changes and new features. See the ChangeLog for details.

News Linux Mint MintBox NVIDIA Ubuntu Google Android Security Whonix

In the End Is the Command Line

Wednesday 3rd of July 2019 11:30:00 AM
by Doc Searls

Times have changed every character but one in Neal Stephenson's classic. That one is Linux.

I was wandering through Kepler's, the legendary bookstore, sometime late in 1999, when I spotted a thin volume with a hard-to-read title on the new book table. In the Beginning...Was the Command Line, the cover said.

The command line was new to me when I started writing for Linux Journal in 1996. I hadn't come from UNIX or from programming. My tech background was in ham radio and broadcast engineering, and nearly all my hacking was on RF hardware. It wasn't a joke when I said the only code I knew was Morse. But I was amazed at how useful and necessary the command line was, and I was thrilled to see Neal Stephenson was the author of that book. (Pro tip: you can tell the commercial worth of an author by the size of his or her name on the cover. If it's bigger than the title of the book, the writer's a big deal. Literally.)

So I bought it, and then I read it in one sitting. You can do the same. In fact, I command that you do, if you haven't already, because (IMHO) it's the most classic book ever written about both the command line and Linux itself—a two-fer of the first order.

And I say this in full knowledge (having re-read the whole thing many times, which is easy, because it's short) that much of what it brings up and dwells on is stale in the extreme. The MacOS and the Be operating systems are long gone (and the Be computer was kind of dead on arrival), along with the Windows of that time. Today Apple's OS X is BSD at its core, while Microsoft produces lots of open-source code and contributes mightily to The Linux Foundation. Some of Neal's observations and complaints about computing and the culture of the time also have faded in relevance, although some remain enduringly right-on. (If you want to read a section-by-section critique of the thing, Garrett Birkel produced one in the mid-2000s with Neal's permission. But do read the book first.)

What's great about Command Line is how well it explains the original virtues of UNIX, and of Linux as the operating system making the most of it:

The file systems of Unix machines all have the same general structure. On your flimsy operating systems, you can create directories (folders) and give them names like Frodo or My Stuff and put them pretty much anywhere you like. But under Unix the highest level—the root—of the filesystem is always designated with the single character "/" and it always contains the same set of top-level directories:

Go to Full Article

Episode 22: Don't Panic, It's All About the Kernel

Tuesday 2nd of July 2019 10:06:16 PM
Your browser does not support the audio element. Episode 22: Don't Panic, It's All About the Kernel

Katherine Druckman talks to Linux Journal Editor at Large, Petros Koutoupis, about building your own kernel, kernel panics, and other projects.

Links mentioned:

Mageia 7 Now Available, NVIDIA Announces New "SUPER" Line with Revised Graphics Cards, Humble Store's DRM-Freedom Sale, Ubuntu MATE Coming to Raspberry Pi 4 and Backbox Linux Releases Version 6.0

Tuesday 2nd of July 2019 01:52:20 PM

News briefs for July 2, 2019.

Mageia 7 was released yesterday. This new version has "lots of new features, exciting updates, and new versions of your favorite programs, as well as support for very recent hardware." In addition, the Mageia team made an effort to enhance gaming in Mageia, so the game collection features many upgrades and additions. See the Release Notes and the full documentation for more information and installation options.

NVIDIA today announced its new "SUPER" line with revised RTX 2060 (starting at $399), RTX 2070 (starting at $499) and RTX 2080 (starting at $699) graphics cards, available later this month. See Phoronix for more details on the new GeForce RTX SUPER GPUs.

The Humble Store is having a DRM-Freedom sale. GamingOnLinux reports that all the included games have DRM-free builds available. Deals include Rogue Legacy at 80% off, Prison Architect at 75% off, Lovers in a Dangerous Spacetime at 60% off and much more.

Ubuntu MATE is coming to the Raspberry Pi 4. According to Forbes, lead developer Martin Wimpress revealed he is working on bringing MATE to the new RPi when he tweeted a photo of it with the caption "This should keep me occuPIed 4 a while". The Forbes post also notes that "While Raspbian 10 (based on Debian Buster) is a solid choice, Ubuntu MATE feels like a more modern desktop experience with less of a learning curve. It also includes office software, media players, the excellent Shotwell photo utility and the basic software most people need for general PC use."

Backbox Linux releases an update to version 6.0. Rogue Media News reports that the update of the ethical hacking and pen-testing distro includes a "new kernel, updated tools and some structural changes with a focus on maintaining stability and compatibility with Ubuntu 18.04 LTS". Go here to download the latest version.

News Mageia NVIDIA gaming Humble Store Ubuntu MATE Raspberry Pi Backbox Linux

Online Censorship Is Coming--Here's How to Stop It

Tuesday 2nd of July 2019 01:19:15 PM
by Glyn Moody

EU's upload filters are coming. Why and how the Open Source world must fight them.

A year ago, I warned about some terrible copyright legislation being drawn up in the EU that would have major adverse effects on the Open Source world. Its most problematic provision would force many for-profit sites operating in the EU to use algorithmic filters to block the upload of unauthorized material by users. As a result of an unprecedented campaign of misinformation, smears and outright lies, supporters managed to convince/trick enough Members of the European Parliament (MEPs) to vote in favour of the the new Copyright Directive, including the deeply flawed upload filters.

A number of changes were made from the original proposals that I discussed last year. Most important, "open source software development and sharing platforms" are explicitly excluded from the scope of the requirement to filter uploads. However, it would be naïve to assume that the Copyright Directive is now acceptable, and that free software will be unaffected.

Open source and the open internet have a symbiotic relationship—each has fed constantly into the other. The upload filters are a direct attack on the open internet, turning it into a permissioned online space. They will create a censorship system that past experience shows is bound to be abused by companies and governments alike to block legitimate material. It would be a mistake of the highest order for the Open Source community to shrug its shoulders and say: "we're okay—not our problem." The upload filters are most definitely the problem of everyone who cares about the open and healthy internet, and about freedom of speech. For example, the GitHub blog points out that false positives are likely to be a problem when upload filters are implemented—regardless of nominal "exemptions" for open source: "When a filter catches a false positive and dependencies disappear, this not only breaks projects—it cuts into software developers' rights as copyright holders too."

So, what can be done?

As the Pirate MEP Julia Reda emphasises in her post summarizing the multi-year battle to improve the text of the Copyright Directive: "My message to all who took part in this movement: Be proud of how far we came together! We've proven that organised citizens can make an impact—even if we didn't manage to kill the whole bill in the end. So don't despair!" Specifically:

Go to Full Article

The Command-Line Issue

Monday 1st of July 2019 03:00:00 PM
by Bryan Lunduke

Summer. 1980-something. An elementary-school-attending, Knight Rider-T-Shirt-wearing version of myself slowly rolls out of bed and shuffles to the living room. There, nestled between an imposingly large potted plant and an over-stocked knick-knack shelf, rested a beautifully gray, metallic case powered by an Intel 80286 processor—with a glorious, 16-color EGA monitor resting atop.

This was to be my primary resting place for the remainder of the day: in front of the family computer.

That PC had no graphical user interface to speak of—no X Window System, no Microsoft Windows, no Macintosh Finder. There was just a simple command line—in this case, MS-DOS. (This was long before Linux became a thing.) Every task I wished to perform—executing a game, moving files—required me to type the commands in via a satisfyingly loud, clicky keyboard. No, "required" isn't the right word here. Using the computer was a joy. "Allowed" is the right word. I was allowed to enjoy typing those commands in. I never once resented that my computer needed to be interacted with via a keyboard. That is, after all, what computers do. That's what they're for—you type in commands, and the computer executes them for you, often with a "beep".

For a kid, this was empowering—taking my rudimentary understanding of language (aided, at first, by a handy DOS command cheat sheet) and weaving together strings of words that commanded the computer to do my bidding. It was like organizing runes to enact an ancient spell. It was magic. And I was a wizard. Did I miss not being able to "double click" or "drag and drop"? Of course not. I'd seen some such, mouse-driven user interfaces (like the early Macintoshes) but—from my vantage—that wasn't how computers really worked. I viewed such things as cool-looking, but not necessary. Computers use words. Powerful, magical words.

But this isn't 1980-something. In fact, it's barely 2010-something. (Did anyone else just realize that it's almost 2020?) For better or worse, how people use—and view—computers has changed dramatically since the days of Knight Rider. Modern operating systems are, often, belittled if they require users to interact with the machine via a command line. The graphical user interface is king. Which is, perhaps, the inevitable evolution of how we all interact with our computers.

Yet the value of the command line (or terminal, shell and so on) is still there. For many, it makes using computers more accessible. For others, it provides streamlined workflows that a mouse or touch-driven interface simply can't compete with. And, for others still, the blinking cursor provides a bit of nostalgic joy—or an aesthetically simple, and distraction free, environment.

This issue of Linux Journal celebrates the cursor—that wonderful blinking underscore and all the potential that it holds.

Go to Full Article

Linux Used More than Windows on Azure, Debian Asks for Help Testing Buster, Red Hat Announces Packit-as-a-Service, KaOS 2019.07 Released and Kernel 5.2-rc7 Is Out

Monday 1st of July 2019 01:45:48 PM

News briefs for July 1, 2019.

Linux is now used more than Windows on Azure. According to ZDNet, Microsoft Linux kernel developer Sasha Levin revealed that "the Linux usage on our cloud has surpassed Windows" when requesting that Microsoft be allowed to join a Linux security developer list. The ZDNet piece concludes with "There are now at least eight Linux distros available on Azure. And that's not counting Microsoft's own Azure Sphere. This is a software and hardware stack designed to secure edge devices, which includes what Microsoft president Brad Smith declared 'a custom Linux kernel'. It's now a Linux world—even at Microsoft headquarters in Redmond, Washington."

Debian 10.0 "Buster" release images are available for testing. Phoronix reports that with the 10.0 release coming next weekend, the "near-final images" are uploaded and folks are encouraged to test them: "There is a call for 'smoke testing' of these Debian 10.0 images for AMD64 (x86_64), i386, MIPS, MIPSEL, MIPS64EL, PPC64EL, and s390x. The Debian Developers are aiming to ensure there are no release critical bugs. In particular they are looking for more testing of their live images on bare metal PCs in both BIOS (CSM) and UEFI boot modes." Read the "call for help" here.

Red Hat this morning announced the availability of Packit-as-a-Service, a GitHub app that uses the Packit project: "Using the Packit service in your upstream projects helps you continuously ensure that your projects work in Fedora OS. Just add one config file to your repository, along with the RPM spec file and you're almost there. We have started publishing docs for the service over here."

KaOS 2019.07 was released today. This rolling distro includes the latest packages for the Plasma Desktop (Frameworks 5.59.0, Plasma 5.16.2 and KDE Applications 19.04.2), all built on Qt 5.13.0. See the Download Page for installation instructions.

Linux 5.2-rc7 is out. Linus Torvalds writes (from "in the middle of nowhere on a boat"), "It's been _fairly_ calm. Would I have hoped for even calmer with my crappy internet? Sure. But hey, it's a lot smaller than rc6 was and I'm not really complaining. All small and fairly uninteresting. Arch updates, networking, core kernel, filesystems, misc drivers. Nothing stands out - just read the appended shortlog. It's small enough to be easy to just scroll through."

News Windows Microsoft Azure Debian Red Hat Packit-as-a-Service GitHub KaOS kernel KDE Desktop

More in Tux Machines

Samsung discontinues ‘Linux on DeX’ program

  • Samsung discontinues ‘Linux on DeX’ program, removing support w/ Android 10

    Late last year, Samsung and Canonical partnered on an app that allowed select Galaxy phones to run a full Linux desktop on top of Android. Less than a year later, Samsung has announced that they’re discontinuing the Linux on DeX program, coinciding with the update to Android 10. One of the sci-fi-style dreams that many of us have had since the onset of smartphones is the idea of plugging your phone into a desktop-size monitor to get a desktop-style experience. Through the years, many have attempted it in earnest, and the latest offering from Samsung brought an interesting approach.

  • Samsung Calls It Quits on the ‘Linux on DeX’ Project

    Samsung DeX, if you have heard of it, allows the users to turn their Galaxy phones into desktop PCs simply by connecting a monitor and other peripherals. The company made DeX more welcoming and useful for Galaxy flagship users by partnering with Canonical earlier last year. It made it possible for users to run a full Linux desktop instance on its DeX-supported flagship phones. This was an amazing feature for developers and users who didn’t really like carrying a laptop with them. They could rely on their Galaxy flagship (including the Galaxy S and Note-series) for a desktop-like experience, running Ubuntu on the move. However, the response to Linux on DeX seems to have been lackluster and Samsung has decided to shutter this project.

  • Samsung is discontinuing Linux support on Dex

    Samsung goes on to explain that starting with its Android 10 beta ROMS, already rolling out on certain devices, Linux support will be removed from Dex altogether. This does make us wonder if, perhaps, the third-party OS emulation setup Samsung was employing to get Linux to work in the first place somehow breaks certain rules or security policies Google implemented with the latest Android version. Regardless of whether or not this is the case, if you are currently using Linux on Dex, you definitely want to start keeping regular backups of your data. Since, given current developments even staying on Android 9 and not updating your phone's Android OS still might not be a sure-fire way to keep the feature running.

Android Leftovers

To space and beyond with open source

The Cambridge Dictionary defines curiosity as "an eager wish to know or learn about something." It's curiosity that fuels our drive to acquire knowledge about outer space, but what drives our curiosity, our "eager wish," in the first place? I believe that our curiosity is driven by the desire to escape the unpleasant feeling of uncertainty that is triggered by acknowledging our lack of knowledge. The intrinsic reward that comes from escaping uncertainty pushes us to find a correct (or at least a less wrong) answer to whatever question is at hand. If we want space discovery to advance at a faster pace, we need more people to become aware of the rewards that are waiting for them when they make the effort and discover answers for their questions about the universe. Space discovery is admittedly not an easy task, because finding correct answers requires following rigorous methods on a long-term scale. Luckily, open source initiatives are emerging that make it easier for people to get started exploring and enjoying the beauty of outer space. Read more

Announcing the release of LTTng 2.11

We're happy to announce the release of LTTng 2.11 "Lafontaine". This is a combined release announcement for the 2.11.0 - "Lafontaine" release of the LTTng Tools, LTTng UST, and LTTng modules projects. This release is named after a modern Saison beer from Montréal's Oshlag microbrewery. It is a refreshing, zesty, rice beer with hints of fruit and spices. Some even say it makes for a great Somaek when mixed with Chamisul Soju, not that we've tried! Lafontaine is also a tongue-in-cheek reference to a water leak that affected EfficiOS's offices during the development of this release. Read more Also: LTTng 2.11.0 "Lafontaine" released