Monday, 16 July 2018

Chromium OS for Raspberry Pi SBCs Is Making a Comeback Soon, Better Than Ever

Chromium OS for Raspberry Pi SBCs Is Making a Comeback Soon, Better Than Ever

Jul 13, 2018, 14:00 (0 Talkback[s]) (Other stories by Marius Nestor)

Now that Flint OS is "gone," and there's still no feasible way of getting pure Chromium OS running on your tiny single-board computer, Keith Callahan announced today that he is reviving the Chromium OS for SBCs project in an attempt to offer the community an easy way of installing the open-source Chromium OS operating system on Raspberry Pi SBCs. Callahan told Softpedia that he is currently working hard on the new Chromium OS for SBCs 1.0 (Codename Weinreich) release, which should hit the streets near the Christmas holidays, with initial support for Raspberry Pi 2, Raspberry Pi 3 Model B, and the new Raspberry Pi 3 Model B+ boards.

Complete Story

Read the full article here by Linux Today

Guido van Rossum retires as Python's BDFL 😱

[python-committers] Transfer of power

Guido van Rossum guido at
Thu Jul 12 10:57:35 EDT 2018
Now that PEP 572 is done, I don't ever want to have to fight so hard for a
PEP and find that so many people despise my decisions.

I would like to remove myself entirely from the decision process. I'll
still be there for a while as an ordinary core dev, and I'll still be
available to mentor people -- possibly more available. But I'm basically
giving myself a permanent vacation from being BDFL, and you all will be on
your own.

After all that's eventually going to happen regardless -- there's still
that bus lurking around the corner, and I'm not getting younger... (I'll
spare you the list of medical issues.)

I am not going to appoint a successor.

So what are you all going to do? Create a democracy? Anarchy? A
dictatorship? A federation?

I'm not worried about the day to day decisions in the issue tracker or on
GitHub. Very rarely I get asked for an opinion, and usually it's not
actually important. So this can just be dealt with as it has always been.

The decisions that most matter are probably
- How are PEPs decided
- How are new core devs inducted

We may be able to write up processes for these things as PEPs (maybe those
PEPs will form a kind of constitution). But here's the catch. I'm going to
try and let you all (the current committers) figure it out for yourselves.

Note that there's still the CoC -- if you don't like that document your
only option might be to leave this group voluntarily. Perhaps there are
issues to decide like when should someone be kicked out (this could be
banning people from python-dev or python-ideas too, since those are also
covered by the CoC).

Finally. A reminder that the archives of this list are public ( although membership
is closed (limited to core devs).

I'll still be here, but I'm trying to let you all figure something out for
yourselves. I'm tired, and need a very long break.

--Guido van Rossum (
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the python-committers mailing list

Read the full article here by Changelog

Live Twitch • Gros défis sur The Crew 2

Retour sur The Crew 2 ce soir, à la demande générale. la suite d'un mouvement initié par l'équipe de modération de la chaîne, cette soirée sera placée sous le signe du challenge, un nouveau signe zodiacal de notre invention... [Tout lire]

Read the full article here by Le comptoir du hardware

Monday, 2 July 2018

Install And Play Overwatch With Lutris On Ubuntu 18.04

Linuxconfig: Overwatch is one of the most popular PC games right now. It has a thriving esports scene and a community of millions playing it regularly worldwide.

Read the full article here by Linux Today

Friday, 29 June 2018

MindForger - More Than A Notebook and Markdown IDE

MindForger - More Than A Notebook and Markdown IDE

Jun 29, 2018, 06:00 (0 Talkback[s]) (Other stories by FossMint)

MindForger is a modern, free, open-source, privacy-focused and performance-driven Markdown IDE for creating, editing, and managing all types of notes.

Complete Story

Read the full article here by Linux Today

Thursday, 28 June 2018

Google Doubles Down on Linux and Open Source

Steven J. Vaughan-Nichols, writing for ZDNet: Google couldn't exist without Linux and open-source software. While you may not think of Google as a Linux company in the same way as you do Canonical, Red Hat, or SUSE, it wouldn't be the search and advertising giant it is today without Linux. So, it makes sense that Google is moving up from its Silver membership in The Linux Foundation, to the Platinum level. With this jump in status, Google gets a seat on the Foundation's board of directors. This position will be filled by Sarah Novotny, the head of open source strategy for Google Cloud Platform. Earlier this week, Chinese tech giant Tencent joined the Linux Foundation as a platinum member.
Share on Google+

Read more of this story at Slashdot.

Read the full article here by Slashdot

Wednesday, 27 June 2018

Google Opens Its Human-Sounding Duplex AI To Public Testing

Google is moving ahead with Duplex, the stunningly human-sounding artificial intelligence software behind its new automated system that places phone calls on your behalf with a natural-sounding voice instead of a robotic one. From a report: The search giant said Wednesday it's beginning public testing of the software, which debuted in May and which is designed to make calls to businesses and book appointments. Duplex instantly raised questions over the ethics and privacy implications of using an AI assistant to hold lifelike conversations for you. Google says its plan is to start its public trial with a small group of "trusted testers" and businesses that have opted into receiving calls from Duplex. Over the "coming weeks," the software will only call businesses to confirm business and holiday hours, such as open and close times for the Fourth of July. People will be able to start booking reservations at restaurants and hair salons starting "later this summer."
Share on Google+

Read more of this story at Slashdot.

Read the full article here by Slashdot

Saturday, 23 June 2018

Leclerc: “L’ottavo tempo è magico, non ci posso credere”

Grande prestazione da parte del monegasco al volante della Sauber, con il pilota della FDA in grado di centrare per la prima volta in carriera il Q3.

Read the full article here by

Wednesday, 20 June 2018

AMD trolle joliement Intel et son 8086K

Test • Intel Z370 / Core i7-8700K / i5-8400 / i3-8350K

Coffee Lake, l'anti Ryzen d'Intel ?   Durant les années 2000 et consécutivement à l'échec de Netburst, Intel a mis en place la stratégie du Tick Tock, co...

Read the full article here by Le comptoir du hardware

Microsoft ports Windows 10, Linux to homegrown CPU design


Microsoft has ported Windows 10 and Linux to E2, its homegrown processor architecture it has spent years working on mostly in secret.

As well as the two operating systems, the US giant's researchers say they have also ported Busybox and FreeRTOS, plus a collection of toolkits for developing and building applications for the processor: the standard C/C++ and .NET Core runtime libraries, the Windows kernel debugger, Visual C++ 2017's command line tools, and .NET's just-in-time compiler RyuJIT.

Microsoft has also ported the widely used LLVM C/C++ compiler and debugger, and related C/C++ runtime libraries. The team wanted to demonstrate that programmers do not need to rewrite their software for the experimental chipset, and that instead programs just need to be recompiled - then they are ready to roll on the new technology.

I had no idea Microsoft was working on its own instruction set - even if only for research purposes. The Register has some more information on what E2 is like.

The Register understands from people familiar with its development that prototype E2 processors exist in the form of FPGAs - chips with reprogrammable circuitry that are typically used during the development of chips. For example, a dual-core implementation on Xilinx FPGAs exists, clocked at 50MHz. The team has also developed a cycle-accurate simulator capable of booting Windows and Linux, and running applications.

Qualcomm researchers were evaluating two EDGE chip designs with Microsoft: a small R0 core, and an R1 core running up to 2GHz fabricated using a 10nm process. The project, we must stress, is very much a work in progress.

It seems to be a radical departure from the norm, and I'm very interested to see where this will lead.

Read the full article here by OSNews

Please Oliver

Tuesday, 19 June 2018

Monday, 18 June 2018

EXT4 fscrypt vs. eCryptfs vs. LUKS dm-crypt Benchmarks

Given the recent advancements of the EXT4 file-system with its native file-system encryption support provided by the fscrypt framework, here are benchmarks comparing the performance of an EXT4 file-system with no encryption, fscrypt-based encryption, eCryptfs-based encryption, and a LUKS dm-crypt encrypted volume.

For those wondering how these different file-system encryption options compare for performance, I ran some fresh benchmarks using a Linux 4.18 development kernel as of 14 June from the Linux Git tree. The options tested were EXT4, fscrypt, eCryptfs, and LUKS dm-crypt encryption with the EXT4 file-system and tested with the defaults unless otherwise noted. A Toshiba TR150 SATA 3.0 SSD was used as the drive under test for all of the benchmarking. Ubuntu 18.04 LTS was the basis for this benchmarking aside from the Linux kernel upgrade.

All of thes Linux file-system encryption benchmarks were carried out in a standardized and fully reproducible manner using the open-source Phoronix Test Suite benchmarking software.

Read the full article here by Phoronix

Tuesday, 12 June 2018

Drone That Can Follow You Around Obstacles

Skydio R1 review..(Read...)

Read the full article here by Likecool

F2FS File-System Gets Discard Improvements, Nobarrier Fsync Mode For Linux 4.18

Flash-Friendly File-System (F2FS) maintainer Jaegeuk Kim has submitted the file-system updates intended for the Linux 4.18 kernel.

This flash storage optimized file-system has improvements around its discard/fstrim support, including the splitting of large discard commands for better responsiveness. There is also a new


mount option available for reducing the number of cache flushes.

F2FS for Linux 4.18 also has improved sanity checks, various code clean-ups, and at least six known bug fixes.

The complete list of F2FS file-system changes for Linux 4.18 can be found via

the kernel mailing list


Read the full article here by Phoronix

Monday, 11 June 2018

How to Android without Google


This guide shows how to install LineageOS without GApps with the help of signature spoofing and microG, so that you can have Push Notifications, Location Services and the like, without needing to have Google Play Services installed (without Google-anything for that matter).

It was made possible by the hard work of creators, maintainers and community around LineageOS, microG, XPosedFramework, F-Droid, Yalp Store and many others.

Exactly what it says on the tin.

Read the full article here by OSNews

Sunday, 10 June 2018

Linux Solutions: Snappy, Flatpak, and AppImage

It wasn't all that long ago the idea of binary packages were seen as salvation from having to compile software packages for one's Linux system.

In 2018, we've jumped ahead even further, with distro independent package installation solutions. In this article, we're going to look into three rising stars in this area: Snappy, Flatpak and AppImage.

AppImage is a software disk image that just works

I'm a huge fan of AppImage as you simply make the individual application you wish to run executable, then double click it. AppImages are just that simple. According to their website, the idea is that you get the software directly from the author of said program. Using the AppImage format, installing an application can feel similar to how one might do it with Windows.

The advantage of running an AppImage is that there is no need for sudo, root or even the need to be bothered with system dependencies. You're basically mounting a disk image, similar to how one might mount disk images in OS X.

Perhaps the biggest advantage to running AppImages is that you're running an application that can be removed by simply deleting a single file. This single file/disk image approach is both great and a hardship depending on how you look at it. AppImages are great in that they're easily distributed and simple to run.

The downside of AppImages are that even when you get the software directly from the author's website, you still don't really know if the application has been tampered with. This problem of trusting software is best demonstrated with what happened to OS X users and the application known as Transmission. This application allowed ransomware to infect those individuals who ran the application on their Macs.

So as much as I like AppImages, I take issue with the bold print statement that AppImages are to be trusted absolutely. Fact is, they're just disk images and instead we need to trust the distributor of each individual AppImage. Thankfully if one chooses to run an AppImage within a sandbox, this prevents things from getting out of hand should the downloaded AppImage become exploited on the source website.

Flatpak provides isolated runtimes

Updates and applications installed by Flatpak are handled by individual runtimes. The idea is that this provides more streamlined package handling than running typical Linux package updates. Now here's where Flatpak shines - it's designed for desktop Linux distros. So the applications that are distributed with Flatpaks are going to be designed for desktop Linux users. This is a characteristic also found with AppImages, however Flatpaks differ in that they allow for individual application updates.

Flatpaks share similarities with Ubuntu PPAs in that they're using individual repositories for application installation and updates. I'll be first to admit that I honestly don't love this element of Flatpaks as it's time consuming to have to chase down individual repos. On the positive side, however, it does provide a better system for installation/updates as it's distro independent.

Another consideration is that installing the framework for Flatpaks requires the installation of needed components to make the Flatpak available software installable. The irony takes place with distros such as Ubuntu whereas you must add an Ubuntu PPA for the Flatpak framework. In short, install a PPA repository to install a framework to install Flatpak repositories. While it's not difficult to do this, it is a bit redundant.

The benefit of running Flatpak installed applications is that you can run the latest software on any distro you choose. Additionally, to curb the headache of seeking out individual Flatpak repos, Flathub's Application section makes finding software easy.

Flathub provides the ability locate software in one location, even though historically Flatpaks aren't located in a singular location. It's actually a great idea and it makes using Flatpaks a lot more appealing. Perhaps most importantly, Flathub's software categories are packed full of tons of software to choose from.

To repeat an item from above: Like AppImages, Flatpaks are designed for Linux desktops. This is an important consideration as we roll into the next section of this article.

Snap Packages are a compressed file system

Snap packages are a packaging concept created by Canonical and designed for Linux and IoT (internet of things). When you arrive at the Snapcraft website the first impression you find yourself with is that Snaps put the developer ahead of the end user. I don't mean that as a negative statement, however the Snaps web presence backs up my statement completely. The two buttons on the front page are "Build your first snap" and "Get started using Github."

Both button links mentioned above assume you're a developer. This differs substantially from the front page of the Flatpak. The Flatpak front page is dedicated to getting Flatpak software onto the PCs of end users. Snaps only offers end user solutions if you look to the very top navigation bar and click on store. Once you click the store link, you're presented with available Snaps to install onto target PCs and servers.

Snaps also share similarities with AppImage in that you're mounting a software image vs installing software. Another benefit with Snaps is being able to roll back to an earlier version of software. Additionally, updates are made easy since Snaps share a single repository.

The biggest downside some people find with Snaps is the fact it provides a centralized packaging format that Canonical controls. Granted, Snaps are available across multiple distros, but the control of available Snaps remains in a single location. It's also worth noting that notable open and closed source software is welcome in Snap's repository.

One last important point with Snaps is that they're not limited to the Linux desktop as I mentioned previously. They're also designed to provide packaging solutions for IoT (internet of things). This is the biggest difference between Snaps and both Flatpak and AppImage. Snaps are heavily focused on IoT with Linux being an added bonus.

Which packaging type is best for Linux?

After looking at the differences and advantages of each packaging type mentioned above, we're left wondering which one is best. In terms of simplicity, I'd argue that AppImage wins this one. But if you want to be able to update your software using one of these packaging formats, then Flatpak or Snaps make more sense.

One approach might be to try out each of them and see which packaging type has the user experience and the software titles you're looking for.

What say you? Do you have a preference? If so, what is your rationale as to your choice of software packaging. Hit the Comments, let's hear your perspective.

Read the full article here by