Slashdot Mirror


Linux Kernel 4.13 Officially Released (softpedia.com)

prisoninmate writes: As expected, the Linux 4.13 kernel series was made official this past weekend by none other than its creator, Linus Torvalds, which urges all Linux users to start migrating to this version as soon as possible. Work on Linux kernel 4.13 started in mid-July with the first Release Candidate (RC) milestone, which already gave us a glimpse of the new features coming to this major kernel branch. There are, of course, numerous improvements and support for new hardware through updated drivers and core components. Highlights of Linux kernel 4.13 include Intel's Cannon Lake and Coffee Lake CPUs, support for non-blocking buffered I/O operations to improve asynchronous I/O support, support for "lifetime hints" in the block layers and the virtual filesystem, AppArmor enhancements, and better power management. There's also AMD Raven Ridge support implemented in the AMDGPU graphics driver, which received numerous improvements, support for five-level page tables was added in the s390 architecture, and the structure randomization plugin was added as part of the build system.

6 of 43 comments (clear)

  1. Re:Does it fix Ryzen crashes? by bill_mcgonigle · · Score: 4, Insightful

    I'm thinking to upgrade my computer but I want to make sure Linux can take it... Linux has never been great with support for new hardware but a poorly supported CPU really surprised me.

    AMD has a recall on the crashy Ryzens. Contact customer service if you're affected.

    Errata happen, but If you want to be pissed about something, let it be AMD's refusal to provide thermal management documentation. It's insane - they will eventually capitulate and release the docs, but right now they're killing a golden opportunity they've created to disrupt Intel's previous lead, because sysadmins and systems integrators need to know how hot their systems are running.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  2. Still no mount events! by Gravis+Zero · · Score: 4, Interesting

    As someone who has been working on an init system for Linux, I can assure you that there is literally no event for when a mount has occurred! The best you can do is poll /proc/self/mountinfo to see if it's changed since you last looked. Udev had mount event support but it was so buggy and wrong that they decided to remove it completely!

    New processor support is nice but how about better event support for userspace programs?

    --
    Anons need not reply. Questions end with a question mark.
    1. Re:Still no mount events! by complete+loony · · Score: 2

      If something is broken, but nobody has complained, then obviously nobody is using it and the code can be deleted.

      Or at least this is a line of reasoning that is commonly used to remove features from open source software.

      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
    2. Re:Still no mount events! by Gravis+Zero · · Score: 3, Informative

      Udev can detect mount events such as the DVD being ejected by the eject button on the front of the unit.

      No, what it can detect is a change in media. Mounting is different because you can have several partitions on a drive and mount and unmount them at different times. However, udev cannot detect any of these mounts or unmounts.

      --
      Anons need not reply. Questions end with a question mark.
  3. Re:Having even finished testing .10 yet. by bankman · · Score: 2

    It's a bit like Google, Facebook, et al., where you are the product. Only in this case you are the QA.

    You're right, apart from the fact that being the QA is nothing like being the product of course. And you've figured out the QA part in FOSS now? Impressive since it almost says so in the definition...

    --
    I feel so sig.
  4. Re:Does it fix Ryzen crashes? by Anonymous Coward · · Score: 2, Informative

    Old info. Its was under NDA and license was stupid, it got sorted a few days ago.

    @rozhuk-im: That helped, thanks. Patch for the k10temp driver submitted upstream. Too late for the v4.14 kernel, but it will be available in v4.15.

    https://github.com/groeck/lm-sensors/issues/16