Language Selection

English French German Italian Portuguese Spanish

Interviews

Interview – NXP Linux BSP and Timesys Vigiles Maintenance Service & Security Updates

Filed under
Development
Linux
Interviews

Answer: The kernel strategy for NXP’s i.MX family BSPs closely follows the annual cadence of kernel.org’s LTS kernel selection. As soon as kernel.org establishes the next official LTS kernel version, NXP transitions our internal development to that particular kernel. However, the migration of the kernel is only one aspect of our next major release. There may be a number of associated updates to be included, such as a new version to Yocto, updates to U-Boot, and many other package changes we integrate into the Yocto release specific to the i.MX BSP. These factors, plus our rigorous testing process create an inevitable delay between the community version of the latest LTS kernel release and NXP’s i.MX board support package (BSP) based on that same kernel.

We must also consider a number of other factors that come into play between our planned cadence of Linux LTS kernel updates. NXP may introduce new products, or there may be updates to various packages, and of course, there are issue resolutions (including LTS minor version updates) to be considered. Our engineering team must balance all these factors while maintaining consistent quality standards for the entire i.MX product family being supported by each BSP release.

Read more

PCLinuxOS Interview and Screenshots

Filed under
PCLOS
Interviews

Why and when did you start using Linux?
2005. The security issues with Windows XP were really blowing up at the time, so when I ordered a new computer for school I made sure to do so with a second drive planning on giving 'Nix a try. I started off on Ubuntu on that machine, and when I got a laptop a couple of years later I wanted to try something different and ran through a couple distros before settling on PCLinuxOS. It's become my everyday driver, and I now use Linux most of the time on my own machines simply because I like it better. I'm currently running Debian 10 and PCLinuxOS.

What specific equipment do currently use with PCLinuxOS?
This desktop has an AMD Ryzen 7 3800X, Radeon 580X graphics, Asus X570 mobo, and 64GB of G-Skill Ripjaws RAM. I also have a Nektar Impact GX61 MIDI controller keyboard and Focusrite Scarlett 4i4 audio interface connected to this machine since it's my production rig. I also have PCLinuxOS installed on a hand-me-down laptop (Lenovo Z580) that runs only Linux.

Do you feel that your use of Linux influences the reactions you receive from your computer peers or family? If so, how?
I'm not sure how much using Linux has to do with it, but I've certainly become the tech support for my family... Outside of a few die-hards, I find that folks generally aren't too hung up on what OS you use. I use Windows, MacOS, and Linux daily and think each has its place, though I'd likely never use Windows at all on my own boxes if WINE support for games and a few audio programs was better.

Read more

Also: [PCLinuxOS] Screenshot Showcase

Audiocasts/Shows: Ubuntu, Manjaro, Python Bytes and GNU World Order

Filed under
Development
GNU
Linux
Interviews

Interview with Albert Weand

Filed under
KDE
Interviews

A couple of years ago, I started to gain interest in GNU/Linux and even considered using it as my main OS. One of my priorities was to find a good painting application compatible with the system. I tried MyPaint and Gimp, but Krita was definitely the best option.

I really like the user interface, it’s very flexible. I like to keep things simple and just focus on the artwork. The shortcuts to navigate around the canvas are great, they feel very natural. There’s no need to change tools in order to zoom in, zoom out or move around the canvas. I also like the default brushes, they feel organic and the textures help to simulate real brushes in traditional painting.

Read more

Interview with Clément Mona

Filed under
KDE
Interviews

I wanted to try someting different and a friend of mine showed me Krita in 2017.

I loved how intuitive Krita is, I handled the program very fast, more over my Wacom tablet worked perfectly on it, and that was not the case with oher applications at this time.

I love how fast I can paint with Krita. Also, the brush customisation is very nice and complete.

Read more

In Free Software, the Community is the Most Important Ingredient: Jerry Bezencon of Linux Lite [Interview]

Filed under
Interviews

Jerry Bezencon, the creator of Linux Lite project, shares some interesting details about this popular lightweight Linux distribution.
Read more

In Free Software, the Community is the Most Important Ingredient: Jerry Bezencon of Linux Lite [Interview]

Filed under
GNU
Linux
Interviews

Linux Lite was started in 2012 for 3 important reasons. One, I wanted to dispel myths that a Linux based operating system was hard to use. Two, at that time, there was a shortage of simple, intuitive desktop experiences on Linux that offered long-term support. Three, I had used Linux for over 10 years before starting Linux Lite.

I felt I needed to give back to a community that had given so much to me. A community that taught me that by sharing code and knowledge, one could have a dramatically positive impact over peoples computing experiences.

Read more

Debian Edu interview: Yvan Masson

Filed under
Interviews
Debian

It is free software! Built on Debian, I am sure that users are not spied upon, and that it can run on low end hardware. This last point is very important, because we really need to improve "green IT". I do not know enough about Skolelinux / Debian Edu to tell how it is better than another free software solution, but what I like is the "all in one" solution: everything has been thought of and prepared to ease installation and usage.

I like Free Software because I hate using something that I can not understand. I do not say that I can understand everything nor that I want to understand everything, but knowing that someone / some company intentionally prevents me from understanding how things work is really unacceptable to me.

Secondly, and more importantly, free software is a requirement to prevent abuses regarding human rights and environmental care. Humanity can not rely on tools that are in the hands of small group of people.

Read more

Interview with Jefferson Nascimento

Filed under
KDE
Interviews

I use Linux as a main OS from time to time, in 2016 I was searching open source alternatives for drawing, back in the days I was using MyPaint, I never liked Gimp for drawing, so I used an “alternative” copy of other software, but not Photoshop, I never liked to draw with Photoshop. Then I found this piece of software that looked like a good alternative and tried. It fit all my expectations.

Tough one. Can I say David Revoy? or Wolthera? I learned so much from those two. Ok, enough kidding, I love the layer management. I don’t have to use the mouse to quickly rename and organize everything, I worked in an office where I had to use Photoshop, and man, oh man, I suddenly realized why every artist ever who uses Photoshop doesn’t rename layers, it’s just terrible.

Read more

Paul Cormier brings an engineer’s eye to top role at Red Hat

Filed under
Red Hat
Interviews

Red Hat Inc. opens the virtual doors of its annual Red Hat Summit this week amid a major leadership shift at both the open-source giant and its parent, IBM Corp.

Less than three weeks ago Arvind Krishna took over as chief executive of IBM, becoming the first engineer to hold the position in the company’s 106-year history. At the same time, Jim Whitehurst ascended to the role of IBM president and Paul Cormier (pictured at the 2018 summit) assumed the CEO spot at Red Hat.

Like Krishna, Cormier is the first engineer to lead his company. That’s appropriate, he said in an interview with SiliconANGLE. The technology landscape is becoming more complex and there’s more at stake when customers make decisions.

“There’s so much more fear, uncertainty and doubt out there that it takes more technically savvy people to wade through it,” he said. “It’s a much more complex sale now than it used to be.”

Read more

Syndicate content

More in Tux Machines

NanoPi NEO3 Headless SBC Launched for $20 and up

Last month, we found out FriendlyELEC was working on NanoPi NEO3, a tiny SBC powered by Rockchip RK3328 processor and made for headless applications and networked storage thanks to Gigabit Ethernet and USB 3.0 ports, as well as a 26-pin GPIO header. At the time, the board was still been finalized, but the company has now started to take orders for $20 and up depending on options which include a cute white enclosure... [...] The Wiki has been updated as well, and the company provides both Ubuntu Core 18.04 based FriendlyCore, and OpenWrt based FriendlyWrt operating systems for the board with both relying on Linux 5.4.12 kernel. I’d also expect Armbian to eventually provide Ubuntu 20.04 and Debian 10 images. Read more

Moving (parts of) the Cling REPL in Clang

Motivation
===

Over the last decade we have developed an interactive, interpretative 
C++ (aka REPL) as part of the high-energy physics (HEP) data analysis 
project -- ROOT [1-2]. We invested a significant  effort to replace the 
CINT C++ interpreter with a newly implemented REPL based on llvm -- 
cling [3]. The cling infrastructure is a core component of the data 
analysis framework of ROOT and runs in production for approximately 5 
years.

Cling is also  a standalone tool, which has a growing community outside 
of our field. Cling’s user community includes users in finance, biology 
and in a few companies with proprietary software. For example, there is 
a xeus-cling jupyter kernel [4]. One of the major challenges we face to 
foster that community is  our cling-related patches in llvm and clang 
forks. The benefits of using the LLVM community standards for code 
reviews, release cycles and integration has been mentioned a number of 
times by our "external" users.

Last year we were awarded an NSF grant to improve cling's sustainability 
and make it a standalone tool. We thank the LLVM Foundation Board for 
supporting us with a non-binding letter of collaboration which was 
essential for getting this grant.


Background
===

Cling is a C++ interpreter built on top of clang and llvm. In a 
nutshell, it uses clang's incremental compilation facilities to process 
code chunk-by-chunk by assuming an ever-growing translation unit [5]. 
Then code is lowered into llvm IR and run by the llvm jit. Cling has 
implemented some language "extensions" such as execution statements on 
the global scope and error recovery. Cling is in the core of HEP -- it 
is heavily used during data analysis of exabytes of particle physics 
data coming from the Large Hadron Collider (LHC) and other particle 
physics experiments.


Plans
===

The project foresees three main directions -- move parts of cling 
upstream along with the clang and llvm features that enable them; extend 
and generalize the language interoperability layer around cling; and 
extend and generalize the OpenCL/CUDA support in cling. We are at the 
early stages of the project and this email intends to be an RFC for the 
first part -- upstreaming parts of cling. Please do share your thoughts 
on the rest, too.


Moving Parts of Cling Upstream
---

Over the years we have slowly moved some patches upstream. However we 
still have around 100 patches in the clang fork. Most of them are in the 
context of extending the incremental compilation support for clang. The 
incremental compilation poses some challenges in the clang 
infrastructure. For example, we need to tune CodeGen to work with 
multiple llvm::Module instances, and finalize per each 
end-of-translation unit (we have multiple of them). Other changes 
include small adjustments in the FileManager's caching mechanism, and 
bug fixes in the SourceManager (code which can be reached mostly from 
within our setup). One conclusion we can draw from our research is that 
the clang infrastructure fits amazingly well to something which was not 
its main use case. The grand total of our diffs against clang-9 is: `62 
files changed, 1294 insertions(+), 231 deletions(-)`. Cling is currently 
being upgraded from llvm-5 to llvm-9.

A major weakness of cling's infrastructure is that it does not work with 
the clang Action infrastructure due to the lack of an 
IncrementalAction.  A possible way forward would be to implement a 
clang::IncrementalAction as a starting point. This way we should be able 
to reduce the amount of setup necessary to use the incremental 
infrastructure in clang. However, this will be a bit of a testing 
challenge -- cling lives downstream and some of the new code may be 
impossible to pick straight away and use. Building a mainline example 
tool such as clang-repl which gives us a way to test that incremental 
case or repurpose the already existing clang-interpreter may  be able to 
address the issue. The major risk of the task is avoiding code in the 
clang mainline which is untested by its HEP production environment.
There are several other types of patches to the ROOT fork of Clang, 
including ones  in the context of performance,towards  C++ modules 
support (D41416), and storage (does not have a patch yet but has an open 
projects entry and somebody working on it). These patches can be 
considered in parallel independently on the rest.

Extend and Generalize the Language Interoperability Layer Around Cling
---

HEP has extensive experience with on-demand python interoperability 
using cppyy[6], which is built around the type information provided by 
cling. Unlike tools with custom parsers such as swig and sip and tools 
built on top of C-APIs such as boost.python and pybind11, cling can 
provide information about memory management patterns (eg refcounting) 
and instantiate templates on the fly.We feel that functionality may not 
be of general interest to the llvm community but we will prepare another 
RFC and send it here later on to gather feedback.


Extend and Generalize the OpenCL/CUDA Support in Cling
---

Cling can incrementally compile CUDA code [7-8] allowing easier set up 
and enabling some interesting use cases. There are a number of planned 
improvements including talking to HIP [9] and SYCL to support more 
hardware architectures.



The primary focus of our work is to upstreaming functionality required 
to build an incremental compiler and rework cling build against vanilla 
clang and llvm. The last two points are to give the scope of the work 
which we will be doing the next 2-3 years. We will send here RFCs for 
both of them to trigger technical discussion if there is interest in 
pursuing this direction.


Collaboration
===

Open source development nowadays relies on reviewers. LLVM is no 
different and we will probably disturb a good number of people in the 
community ;)We would like to invite anybody interested in joining our 
incremental C++ activities to our open every second week calls. 
Announcements will be done via google group: compiler-research-announce 
(https://groups.google.com/g/compiler-research-announce).



Many thanks!


David & Vassil

Read more Also: Cling C++ Interpreter Looking To Upstream More Code Into LLVM

This week in KDE: New features galore!

Tons and tons of awesome new features and UI polish landed this week, alongside an equally weighty ton of important bugfixes. Read more

Elive 3.8.14 beta released

The Elive Team is proud to announce the release of the beta version 3.8.14 This new version includes: Kernel updated to 5.6.14 retrowave special theme themes, designs, icons improvements and more customizations included bootup with a much more friendly graphical menu, it now remembers your last selected OS, all the options are in the same menu instead of submenus, disabled useless recovery options, improved resolution, fixed wallpaper issue on encrypted installations SWAP space is much more performant now, feedbacks welcome Read more