Language Selection

English French German Italian Portuguese Spanish

Dell Shipped Linux On 162 Unique Platforms In Fiscal Year 2019

Filed under
GNU
Linux

Despite having shipped Linux on client systems since 1999, Dell has made waves in the developer and consumer space more recently with Project Sputnik, a now 6-year-old initiative that aimed to create a premium Linux PC that "just works" right out of the box using Ubuntu. That device, as most of you probably know, is the XPS 13.

However, over FY2019 Dell shipped Linux across 162 platforms, including various models of Precision Workstations, Latitude, Optiplex, Inspiron, Vostro and XPS lines. While Dell primarily ships with Ubuntu pre-installed, they also support a couple different China-specific distributions, and they certify machines like its Precision Mobile Workstation for Red Hat. (Dell simply chooses not to pre-install RHEL only because most customers will buy an enterprise license and then install it independently.)

If this hits you as somewhat of a surprise, you're not alone! Even Project Sputnik lead Barton George was taken aback by this statistic, and understands that people following Dell's movements don't necessarily have visibility into what's happening beyond Sputnik.

Read more

More in Tux Machines

Programming/Development: Zato, Wing, Receiving Code Review, CoffeeScript and BASIC

  • Zato 3.1 Released - Open-Source Python-based API Integrations and Backend Application Server
    The newest version of Zato, the open-source Python-based enterprise API integrations platform and backend application server, is out with a lot of interesting features, changes and additions.
  • Extending Wing with Python (Part Two)
    To debug extension scripts written for Wing, you will need to set up a new project that is configured so that Wing can debug itself. The manual steps for doing this are documented in Debugging Extension Scripts. However, let's use an extension script to do this automatically.
  • Robbie Harwood: Receiving Code Review
    From a maintainer's perspective, that's the primary role of code review: to ensure project quality and continued maintainability. But there's an important secondary purpose as well: to help contributors (and potential contributors) learn and grow. In other words, receiving code review is a learning and growth opportunity, and should be approached as such. And so, first and foremost: code review is not a judgement on you. It's a second set of eyes, and both of you are trying to make sure the changes are good. If they didn't want the change in the project, they'd say so! Subtlety isn't what's happening here. And besides, if anyone were perfect, we would do code review. Which leads into: everyone needs code review. No change is too small for it, and no one is perfect. I've broken builds by changing only documentation, and flagged potential security issues from developers who have been coding almost as long as I've been alive. (And they've done the same to me!) That's normal. That's life. That's code review. And it's fine, because we don't need it to be perfect on the first try. Contributing to open source isn't a school exam where we get a single attempt and it's most of the grade. We're concerned only with improving our software, and if there's grading at all, it's externally imposed (e.g., by an employer).
  • Best Free Books to Learn about CoffeeScript
    CoffeeScript is a very succinct programming language that transcompiles into JavaScript, so there is no interpretation at runtime. The syntax is inspired by Ruby, Python and Haskell, and implements many features from these three languages. CoffeeScript is closely related to JavaScript without having its eccentricities. However, CoffeeScript offers more than fixing many of the oddities of JavaScript, as it has some useful features including array comprehensions, prototype aliases and classes. It allows developers to write less code to get more done.
  • 10 PRINT Memorial in New Hampshire marks the birthplace of BASIC
    After just over 55 years, the birthplace of BASIC has been honoured with a memorial marker in New Hampshire, USA. Thanks to a campaign by local paper columnist David Brooks, the New Hampshire Historical Highway Marker was installed earlier this month. Professor John Kemeny, Maths professor Thomas Kurtz, and a group undergraduate students at Dartmouth College (pics) created BASIC (Beginner's All-purpose Symbolic Instruction Code). The first program ran on 1 May 1964.

Audiocasts/Shows: Linux Gaming News Punch, GNU World Order and More

Release of DragonFly BSD 5.6

  • DragonFly BSD 5.6
    DragonFly version 5.6 brings an improved virtual memory system, updates to radeon and ttm, and performance improvements for HAMMER2. The details of all commits between the 5.4 and 5.6 branches are available in the associated commit messages for 5.6.0rc1 and 5.6.0.
  • DragonFlyBSD 5.6 Released With VM System, HAMMER2 In Good Shape
    DragonFlyBSD 5.6 is now available as the latest major update to this popular BSD operating system. DragonFlyBSD 5.6 brings the HAMMER2 file-system by default following numerous improvements this cycle to HAMMER2 to put it now in comparable/better standing than HAMMER1. HAMMER1 though remains available for those interested. I'll have out some new HAMMER2 DragonFlyBSD benchmarks shortly.

Qt 5.12.4

  • Qt 5.12.4 Released with support for OpenSSL 1.1.1
    The update to OpenSSL 1.1.1 is important to note for users leveraging OpenSSL in their applications. We wanted to update now as the earlier version of OpenSSL runs out of support at the end of the year and some platforms, such as Android, need the new one even sooner. Unfortunately OpenSSL 1.1 is binary incompatible with 1.0, so users need to switch to the new one and repackage their applications. One important functionality enabled by OpenSSL 1.1 is TLS 1.3 bringing significant cryptography and speed improvements. As part of the change, some old and insecure crypto algorithms have been removed and support for some new crypto algorithms added. For the users not leveraging OpenSSL in their applications, no actions are needed. OpenSSL is not included in a Qt application, unless explicitly so defined by the developer. Going forward, Qt 5.12 LTS will receive many more patch releases throughout the coming years and we recommend all active developed projects to migrate to Qt 5.12 LTS. Qt 5.9 LTS is currently in ‘Strict’ phase and receives only the selected important bug and security fixes, while Qt 5.12 LTS is currently receiving all the bug fixes. Qt 5.6 Support has ended in March 2019, so all active projects still using Qt 5.6 LTS should migrate to a later version of Qt.
  • Qt 5.12.4 Released with support for OpenSSL 1.1.1
    Qt developers have announced the new release of Qt 5.12.4 on 17th June, 2019. Qt 5.12.4, the fourth patch release of Qt 5.12 LTS. It provides a number of bug fixes, as well as performance and other improvements. Also, it provides binaries build with OpenSSL 1.1.1, including the new TLS 1.3 functionality. Qt 5.12.4 provides around 250 bug fixes compared with the previous release of Qt 5.12.3. OpenSSL 1.1.1 has beenn updated since the older version of OpenSSL runs out of support at the end of the year. And some platforms requires OpenSSL 1.1.1 sooner like Android, etc.,