Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Monday February 10 2020, @07:18PM   Printer-friendly
from the lots-of-new-and-shiny dept.

www.phoronix.com

This kernel is simply huge: there is so many new and improved features with this particular release that it's mind-boggling. I'm having difficulty remembering such a time a kernel release was so large.

The quick summary of Linux 5.6 changes include: WireGuard, USB4, open-source NVIDIA RTX 2000 series support, AMD Pollock enablement, lots of new hardware support, a lot of file-system / storage work, multi-path TCP bits are finally going mainline, Year 2038 work beginning to wrap-up for 32-bit systems, the new AMD TEE driver for tapping the Secure Processor, the first signs of AMD Zen 3, better AMD Zen/Zen2 thermal and power reporting under Linux, at long last having an in-kernel SATA drive temperature for HWMON, and a lot of other kernel infrastructure improvements.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Insightful) by Anonymous Coward on Monday February 10 2020, @07:28PM (53 children)

    by Anonymous Coward on Monday February 10 2020, @07:28PM (#956473)

    You're saying this like it's a GOOD thing.

    HINT: It's NOT

    Starting Score:    0  points
    Moderation   +4  
       Insightful=2, Interesting=2, Total=4
    Extra 'Insightful' Modifier   0  

    Total Score:   4  
  • (Score: 0) by Anonymous Coward on Monday February 10 2020, @07:40PM (8 children)

    by Anonymous Coward on Monday February 10 2020, @07:40PM (#956481)

    Of course it's huge! now with systemd! No module needed! Shhh... Like Boeing's MCAS, it's a secret. There's no need for anybody to know about it.

    • (Score: 3, Touché) by DannyB on Monday February 10 2020, @09:13PM (7 children)

      by DannyB (5839) Subscriber Badge on Monday February 10 2020, @09:13PM (#956531) Journal

      You have it backward.

      systemd will include the kernel. Not the kernel including systemd.

      systemd will include the boot loader.

      --
      People today are educated enough to repeat what they are taught but not to question what they are taught.
      • (Score: 2, Funny) by Anonymous Coward on Tuesday February 11 2020, @01:27AM (6 children)

        by Anonymous Coward on Tuesday February 11 2020, @01:27AM (#956649)

        Well I expect systemd to include the entire OS and at least three window managers, and I expect it to fly me to Vegas on the weekends.

        • (Score: 1, Funny) by Anonymous Coward on Tuesday February 11 2020, @06:14AM (1 child)

          by Anonymous Coward on Tuesday February 11 2020, @06:14AM (#956750)

          OK well fly, maybe. Would you accept crash nearby?

        • (Score: 2) by DeVilla on Wednesday February 12 2020, @02:55AM (2 children)

          by DeVilla (5354) on Wednesday February 12 2020, @02:55AM (#957065)

          Well I expect systemd to include ... at least three window managers

          Systemd is entirely too opinionated to allow that much choice. Systemd will provide one solution that will do everything you think you need a window manager for and nothing you don't. If you think you need something systemd doesn't provide, your requirements are wrong and you are trying to do something the wrong way. If it provides something you think you don't need, you don't understand the problem you currently have that systemd fixes if you use it the right way.

          • (Score: 0) by Anonymous Coward on Wednesday February 12 2020, @03:11AM (1 child)

            by Anonymous Coward on Wednesday February 12 2020, @03:11AM (#957071)

            If you think you need something systemd doesn't provide, your requirements are wrong and you are trying to do something the wrong way.

            Ok, will it least get me to Reno? Will it keep me from getting drunk and marrying some transvestite in an Elvis Chapel?

            • (Score: 2) by DeVilla on Sunday February 16 2020, @12:30AM

              by DeVilla (5354) on Sunday February 16 2020, @12:30AM (#958639)

              Ok, will it least get me to Reno?

              Absolutely not. You should go to Atlantic City.

              Will it keep me from getting drunk and marrying some transvestite in an Elvis Chapel?

              Yes. It will be a Star Trek themed Chapel.

        • (Score: 2) by driverless on Saturday February 15 2020, @06:27PM

          by driverless (4770) on Saturday February 15 2020, @06:27PM (#958566)

          Just don't expect it to buy you dinner afterwards.

  • (Score: 3, Funny) by EJ on Monday February 10 2020, @08:10PM (10 children)

    by EJ (2452) on Monday February 10 2020, @08:10PM (#956495)

    Bigger is ALWAYS better. The kernel should include a web browser, text editor, paint program, etc. Why should you have to get some 3rd party utility to do something any self-respecting OS should already have integrated?

    Memory is cheap. Everyone should have at LEAST a spare 128GB to hold the kernel.

    • (Score: 2) by DannyB on Monday February 10 2020, @08:25PM (4 children)

      by DannyB (5839) Subscriber Badge on Monday February 10 2020, @08:25PM (#956503) Journal

      Memory is cheap. Everyone should have at LEAST a spare 128GB to hold the kernel.

      Hey! Save some of that memory for Java!

      Modern Java is able to take advantage of more memory than ever before. Often this is done on Linux. Imagine a highly optimizing (for speed) compiler that can turn 1 K of native code into many times that much native code. Aggressive inlining. Loop unrolling. NO function call overhead for long stretches of native code. Calls to many functions vanish, or rather are replaced by the code they would call. Dynamically based on the runtime characteristics of your actual hardware at this moment. Something a C compiler can't do ahead of time because it doesn't have the whole picture. When the compiler runs, a function that should get inlined might not even be written yet -- other than as an entry in a .h file.

      --
      People today are educated enough to repeat what they are taught but not to question what they are taught.
      • (Score: 2) by pipedwho on Monday February 10 2020, @08:45PM (3 children)

        by pipedwho (2032) on Monday February 10 2020, @08:45PM (#956514)

        And it still manages to run much slower than 'non-optimised' native code.

        • (Score: 5, Insightful) by DannyB on Tuesday February 11 2020, @12:30AM (2 children)

          by DannyB (5839) Subscriber Badge on Tuesday February 11 2020, @12:30AM (#956622) Journal

          Native code vs native code? Did you read what I wrote? Did you understand the JIT compiler having the whole runtime picture?

          In any case, it obviously is fast enough that Twitter rewrote [soylentnews.org] their stack in 2012 to Java, specifically for performance. What idiots they must be.

          Java won't win every speed contest. It does win some. But it's not so slow as you think. (Greenspun's tenth rule [wikipedia.org]) For some reason it's been #1 in most of the last fifteen years [youtube.com], but never going below 2nd place.

          There is a simple reason for Java's success. Since the beginning of computers in business, and mostly also in science, money has been the dominant concern. Once upon a time optimizing for dollars also meant optimizing obsessively for every last cpu cycle and byte. No more. Today we optimize for dollars, which means optimizing for developer time. The dominant cost today is developer time. For the price of a developer with benefits for only one year, say $100-$250K, you can buy a pretty sweet server box. Point being that hardware is cheap compared to developer time. That hardware will last more years than that cost of one developer for one year.

          We're still optimizing for dollars, just not for bytes and cpu cycles any more. I know this may come as unwelcome news. I get a rush of dopamine every time I save cpu cycles or bytes. But I'm not obsessed with it. I know my true optimization is ultimately for dollars, which is developer time.

          I don't cite the source here: a language is too low level when it forces you to focus on the irrelevant.

          The irrelevant is anything that isn't relevant to the problem you're trying to solve.

          This is the reality we live in. Hate it as you may, Java is number one. Please consider that there is probably a reason for that. Companies like Red Hat, IBM, Amazon, Microsoft are investing lots of money into research into JVM, its GC, and other VM optimizations. Why is that do you suppose? Not out of the goodness of their hearts. They think there is money to be made by investing major resources into Java.

          Again, I'm sorry if this is unhappy news to you; But it is the REALITY of the world we live in. Not some fantasy world where bytes and cpu cycles are the dominant concern. Ah, to be a programmer back in the 1970's once again. But I can't go back.

          --
          People today are educated enough to repeat what they are taught but not to question what they are taught.
          • (Score: 0) by Anonymous Coward on Tuesday February 11 2020, @06:21AM (1 child)

            by Anonymous Coward on Tuesday February 11 2020, @06:21AM (#956756)

            You optimize for dollars... I mean developer time, until some developer optimizes in a better and faster way. Then you optimize for developers. It's so confusing for managers.

            • (Score: 2) by DannyB on Wednesday February 12 2020, @08:27PM

              by DannyB (5839) Subscriber Badge on Wednesday February 12 2020, @08:27PM (#957368) Journal

              Based on Java usage, managers don't appear to be confused about optimizing for greed dollars.

              Never have been.

              It's just that once long ago that also meant optimizing for bytes and cycles.

              --
              People today are educated enough to repeat what they are taught but not to question what they are taught.
    • (Score: 1, Funny) by Anonymous Coward on Monday February 10 2020, @09:00PM (3 children)

      by Anonymous Coward on Monday February 10 2020, @09:00PM (#956526)

      You speak then perhaps of Emacs? For that includes all of the above, and more.
      Emacs 2020 will include a Linux Kernel. :) ...just to "be safe" and be "feature complete."

      • (Score: 1) by DECbot on Monday February 10 2020, @10:13PM

        by DECbot (832) on Monday February 10 2020, @10:13PM (#956563) Journal

        That kernel is just for VMs and containers. The native kernel with kexec functionality isn't scheduled until 2022.

        --
        cats~$ sudo chown -R us /home/base
      • (Score: 4, Funny) by DannyB on Tuesday February 11 2020, @12:32AM (1 child)

        by DannyB (5839) Subscriber Badge on Tuesday February 11 2020, @12:32AM (#956623) Journal

        Here is what happened with Emacs users.

        The first time they get into emacs, they don't know how to exit. So they eventually build all other OS functionality into emacs lisp, being unable to escape.

        --
        People today are educated enough to repeat what they are taught but not to question what they are taught.
        • (Score: 3, Funny) by Runaway1956 on Tuesday February 11 2020, @01:29AM

          by Runaway1956 (2926) Subscriber Badge on Tuesday February 11 2020, @01:29AM (#956650) Journal

          Huh? Wait a second. Is there an exit? I didn't even know that. When I found myself in Emacs Land, I just nuked from orbit, and repaved.

    • (Score: 2) by DannyB on Wednesday February 12 2020, @08:34PM

      by DannyB (5839) Subscriber Badge on Wednesday February 12 2020, @08:34PM (#957372) Journal

      Memory is cheap. Everyone should have at LEAST a spare 128GB to hold the kernel.

      Here is a convenient memory sizing tool [yourdatafitsinram.net] to help identify which hardware might be big enough to hold your Java hello world program.

      References:
      Java Hello World -- Enterprise Edition [github.com]
      Java Fizzbuzz -- Enterprise Edition [github.com]

      --
      People today are educated enough to repeat what they are taught but not to question what they are taught.
  • (Score: 5, Insightful) by DannyB on Monday February 10 2020, @08:12PM (16 children)

    by DannyB (5839) Subscriber Badge on Monday February 10 2020, @08:12PM (#956497) Journal

    Isn't the kernel modular?

    Now the last time I read about this, and compiling kernels, was in about 1997 as I was studying Linux. In June 1999 I finally got my first Linux box and never looked back.

    As I understood things at that time, kernel modules could be omitted, compiled into the kernel, or compiled as loadable modules.

    1. Omitted -- probably because they are irrelevant. Hardware modules for hardware you don't have. Etc.

    2. Compiled in to kernel -- because you want them at boot time even before the ramdisk is available.

    3. loadable modules -- because you might want them, and can make them packages so that you could possibly omit installing them, but with a package manager could load them if software needing those modules depends on them. Contrived examples: VPN, certain hardware support, WiFi, certain filesystems, etc.

    If you're needing a kernel for a small system like a Raspberry Pi, isn't it possible to build a modular kernel, and leave most of the modules off of the distribution image? Letting those modules be "installed", then at runtime "loaded" as needed?

    Or am I misunderstanding something?

    --
    People today are educated enough to repeat what they are taught but not to question what they are taught.
    • (Score: 0) by Anonymous Coward on Monday February 10 2020, @09:41PM (12 children)

      by Anonymous Coward on Monday February 10 2020, @09:41PM (#956548)

      Sure. Much like Windows you install drivers for devices you attach vs. pre-installed drivers.

      Its really a balancing game, pre-installed so stuff just works right out of the box for various scenarios vs. the basic stuff mostly works, for all others the users have to go "configure" (in the case of linux) or install drivers (in the case of windows).

      For majority of folks, the non-geeks, I'd assume the former is preferable. For the geeks, obviously the former is an affront to architecture purity due to the "bloat" and the rest of the world should follow their shining light.

      • (Score: 2) by DannyB on Monday February 10 2020, @11:00PM (11 children)

        by DannyB (5839) Subscriber Badge on Monday February 10 2020, @11:00PM (#956576) Journal

        It would seem to me that having all of the kernel modules available on disk has no significant penalty. It merely costs disk space. Nothing more. If you plug in a new hardware item, you already have a driver immediately ready to use. That's convenience. Or alternately, go through a Windows-like experience of "searching for driver . . ."

        --
        People today are educated enough to repeat what they are taught but not to question what they are taught.
        • (Score: 4, Insightful) by Runaway1956 on Tuesday February 11 2020, @01:37AM (5 children)

          by Runaway1956 (2926) Subscriber Badge on Tuesday February 11 2020, @01:37AM (#956652) Journal

          That "searching for driver" experience is vastly different on Linx, vs Windows. Mostly, the drivers are found via the package manager, whether it be RPM or APT or whatever. On Windows, if you don't have an installation disk, then you go to Google. Google doesn't mark the results with tags like "reputable source" or anything. Unless you know what you are doing, you can easily download a boatload of malware, and install it, instead of the driver you were searching for. Alternatively, you can find an outdated driver, which may or may not work for your particular hardware.

          Both worlds have their problems, but I think Linux problems are a lot easier to solve reliably than Windows.

          • (Score: 0) by Anonymous Coward on Tuesday February 11 2020, @06:28AM (4 children)

            by Anonymous Coward on Tuesday February 11 2020, @06:28AM (#956759)

            I wish they would just compile statically. Give up on the dream of upgrading each package separately. Huge, static globs of binary for each program you use that I can run off a USB. That is actually my idea of perfection in software - it never breaks after upgrade. You can run off a USB stick. It never breaks(*).

            (*) Shut up.

            • (Score: 2) by DannyB on Tuesday February 11 2020, @02:40PM (3 children)

              by DannyB (5839) Subscriber Badge on Tuesday February 11 2020, @02:40PM (#956840) Journal

              Maybe another alternative . . .

              Maybe it is time that Kernel developers consider the possibility of . . . OMG . . . having a standard kernel driver API. Not for all possible kernel modules, but for device drivers. It seems device drivers are the vast majority of kernel source code, or so I am under the impression. If necessary later, introduce a 2nd improved kernel driver API. Surely enough is understood about what kernel access a device driver needs after about 30 years?

              Another idea, multiple standard interfaces for different kinds of drivers. Eg, filesystems. Direct memory access drivers. Video devices. Etc. A single driver could implement one or more of these interfaces.

              --
              People today are educated enough to repeat what they are taught but not to question what they are taught.
        • (Score: 2, Informative) by The Mighty Buzzard on Tuesday February 11 2020, @04:20AM (3 children)

          by The Mighty Buzzard (18) Subscriber Badge <themightybuzzard@proton.me> on Tuesday February 11 2020, @04:20AM (#956719) Homepage Journal

          Having the necessary functionality for a specific module to even hook into does cause very significant overhead. Having a specific SATA driver, for instance, built as a module is not the same as not even having SATA support in the kernel. If you know you're never going to need any hardware but what you currently have, you can shrink the complete fuck out of the kernel.

          --
          My rights don't end where your fear begins.
          • (Score: 2) by DannyB on Tuesday February 11 2020, @02:45PM

            by DannyB (5839) Subscriber Badge on Tuesday February 11 2020, @02:45PM (#956842) Journal

            That is another useful thing about the kernel, its adaptability for small devices with fixed hardware. Wristwatches. Cameras. RoKu, TiVo. Thermostats. And who knows what else.

            --
            People today are educated enough to repeat what they are taught but not to question what they are taught.
          • (Score: 2) by DannyB on Tuesday February 11 2020, @10:36PM (1 child)

            by DannyB (5839) Subscriber Badge on Tuesday February 11 2020, @10:36PM (#956997) Journal

            That makes sense. Having support for the module in the kernel is a non-zero cost, in addition to disk cost of the module.

            --
            People today are educated enough to repeat what they are taught but not to question what they are taught.
            • (Score: 0) by Anonymous Coward on Wednesday February 12 2020, @02:45AM

              by Anonymous Coward on Wednesday February 12 2020, @02:45AM (#957061)

              Not to mention that some modules and CONFIGs are mutually exclusive.

        • (Score: 2) by RS3 on Tuesday February 11 2020, @06:42PM

          by RS3 (6367) on Tuesday February 11 2020, @06:42PM (#956924)

          ... kernel modules available on disk has no significant penalty. It merely costs disk space.

          In fact it's probably net zero. It's about the same size as a module or compiled into the kernel.

          You could argue that the kernel usually resides in a separate partition than /lib, but either way, kernel modules are pretty small.

    • (Score: 2) by digitalaudiorock on Monday February 10 2020, @10:23PM (1 child)

      by digitalaudiorock (688) on Monday February 10 2020, @10:23PM (#956568) Journal

      Absolutely. This machine (very old hardware) is running Gentoo and a 4.19.97 kernel, with everything I need, and pretty much nothing more, compiled directly into the kernel with the exception of a few modules:

      du -sh /boot/kernel-4.19.97-gentoo /lib/modules/4.19.97-gentoo/
      4.2M /boot/kernel-4.19.97-gentoo
      316K /lib/modules/4.19.97-gentoo/

      The only thing that's huge is the (mostly unused) source:

      du -sh /usr/src/linux-4.19.97-gentoo/
      1.2G /usr/src/linux-4.19.97-gentoo/

      • (Score: 2) by The Mighty Buzzard on Tuesday February 11 2020, @04:22AM

        by The Mighty Buzzard (18) Subscriber Badge <themightybuzzard@proton.me> on Tuesday February 11 2020, @04:22AM (#956721) Homepage Journal

        I used to do that too. Until about the three bazillionth time I had to rebuild the kernel because I wanted to plug something in that I hadn't built the driver in for. It's just not worth doing on a desktop/laptop.

        --
        My rights don't end where your fear begins.
    • (Score: 2) by hendrikboom on Tuesday February 11 2020, @12:58AM

      by hendrikboom (1125) Subscriber Badge on Tuesday February 11 2020, @12:58AM (#956636) Homepage Journal

      What you need is enough drivers compiled in to be able to access the hardware and file systems containing the modules.

  • (Score: 5, Insightful) by Snotnose on Monday February 10 2020, @08:18PM (12 children)

    by Snotnose (1623) on Monday February 10 2020, @08:18PM (#956499)

    Nope, the source is huge. I suspect the average person will use only a small subset of the features. My laptop doesn't support USB4, so that won't be compiled in. I don't have an AMD so none of that will be compiled in, etc etc etc.

    Then again, I haven't configured/compiled a kernel since '04 or so.

    CSB. In '02 I was flying to a trade show with a new laptop. Thought I'd use the dead air (ha!) to configure my kernel. Some guy behind me took an interest, asked me what I was doing. Told him I was configuring my kernel, he said "wow, that's hard core!". To me it had been an everyday part of my job for 10 years.

    Got the kernel compiling, went to watch a DVD, and the battery promptly died about an hour in. Crap.

    --
    Why shouldn't we judge a book by it's cover? It's got the author, title, and a summary of what the book's about.
    • (Score: 2, Insightful) by Anonymous Coward on Monday February 10 2020, @08:24PM (5 children)

      by Anonymous Coward on Monday February 10 2020, @08:24PM (#956501)

      Got the kernel compiling, went to watch a DVD, and the battery promptly died about an hour in. Crap.

      Who in their right mind compiles a Linux kernel and watches a DVD on a laptop that's on battery?

      • (Score: 2) by DannyB on Monday February 10 2020, @08:30PM (1 child)

        by DannyB (5839) Subscriber Badge on Monday February 10 2020, @08:30PM (#956508) Journal

        I don't recall anyone claiming to be in their right mind. So you are making unwarranted assumptions. People who compile kernels in flight might not be like other people who don't. If compiling kernels was part of their job, maybe they even hack on that kernel? Who knows. I would probably be impressed too.

        --
        People today are educated enough to repeat what they are taught but not to question what they are taught.
        • (Score: -1, Flamebait) by Anonymous Coward on Monday February 10 2020, @09:58PM

          by Anonymous Coward on Monday February 10 2020, @09:58PM (#956555)

          People who compile kernels in flight might not be like other people who don't. If compiling kernels was part of their job, maybe they even hack on that kernel?

          Maybe if they were a diversity hire. In 04, watching a DVD would have also used a lot of juice. newb error.

      • (Score: 3, Funny) by Snotnose on Tuesday February 11 2020, @12:42AM

        by Snotnose (1623) on Tuesday February 11 2020, @12:42AM (#956627)

        A guy on an airplane who's never owned a laptop before, for one....

        --
        Why shouldn't we judge a book by it's cover? It's got the author, title, and a summary of what the book's about.
      • (Score: 0) by Anonymous Coward on Tuesday February 11 2020, @09:13AM (1 child)

        by Anonymous Coward on Tuesday February 11 2020, @09:13AM (#956785)

        The alt-right.

        • (Score: 2) by DannyB on Tuesday February 11 2020, @02:41PM

          by DannyB (5839) Subscriber Badge on Tuesday February 11 2020, @02:41PM (#956841) Journal

          Even on Linux, it's ctrl-alt-delete.

          --
          People today are educated enough to repeat what they are taught but not to question what they are taught.
    • (Score: 2, Interesting) by Anonymous Coward on Monday February 10 2020, @08:29PM (5 children)

      by Anonymous Coward on Monday February 10 2020, @08:29PM (#956507)

      You need to try configuring (not even necessarily building the end result) just to see how big of a clusterfuck the configuration menus have become. Lots of shit that is x86 or embedded processor only leaks into the configuration menus for unrelated systems. Various features that should be possible to disable for your specific platform can't be (permanent enabled checkbox). The amount of new configurable but not really configurable hardware Kconfigs in each new minor release of the kernel has become insane. And since the distro maintainers only ever use it was a make all modules config, none of the KConfig shit gets properly tested for non-all module usecases.

      ARM is a secondclass citizen, and every other arch is 3rd or worse class.

      • (Score: 2) by DannyB on Monday February 10 2020, @08:32PM (1 child)

        by DannyB (5839) Subscriber Badge on Monday February 10 2020, @08:32PM (#956509) Journal

        That sounds like the menuconfig system is not maintained with the modules it configures? Or at least its dependency graph is not maintained. Too bad.

        Complexity might really be the measure of "kernel is too big" rather than how much disk or memory size it uses.

        --
        People today are educated enough to repeat what they are taught but not to question what they are taught.
        • (Score: 0) by Anonymous Coward on Monday February 10 2020, @10:08PM

          by Anonymous Coward on Monday February 10 2020, @10:08PM (#956561)

          Spot on. Complexity defines how well the idea is actualized. The other two are only measures of the medium.

      • (Score: 2) by Azuma Hazuki on Tuesday February 11 2020, @04:30AM (2 children)

        by Azuma Hazuki (5086) on Tuesday February 11 2020, @04:30AM (#956726) Journal

        You're not kidding. I used Gentoo back when starting Linux in 2004, but for a long time (2009-late 2019) have just been too hardware-constrained for it. I remember running it on an Inspiron 500m (Pentium-M "Banias" 1.3 GHz single core, 512 MB RAM) and having very little trouble finding everything necessary to run.

        Flash forward to about 3 months ago when I got an amazing deal on a Thinkpad E495 (8GB memory, 256GB NVMe SSD, Ryzen 7 3700U 4C/8T). Granted, I now run LVM-on-LUKS, which is a more complex setup and required an initramfs, but for the life of me I cannot start from a clean "make allnoconfig" file and find everything I need. It compiles fine but sits there forever at "loading initial ramdisk...". Thankfully, booting an Arch liveUSB and running "make localmodconfig" gets a (mostly) working base which I can trim down and modify. But I still have no idea what I did wrong with the from-scratch attempt :/

        As you said, entire categories of stuff just...fail to appear completely unless obscure other options are chosen. No warning is given about this.

        --
        I am "that girl" your mother warned you about...
        • (Score: 2) by The Mighty Buzzard on Tuesday February 11 2020, @03:17PM

          by The Mighty Buzzard (18) Subscriber Badge <themightybuzzard@proton.me> on Tuesday February 11 2020, @03:17PM (#956858) Homepage Journal

          It's still pretty easy if you're building for a headless VM or the like. Once you start doing it for actual hardware, especially on a desktop that you never know WTF you're going to want to attach to it a month from now, it gets a wee bit more difficult. Such are the perils of hardware advancement and variety.

          --
          My rights don't end where your fear begins.
        • (Score: 0) by Anonymous Coward on Wednesday February 12 2020, @03:13AM

          by Anonymous Coward on Wednesday February 12 2020, @03:13AM (#957072)

          Probably passing "quiet" as a kernel parameter or turned down the configured log level, you selected the wrong CPU architecture, you mismatched the microcode, you didn't generate the ramdisk properly by configuring mkinitrd and running it, or a mismatch in compression algorithms for the initrd. In my experience, those are the five most common reasons that pops up. Well, other than not having enough memory/disk space, which seems unlikely here.

  • (Score: 2, Troll) by darkfeline on Monday February 10 2020, @08:51PM (2 children)

    by darkfeline (1030) on Monday February 10 2020, @08:51PM (#956517) Homepage

    How's your microkernel coming along, Tanenbaum? Are you going to release it before Hurd?

    --
    Join the SDF Public Access UNIX System today!
    • (Score: 2) by DannyB on Monday February 10 2020, @09:17PM

      by DannyB (5839) Subscriber Badge on Monday February 10 2020, @09:17PM (#956533) Journal

      Or Google's Fuchsia?

      --
      People today are educated enough to repeat what they are taught but not to question what they are taught.
    • (Score: 5, Insightful) by RamiK on Monday February 10 2020, @09:44PM

      by RamiK (1813) on Monday February 10 2020, @09:44PM (#956551)

      How's your microkernel coming along, Tanenbaum? Are you going to release it before Hurd?

      Tanenbaum's microkernel is probably deployed on more machines than Linux or at least Windows:

      Intel chipsets post-2015 are running MINIX 3 internally as the software component of the Intel Management Engine.[16] [ptsecurity.com][17] [zdnet.com]

      ( https://en.wikipedia.org/wiki/MINIX [wikipedia.org] )

      --
      compiling...