Language Selection

English French German Italian Portuguese Spanish

Ubuntu: NGINX on Ubuntu Server 18.04, Pick, Departure From i386 and Pop!_OS 19.04 Overview

Filed under
Ubuntu
  • How to install the latest version of NGINX on Ubuntu Server 18.04

    NGINX is one of the most popular web servers on the planet. It's reliable, scalable, and easy to use. But did you know, if you install NGINX from the default Ubuntu Server 18.04 repositories, the version you get is out of date? You don't want that. In fact, you probably want the most up-to-date stable release of the software.

  • Pick – A Color Picker for Ubuntu with History Support

    For Ubuntu 18.04 and higher, you can easily install the tool from Ubuntu Software as it has been made as snap package.

  • Ubuntu Confirms It’s Dropping All 32-bit Support Going Forward

    Ubuntu has confirmed plans to drop all support for 32-bit (i386) systems going forward, beginning with the upcoming Ubuntu 19.10 release.

    The decision will mean that the distro no longer builds, packages or distributes any 32-bit software, libraries or tools on newer versions of Ubuntu.

    Users of Ubuntu 18.04 LTS 32-bit are not affected by today’s announcement and will (should?) continue to work as normal, with access to the existing 32-bit archive.

    But the move will mean they are unable to upgrade to a newer Ubuntu release — nope, not even the next LTS!

    Will such a major sounding change have much of an impact?

    Eh, no, not really.

    Ubuntu says it’s stranding a mere 1% of its current user base on 32-bit version Ubuntu 18.04 LTS (which isn’t terrible place to stay, as it is supported until 2023).

  • i386 architecture will be dropped starting with eoan (Ubuntu 19.10)
    Last year, the Ubuntu developer community considered the question of whether
    to continue carrying forward the i386 architecture in the Ubuntu archive for
    future releases.[1]  The discussion at the time was inconclusive, but in
    light of the strong possibility that we might not include i386 as a release
    architecture in 20.04 LTS, we took the proactive step to disable upgrades
    from 18.04 to 18.10 for i386 systems[2], to avoid accidentally stranding
    users on an interim release with 9 months of support instead of letting them
    continue to run Ubuntu 18.04 LTS with its 5 years of standard support.
    
    
    
    
    In February of this year, I also posted to communicate the timeline in which
    we would take a final decision about i386 support in 20.04 LTS[3], namely,
    that we would decide in the middle of 2019.
    
    
    
    
    The middle of 2019 has now arrived.   The Ubuntu engineering team has
    reviewed the facts before us and concluded that we should not continue to
    carry i386 forward as an architecture.   Consequently, i386 will not be
    included as an architecture for the 19.10 release, and we will shortly begin
    the process of disabling it for the eoan series across Ubuntu
    infrastructure.
    
    
    
    
    While this means we will not provide 32-bit builds of new upstream versions
    of libraries, there are a number of ways that 32-bit applications can
    continue to be made available to users of later Ubuntu releases, as detailed
    in [4].   We will be working to polish the 32-bit support story over the
    course of the 19.10 development cycle.  To follow the evolution of this
    support, you can participate in the discourse thread at [5].
  • Ubuntu 19.10 To Drop 32-bit x86 Packages

    Ubuntu and their downstream flavors all stopped shipping x86 32-bit images and now for the 19.10 cycle they have decided to stop their i386 support entirely. Beginning with Ubuntu 19.10, the archive/packages will not be built for x86 32-bit. 

    Longtime Ubuntu developer Steve Langasek announced their decision today that the i386 architecture will be dropped starting with Ubuntu 19.10, affecting all Ubuntu-based platforms / those relying upon the official Ubuntu Eoan archives. 

  • Pop!_OS 19.04 overview | Unleash your potential

    In this video, I am going to show an overview of Pop!_OS 19.04 and some of the applications pre-installed.

Marius Nestor on Canonical Abandoning Old(er) PCs

  • Canonical Will Drop Support for 32-bit Architectures in Future Ubuntu Releases

    Canonical announced today that it finally decided to completely drop support for 32-bit (i386) hardware architectures in future releases of its popular Ubuntu Linux operating system.
    Last year, during the development cycle of the Ubuntu 18.04 LTS (Bionic Beaver) operating system series, Canonical announced that they won't offer 32-bit installation images (ISOs), a trend that was shortly followed by all official Ubuntu Linux flavors with the Ubuntu 18.10 (Cosmic Cuttlefish) release. However, Ubuntu's 32-bit repositories were still available.

    As Ubuntu 18.04 LTS (Bionic Beaver) will be supported for the next five years, Canonical disabled upgrades from Ubuntu 18.04 LTS to Ubuntu 18.10 for 32-bit systems to avoid leaving users on a short-lived release, and now, they announced that starting with the upcoming Ubuntu 19.10 (Eoan Ermine) release, support for 32-bit system will no longer be provided.

Marius Nestor on the latest Linux patches for Ubuntu

  • Canonical Outs Important Linux Kernel Security Update for All Ubuntu Releases

    Canonical has released an important Linux kernel security update for all supported Ubuntu Linux releases to address two critical security vulnerabilities that could crash users' systems.

    In a recent security advisory, Canonical details two recently discovered security vulnerabilities (CVE-2019-11477 and CVE-2019-11478) affecting Linux kernel's TCP retransmission queue implementation when handling some specific TCP Selective Acknowledgment (SACKs).

    Both security vulnerabilities were discovered by Jonathan Looney and could allow a remote attacker to crash the affected system by causing a denial of service. Known as SACK Panic, they affect all supported Ubuntu Linux releases, including Ubuntu 19.04, Ubuntu 18.10, Ubuntu 18.04 LTS, and Ubuntu 16.04 LTS.

Ubuntu says i386 to be 86'd with Eoan 19.10 release

  • Ubuntu says i386 to be 86'd with Eoan 19.10 release: Ageing 32-bit x86 support will be ex-86

    Ubuntu is set to drop support for the i386 processor architecture beginning with its next release.

    Canonical, developer of the iconic Linux distro, said on Tuesday the 19.10 release, code named Eoan Ermine, will drop 32-bit i386 from its supported architectures, which include 64-bit AMD64 (x86-64) and 64-bit Armv8.

    "The Ubuntu engineering team has reviewed the facts before us and concluded that we should not continue to carry i386 forward as an architecture," said Ubuntu desktop team member Will Cooke.

Ubuntu 19.10 To Completely Drop Support For 32-bit Architecture

  • Ubuntu 19.10 To Completely Drop Support For 32-bit Architecture

    The 32-bit architecture used in Intel and other compatible CPUs is referred to as “i386” in the Debian and other communities of Linux distributions. However, as the legacy hardware that only runs a 32-bit operating system isn’t popular anymore, the major Linux distributions and software vendors are shifting away from it. To put things in perspective, there is a good chance that most of the computers made during the last decade only support 64-bit instructions.

    Ubuntu, the world’s most popular open source operating system, decided to ditch its plans to offer 32-bit installation images during its Ubuntu 17.10 development cycle. However, different 32-bit packages were still available to support existing users. Now, Canonical has announced it plans to completely drop support for such 32-bit packages.

By LWN

  • Ubuntu dropping i386 support

    Starting with the upcoming "Eoan Ermine" (a.k.a. 19.10) release, the Ubuntu distribution will not support 32-bit x86 systems.

Canonical won't release the next version of Ubuntu in 32-bit

  • Canonical won't release the next version of Ubuntu in 32-bit

    CANONICAL HAS ANNOUNCED that it will drop 32-bit support for Ubuntu in a forthcoming release.

    Starting with the forthcoming Ubuntu 19.10 (Eoan Ermine, apparently), Ubuntu builds will be available in 64-bit versions only, tapping another nail into the coffin of the ageing architecture.

    The move is an extension of last year's rollout of the recently-patched Ubuntu 18.04 LTS. Because that will be supported for five years, Ubuntu decided not to release a 32-bit edition, and prevented those on a previous 32-bit build from upgrading - a fresh install was required in 64-bit.

    Canonical is keen to point out that unless you have a creaky old lappy, it won't really change anything - 32-bit apps won't run in 64-bit Ubuntu directly, but many of the most popular apps that don't have a native 64-bit version are either already Ubuntu Snaps, or can be easily turned into them.

    The company will release details of what users need to do to be ready for version 19.10 ahead of its release in October 2019. Once the beta is ready, there'll be a lot more detail, in case anyone fancies updating early.

Ubuntu has decided to drop i386 (32-bit) architecture from...

  • Ubuntu has decided to drop i386 (32-bit) architecture from Ubuntu 19.10 onwards

    Yesterday the Ubuntu engineering team announced their decision to discontinue i386 (32-bit) as an architecture, from Ubuntu 19.10 onwards. In a post to the Ubuntu Developer Mailing List, Canonical’s Steve Langasek explains that “i386 will not be included as an architecture for the 19.10 release, and we will shortly begin the process of disabling it for the eoan series across Ubuntu infrastructure.”

    Langasek also mentions that the specific distributions of builds, packages or distributes of the 32-bit software, libraries or tools will no longer work on the newer versions of Ubuntu. He also mentions that the Ubuntu team will be working on the 32-bit support, over the course of the 19.10 development cycle.

Canonical planning to drop 32bit support with Ubuntu 19.10

  • Canonical planning to drop 32bit support with Ubuntu 19.10 onwards

    As you might have heard by now, Canonical has made the decision to drop 32bit support from Ubuntu 19.10 onwards.

    Writing on the mailing list, as well as this post on Ubuntu's Community Hub, Canonical gave a reminder that the decision isn't coming without warning. It was proposed last year and it was followed up with another post detailing a final decision to be made in the middle of 2019. So here we are, the decision seems to have been made.

    The problem isn't hardware, as likely around 99% of people nowadays have a 64bit capable computer. Going by our own statistics, from what 2,254 users told us only 4 are using a 32bit Linux distribution. The issue then, is mainly software and libraries needed to actually run 32bit applications. This is where it sounds like there's going to be plenty of teething issues, with a number of people not too happy about the decision.

Original: I386 architecture will be dropped starting with eoan

  • I386 architecture will be dropped starting with eoan (Ubuntu 19.10)

    Last year, the Ubuntu developer community considered the question of whether to continue carrying forward the i386 architecture in the Ubuntu archive for future releases. The discussion at the time was inconclusive, but in light of the strong possibility that we might not include i386 as a release architecture in 20.04 LTS, we took the proactive step to disable upgrades from 18.04 to 18.10 for i386 systems, to avoid accidentally stranding users on an interim release with 9 months of support instead of letting them continue to run Ubuntu 18.04 LTS with its 5 years of standard support.

    In February of this year, I also posted to communicate the timeline in which we would take a final decision about i386 support in 20.04 LTS, namely, that we would decide in the middle of 2019.

    The middle of 2019 has now arrived. The Ubuntu engineering team has reviewed the facts before us and concluded that we should not continue to carry i386 forward as an architecture. Consequently, i386 will not be included as an architecture for the 19.10 release, and we will shortly begin the process of disabling it for the eoan series across Ubuntu infrastructure.

Wine developers worry

  • Wine Developers Concerned With Ubuntu Dropping 32-bit Support With Ubuntu 19.10

    Ubuntu's solution for using Wine on 32-bit going forward, which is to publish applications as snaps, or use an Ubuntu 18.04 LTS based LXD container that has full access to multiarch 32-bit WINE and related libraries, was also discussed by the Wine developers, with Vincent Povirk of CodeWeavers saying that there's no point putting much effort into this temporary solution. The maintainer of the Wine OBS repository also mentioned that he has no interest in maintaining so many libraries.

    So what's the solution for all of this? Not building Wine packages for Ubuntu 19.10 and later releases, or using the Steam runtime for the Wine packages seem to be the answers, but no final decision has been made yet.

    Ubuntu is not the first Linux distribution to go with 64-bit only releases. openSUSE leap did this as well, but it continues to provide all the 32-bit libraries needed to build and run Wine. From what the Ubuntu announcement and FAQ says about dropping the 32-bit x86 architecture, it's looks like there are no plans for doing something similar in Ubuntu.

On goes the i386 saga

  • Ubuntu Officially Announced it’s Dropping Support for 32-bit Packages Going Forward

    Ubuntu has officially announced about dropping the support for 32-bit (i386) systems going forward, starting with the upcoming Ubuntu 19.10 release.

    The 32-bit architecture is used in many Intel and Intel-compatible CPUs. It’s refereed as i386 in Ubuntu, Debian and some other Linux distributions.

    Many peoples prefer to use the more generic name called “x86” for 32-bit.

    32-bit packages were designed especially for legacy hardware’s that only runs a 32-bit operating system, which isn’t popular anymore.

    No manufacturers have produced any 32-bit computer hardware for desktop / laptop for last 10 years and it was made during the last decade.

    Most of the major Linux distributions (Red Hat) and software vendors (lack of support in the upstream Linux kernel, toolchains, and web browsers) were already dropped support for 32-bit.

  • Canonical Developer Tries Running GOG Games On 64-Bit-Only Ubuntu 19.10 Setup

    In response to the decision to drop 32-bit x86 support beginning in Ubuntu 19.10, Alan Pope of Canonical and longtime Ubuntu member decided to try running some GOG games under an Ubuntu 19.10 daily build that he configured to remove the 32-bit packages ahead of the actual removal. Unfortunately, his experience didn't go so smoothly.

    While Valve has the resources to come up with an effective solution to bypass the Ubuntu archives doing away with 32-bit packages on Ubuntu 19.10, the smaller outfits like GOG may have a more difficult time especially with not being as centralized as Steam. Pains could be involved at least in the short-term for those wanting to enjoy their 32-bit-focused games on newer Ubuntu releases.

  • Results of testing games on 64-bit only eoan (19.10)

    These don’t seem to be true for the limited testing I did. I would urge more testing and feedback. I’m also keen to hear if my testing strategy is flawed in any way. Bear in mind I’m trying to approach this from a “normal user” point of view who wants to download and run a game they already had in their collection, or a new title they just bought.

    I have a few (50) games in GOG that I have purchased over the years. I only had time to select a few at ~random. I picked 5 which gave me a representative sample of relatively modern stuff mixed with retro games, and a good mix between native Linux and native Windows titles.

Ubuntu is dropping i386 support and WINE developers are irked

  • Ubuntu is dropping i386 support and WINE developers are irked

    As of version 19.10, Ubuntu will no longer support i386. With the arrival of Eoan Ermine, Ubuntu is severing 32-bit ties, and some developers are concerned.

    The move is not entirely unexpected. The Ubuntu developers had previously said it would make an i386 decision in the middle of 2019. That time having rolled around, the Ubuntu engineering team says that it "has reviewed the facts before us and concluded that we should not continue to carry i386 forward as an architecture". WINE developers are among those unhappy with the decision.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's leftovers

  • Linux Weekly Roundup #35

    Hello and welcome to this week's Linux Roundup and what a wonderful week we had! We have plenty of Linux Distro releases and LibreOffice 6.3 RC1. The Linux distros with releases this week are Q4OS 3.8, SparkyLinux 5.8, Mageia 7.1, ArcoLinux 19.07.11, Deepin 15.11, ArchBang 2107-beta, Bluestar 5.2.1, Slackel 7.2 "Openbox" and Endeavour OS 2019.07.15. I looked at most of these Linux Distros, links below, I will look at some of them in the new week and some I will unfortunately not have a look at, for download links and more, please visit distrowatch.com Well, this is this week's Linux Roundup, thank you so much for your time! Have a great week!

  • Full Circle Magazine: Full Circle Weekly News #140
  • Christopher Allan Webber: ActivityPub Conf 2019

    That's right! We're hosting the first ever ActivityPub Conf. It's immediately following Rebooting Web of Trust in Prague. There's no admission fee to attend. (Relatedly, the conference is kind of being done on the cheap, because it is being funded by organizers who are themselves barely funded.) The venue, however, is quite cool: it's at the DOX Centre for Contemporary Art, which is itself exploring the ways the digital world is affecting our lives. If you plan on attending (and maybe also speaking), you should get in your application soon (see the flier for details). We've never done one of these, and we have no idea what the response will be like, so this is going to be a smaller gathering (about 40 people). In some ways, it will be somewhere between a conference and a gathering of people-who-are-interested-in-activitypub. As said in the flier, by attending, you are agreeing to the code of conduct, so be sure to read that.

Sysadmin Appreciation Day, IBM and Fedora

  • Gift ideas for Sysadmin Appreciation Day

    Sysadmin Appreciation Day is coming up this Friday, July 26. To help honor sysadmins everywhere, we want you to share your best gift ideas. What would be the best way a team member or customer could show their appreciation for you? As a sysadmin, what was the best gift you've ever received? We asked our writers the same question, and here are their answers: "Whilst working in the Ubuntu community on Edubuntu, I took it upon myself to develop the startup/shutdown sound scheme, which became the default in Ubuntu for, from what I can understand, the next decade. Whilst people had a love-hate relationship with my sound scheme, and rightly so, I had a love-hate relationship with my sound card during the development. At the time I had recorded all my sound samples using one sample rate, but my new sound card, as my motherboard had exploded a few days earlier, did not support it. I had two choices, resample all my samples (which I didn't really want to do) or buy a new sound card.

  • Red Hat OpenStack Platform with Red Hat Ceph Storage: Radosbench baseline performance evaluation

    Red Hat Ceph Storage is popular storage for Red Hat OpenStack Platform. Customers around the world run their hyperscale, production workloads on Red Hat Ceph Storage and Red Hat OpenStack Platform. This is driven by the high level of integration between Ceph storage and OpenStack private cloud platforms. With each release of both platforms, the level of integration has grown and performance and automation has increased. As the customer's storage and compute needs for footprints have grown, we have seen more interest towards running compute and storage as one unit and providing a hyperconverged infrastructure (HCI) layer based on OpenStack and Ceph. [...] Continuing the benchmarking series, in the next post you’ll learn performance insights of running multi-instance MySQL database on Red Hat OpenStack Platform and Red Hat Ceph Storage across decoupled and hyperconverged architectures. We’ll also compare results from a near-equal environment backed by all-flash cluster nodes.

  • The State of Java in Flathub

    For maintainers of Java-based applications in Flathub, it's worth noting that even if you consume the Latest OpenJDK extension in your application, users will not be broken by major updates because OpenJDK is bundled into your Flatpak. The implication of this for users is that they won't see updates to their Java version until the application maintainer rebuilds the application in Flathub. If you maintain a Java-based Flatpak application on Flathub, you can consume the latest version of your chosen OpenJDK stream (either LTS or Latest) simply by rebuilding; the latest version of that OpenJDK steam will be pulled in automatically.

  • Fedora Magazine: Contribute at the Fedora Test Week for kernel 5.2

    The kernel team is working on final integration for kernel 5.1. This version was just recently released, and will arrive soon in Fedora. This version has many security fixes included. As a result, the Fedora kernel and QA teams have organized a test week from Monday, Jul 22, 2019 through Monday, Jul 29, 2019. Refer to the wiki page for links to the test images you’ll need to participate. Read below for details.

Debian and Ubuntu Leftovers

  • Bootstrappable Debian BoF

    Greetings from DebConf 19 in Curitiba! Just a quick reminder that I will run a Bootstrappable Debian BoF on Tuesday 23rd, at 13.30 Brasilia time (which is 16.30 UTC, if I am not mistaken). If you are curious about bootstrappability in Debian, why do we want it and where we are right now, you are welcome to come in person if you are at DebCon or to follow the streaming.

  • Candy Tsai: Outreachy Week 6 – Week 7: Getting Code Merge

    You can’t overhear what others are doing or learn something about your colleagues through gossip over lunch break when working remotely. So after being stuck for quite a bit, terceiro suggested that we try pair programming. After our first remote pair programming session, I think there should be no difference in pair programming in person. We shared the same terminal, looked at the same code and discussed just like people standing side by side. Through our pair programming session, I found out that I had a bad habit. I didn’t run tests on my code that often, so when I had failing tests that didn’t fail before, I spent more time debugging than I should have. Pair programming gave insight to how others work and I think little improvements go a long way.

  • about your wiki page on I/O schedulers and BFQ
    Hi,
    this is basically to report outdated statements in your wiki page on
    I/O schedulers [1].
    
    The main problematic statement is that BFQ "...  is not ideal for
    devices with slow CPUs or high throughput I/O devices" because too
    heavy.  BFQ is definitely more sophisticated than any of the other I/O
    schedulers.  We have designed it that way to provide an incomparably
    better service quality, at a very low overhead.  As reported in [2],
    the execution time of BFQ on an old laptop CPU is 0.6 us per I/O
    event, against 0.2 us for mq-deadline (which is the lightest Linux I/O
    scheduler).
    
    To put these figures into context, BFQ proved to be so good for
    "devices with slow CPUs" that, e.g., Chromium OS migrated to BFQ a few
    months ago.  In particular, Google crew got convinced by a demo [3] I
    made for them, on one of the cheapest and slowest Chromebook on the
    market.  In the demo, a fast download is performed.  Without BFQ, the
    download makes the device completely unresponsive.  With BFQ, the
    device remains as responsive as if it was totally idle.
    
    As for the other part of the statement, "...  not ideal for ...  high
    throughput I/O devices", a few days ago I ran benchmarks (on Ubuntu)
    also with one of the fastest consumer-grade NVMe SSDs: a Samsung SSD
    970 PRO.  Results [4] can be summarized as follows.  Throughput with
    BFQ is about the same as with the other I/O schedulers (it couldn't be
    higher, because this kind of drives just wants the scheduler to stay
    as aside as possible, when it comes to throughput).  But, in the
    presence of writes as background workload, start-up times with BFQ are
    at least 16 times as low as with the other I/O schedulers.  In
    absolute terms, gnome-terminal starts in ~1.8 seconds with BFQ, while
    it takes at least 28.7 (!) seconds with the other I/O schedulers.
    Finally, only with BFQ, no frame gets lost in video-playing
    benchmarks.
    
    BFQ then provides other important benefits, such as from 5x to 10X
    throughput boost in multi-client server workloads [5].
    
    So, is there any chance that the outdated/wrong information on your
    wiki page [1] gets updated somehow?  If I may, I'd be glad to update
    it myself, after providing you with all the results you may ask.
    
    In addition, why doesn't Ubuntu too consider switching to BFQ as
    default I/O scheduler, for all drives that BFQ supports (namely all
    drives with a maximum speed not above ~500 KIOPS)?
    
    Looking forward to your feedback,
    Paolo
    
    
  • Should Ubuntu Use The BFQ I/O Scheduler?

    The BFQ I/O scheduler is working out fairly well these days as shown in our benchmarks. The Budget Fair Queueing scheduler supports both throughput and low-latency modes while working particularly well for consumer-grade hardware. Should the Ubuntu desktop be using BFQ by default? [...] But in addition to wanting to correct that Wiki information, Paolo pops the question of why doesn't Ubuntu switch to BFQ as the default I/O scheduler for supported drives. Though as of yet, no Ubuntu kernel developers have yet commented on the prospect of switching to BFQ.

Devices With Linux Support

  • Quest Releases KACE SDA & SMA Updates

    The update to 7.0 for KACE Systems Deployment Appliance is primarily about bringing a scope of endpoint management capabilities with new support for Linux devices to the table.

  • Rugged, Kaby Lake transport computer has a 10-port LAN switch with PoE

    Axiomtek’s Linux-ready “tBOX400-510-FL” transportation system has a 7th Gen Intel CPU and a 10-port managed switch with 8x M12-style 10/100Mbps PoE and 2x GbE ports. The rugged system also has 3x mini-PCIe slots and dual swappable SATA drives. Axiomtek has launched a fanless, Kaby Lake-U based transportation computer with a choice of power supplies designed for in-vehicle, marine, or railway applications. The rugged tBOX400-510-FL features a Qualcomm-driven, Layer 2 managed PoE switch with support for IP surveillance and video management applications. “Customers can connect IP cameras directly without installing an extra PoE switch, minimizing overall deployment costs and installation space onboard,” stated Axiomtek product manager Sharon Huang.