Language Selection

English French German Italian Portuguese Spanish

Programming: ‘Hack’, Berkeley Packet Filter, Python and More

Filed under
  • Hack Laptop Brings Linux to Desktop for Everyone Learning to Code

    If you have a pre-teen interested in coding, $300 in loose cash and $10/month to spend on a subscription service, the new ‘Hack’ computer might be what you’re looking for.

    Most learn-to-code devices are geared toward a younger crowd, often disguised as toys. The Hack Laptop is simply an ASUS computer. It has a 1920×1080 HD display, 64GB storage, 4GB RAM, and an Intel N5000 processor. It runs Endless OS, which is a version of Linux, and that’s where the real magic begins.

    Instead of some learn-as-you-go app, the Hack Laptop is itself a teaching tool. With that $10/month subscription, students get new challenges that entice them to hack the device itself. The challenges invite them to pick apart code, and a feature dubbed ‘flip to hack’ reverts to the user interface so students can see their user-facing changes in real-time.

  • How to Make Linux Microservice-aware with Cilium and eBPF

    My name is Thomas Graf. Before I start, I would like to know a little bit about what your interests are; who is involved with the upside of things platform, kind of less the dev side, just pure platform? Who is really into kind of development and Dev-ops? So, first of all, I've been asked to stay behind a podium, so whenever you see me walk in front just give me a sign, and push me back. Apparently, the video camera is not able to catch me if I've walked forward too much.

    So what I'm here to talk about is, is BPF, Berkeley Packet Filter, and how BPF can be used to turn and Linux into what we call a Micro Service Operating System. What makes me qualified to talk about this? So I've spent about 15 years working on the Linux kernel. About 10 years of that, I've mostly focused on working and security from a subsystem perspective. So I helped write potentially the biggest monolith ever, 12 million lines of source code by now. I worked on all of the networking subsystem pretty much, a lot of security user space stuff, Netlink, prior to and so on and so on.

  • Clean Architectures in Python: the book

    I'm excited to announce that the success of the post on clean architectures encouraged me to expand the subject and to write a book that I titled "Clean Architectures in Python. A practical approach to better software design".

    The book contains a complete introduction to TDD and clean architectures, two topics that I believe are strictly interconnected. The book is 170 pages long and it is complete, at least for a first edition, but I am already planning to add content that could not fit in this release for several reasons (mostly because still unclear in my mind).

  • pinp 0.0.7: More small YAML options

    One new option was suggested (and implemented) by Ilya Kashnitsky: the bold and small subtitle carrying a default of ‘this version built on …’ with the date is now customisable; motivation was for example stating a post-publication DOI which is indeed useful. In working with DOI I also finally realized that I was blocking displays of DOIs in the references: the PNAS style use \doi{} for a footer display (which we use e.g. for vignette info) shadowing the use via the JSS.cls borrowed from the Journal of Statistical Software setup. So we renamed the YAML header option to doi_footer for clarity, still support the old entries for backwards compatibility (yes, we care), renamed the macro for this use — and with an assist from LaTeX wizard Achim Zeileis added a new \doi{} now displaying DOIs in the references as they should! We also improved some internals as e.g. the Travis CI checks but I should blog about that another time, and documented yet more YAML header options in the vignette.

  • ActiveState Adds Beta Functionality for Open Source Language Automation
  • The New LLVM Repository Is Now Officially Available Via Git On GitHub

    The LLVM project has long been transitioning from Subversion-centered development to using Git around GitHub. The new "LLVM monorepo" Git setup is now considered finalized. 

    A few days ago I wrote about the LLVM transition to Git nearly being finalized while the announcement hit the wire yesterday of its success. James Knight who has been working on this initiative announced, "The new official monorepo is published to LLVM's github organization. At this point, the repository should be considered stable -- there won't be any more rewrites which invalidate commit hashes (barring some _REALLY_ good reason...)."

More in Tux Machines

SUSE releases enterprise Linux for all major ARM processors

SUSE has released its enterprise Linux distribution, SUSE Linux Enterprise Server (SLES), for all major ARM server processors. It also announced the general availability of SUSE Manager Lifecycle. SUSE is on par with the other major enterprise Linux distributions — Red Hat and Ubuntu — in the x86 space, but it has lagged in its ARM support. It’s not like SLES for ARM is only now coming to market for the first time, either. It has been available for several years, but on a limited basis. Read more

MellowPlayer – multi-platform cloud music integration

With my CD collection spiraling out of control, I’m spending more time listening to music with a number of popular streaming services. Linux offers a great range of excellent open source music players. But I’m always on the look out for fresh and innovative streaming players. Step forward MellowPlayer. MellowPlayer offers a web view of various music streaming services with integration with your desktop. It was developed to provide a Qt alternative to Nuvola Player. The software is written in C++ and QML. Read more

Some Thoughts on Open Core

Nothing is inherently anti-business about Free and Open Source Software (FOSS). In fact, a number of different business models are built on top of FOSS. The best models are those that continue to further FOSS by internal code contributions and that advance the principles of Free Software in general. For instance, there's the support model, where a company develops free software but sells expert support for it. Here, I'd like to talk a bit about one of the more problematic models out there, the open core model, because it's much more prevalent, and it creates some perverse incentives that run counter to Free Software principles. If you haven't heard about it, the open core business model is one where a company develops free software (often a network service intended to be run on a server) and builds a base set of users and contributors of that free code base. Once there is a critical mass of features, the company then starts developing an "enterprise" version of the product that contains additional features aimed at corporate use. These enterprise features might include things like extra scalability, login features like LDAP/Active Directory support or Single Sign-On (SSO) or third-party integrations, or it might just be an overall improved version of the product with more code optimizations and speed. Because such a company wants to charge customers to use the enterprise version, it creates a closed fork of the free software code base, or it might provide the additional proprietary features as modules so it has fewer problems with violating its free software license. Read more

Linux 4.20 Allows Overclockers To Increase The Radeon TDP Power Limit

The AMDGPU Linux kernel driver for a while has now offered command-line-driven OverDrive overclocking for recent generations of Radeon GPUs. This has allowed manipulating the core and memory clock speeds as well as tweaking the voltage but has not supported increasing the TDP limit of the graphics card: that's in place with Linux 4.20 Up until now with the AMDGPU Linux kernel driver there hasn't been support for increasing the TDP power limit beyond its default, but has allowed for reducing that limit should you be trying to conserve power / allow your GPU to run cooler. A change was quietly added to the Linux 4.20 kernel to allow increasing the power limit when in the OverDrive mode. This change wasn't prominently advertised but fortunately a Phoronix reader happened to run across it today and tipped us off. Read more