63 comments

  • somat 2 hours ago ago

    Unix itself was created as a rejection of robust software architecture and tools.

    "I remarked to Dennis that easily half the code I was writing in Multics was error recovery code. He said, "We left all that stuff out of Unix. If there's an error, we have this routine called panic, and when it is called, the machine crashes, and you holler down the hall, 'Hey, reboot it.'"

    -- Tom Van Vleck

    Not that this is a bad thing, but unix was created as a hacker's toy, a small elegant system to play games on, This is why it is so fun to use. I mean, it is not really small or elegant anymore. but that is how it started, not as a robust correct business system. That is also why it got so popular. "A small hackable lowcost operating system with full source" colleges: yes please, and at a critical time in computing history, a very influential generation of hackers learned on it. Something now is better than perfect that does not exist, or that old cliche, worse is better.

    • pjmlp an hour ago ago

      Lets remind ourselves that initially, DoD assigned an higher security score to Multics than UNIX, with PL/I proper strings and arrays, with bounds checking available (configurable), as one of the key reasons.

    • marcus_holmes 2 hours ago ago

      "you either die a <minimal hackable low cost OS> or live long enough to become a <huge enterprise OS>"

      • dvrp 2 hours ago ago

        “You either die a LISP, or live long enough to become JavaScript”

        • HexDecOctBin an hour ago ago

          Which is funny, considering the size of CL spec.

    • zombot 26 minutes ago ago

      And now 50 years of "worse is better" come home to roost, with a vengeance.

  • qalmakka 3 hours ago ago

    A great pragmatical axiom of security is that if it doesn't come cheap in terms of speed and convenience, it's likely going to fail in the end. People will always pick practicality over security in the real world: if it takes too much time to lock and unlock the front door, the average person will just leave it ajar.

    Linux was a monolithic kernel because in 1991 microkernel were in earnest 25 years too early. Computers didn't really have the extra performance to spend for things like IPC and stuff. lots of other kernel designs that started back then like NT and Nextstep (was the NextStep kernel called XNU already? I guess not) all tried the microkernel route and then ended up doing stuff like networking at kernel level anyway because it just didn't work well enough.

    arguably nowadays we have extra headroom to spare so stuff like containers, sandboxing, userspace drivers are becoming more and more commonplace.

  • 7373737373 3 hours ago ago

    That most of the Linux kernel runs in https://en.wikipedia.org/wiki/Protection_ring 0 should have stopped decades ago

    Perhaps processor architectures like the https://en.wikipedia.org/wiki/Intel_iAPX_432 which do away with such coarse grained and therefore dangerous abstractions by using capability-based addressing should have succeeded earlier too. This is how modern programming languages should be structured too, instead of giving no guarantees to programmers (and therefore their users) about what (parts of) programs are able to access like they do now.

    • yjftsjthsd-h 3 hours ago ago

      > That most of the Linux kernel runs in https://en.wikipedia.org/wiki/Protection_ring 0 should have stopped decades ago

      Do you have a way to do it on the hardware people actually have that doesn't destroy performance every time the CPU context switches? You can always move all your filesystems to FUSE if you like the performance...

      • 7373737373 2 hours ago ago

        I can't answer the hardware part.

        But i'm perplexed by the unrelenting, ever re-occurring "counterpoint" of performance whenever the topic of sound security architectures comes up. As if even a 2x slowdown would be unacceptable, so many Moore's law doublings after Linux has been created later, in exchange for a system that doesn't allow thousands of vulnerabilities, and would limit the effects of more, yet undetected ones.

        • ptidhomme 4 minutes ago ago

          > a 2x slowdown would be unacceptable, [...] in exchange for a system that doesn't allow thousands of vulnerabilities

          OpenBSD fits the bill

        • yjftsjthsd-h 2 hours ago ago

          I am fairly confident that you would find that most people, if offered the chance to take that performance hit in exchange for some security improvement, would not take the deal so quickly as you. Since this is (somewhat) in the context of mobile, I also have to point out that it's also going to be a battery hit and that might be an even harder sell.

        • anonymous908213 2 hours ago ago

          Software has become doubly bad at the same rate that hardware has become doubly good, so we by no means have compute to spare. A 2x slowdown would absolutely be unacceptable. No business is going to pay for twice as much compute on their servers. No developer is going to pick the OS that takes 30 minutes to compile a large Rust program instead of 15 minutes. If you get double the performance for the same cost, it's not even a contest.

          • 7373737373 2 hours ago ago

            To me this looks like a world rushing toward catastrophic failure

            Security isn't just a word, it's the security of the world as technology becomes ever more integrated and influential in it

            • anonymous908213 2 hours ago ago

              I don't disagree that security is important, but you need a better pitch than "give up half of your compute for security" for a general-purpose OS, because the reality is nobody's buying with a sales pitch like that and you need a pitch that people will actually buy if you want to see that security manifest in the real world.

              • showlife an hour ago ago

                The better pitch is "give up half of your compute for security or give up all of your compute when your company is forced to shut down because of a security incident." Almost all of the work I do is patching or managing the orchestration that facilitates that patching. If my employer didn't think they had to pay me to do this I'm sure they wouldn't!

              • hollerith 24 minutes ago ago

                I’d gladly give up half of the compute on my devices for security if given the option.

                • yjftsjthsd-h 16 minutes ago ago

                  Sadly no real mobile equivalent, but you might consider qubes-os on PC.

        • undefined 2 hours ago ago
          [deleted]
      • pjmlp an hour ago ago

        Yes, it works alright for Windows, macOS, iOS, iPadOS, Android, Fuchsia.

        And all those cars, rockets, factories powered by QNX, INTEGRITY,....

        Ah, and those Switch games, nothing really that relevant.

        • yjftsjthsd-h 43 minutes ago ago

          > Yes, it works alright for Windows, macOS, iOS, iPadOS, Android, Fuchsia.

          Other than Fuchsia (I assume), all of those are at most hybrid systems with the performance-sensitive drivers still in ring 0.

          > And all those cars, rockets, factories powered by QNX, INTEGRITY,....

          Yes, you can get away with a lot if you're willing to sacrifice performance for safety.

          > Ah, and those Switch games, nothing really that relevant.

          That actually is an interesting point. Do you know how that works? I'd guess either they're doing something fun in hardware or they've actually got something going on in software worth considering. (Unless the thing they're doing is impractical to port to more general-purpose systems)

  • privacyishuman 4 hours ago ago
  • __MatrixMan__ 3 hours ago ago

    I don't think this is an accurate description of why linux was created. But I do think it's time to design something that better fits the needs of the modern world.

    We need another Bell Labs.

    • grapheneos an hour ago ago

      Our post isn't about why Linux was created. It's about the design choices and priorities from the initial creation of the project to the present day. We said it was created as a rejection of those things, not that the project was started in order to do so.

      • zombot 20 minutes ago ago

        That looks like a distinction without a difference to me.

    • notorandit an hour ago ago

      Not even that, IMHO.

      The fact that we now have multi gigabyte RAM devices, does not mean that the kernel can go multi megabyte.

      I'm also think that CPU designers should talk more to kernel developers: Linus is right on this topic.

    • wilsonjensen 2 hours ago ago

      > I don't think this is an accurate description of why linux was created.

      Yeah I think they're conflating UNIX-like general philosophy and Linux.

      The UNIX method has been shown to have many upsides.

      Though implementations due to slow old computers without fancy GPUs are user hostile

      It's all computer state so IMO applying the same concept and principle is more valuable a mindset than something more specific "Linux 4eva!"

      • notorandit an hour ago ago

        Unix ans Linux are 20+ years apart with all the changes that happened to hardware, software and even to C: they could hardly have the same general architecture.

        Of course, I am talking about the kernel, not the entire OS.

        Linux stood up on the shoulders of a giant like Minix, Unix was basically designed and coded from scratch.

      • grapheneos an hour ago ago

        Our posts were only about the Linux kernel, not an overall OS built on top of it. We weren't talking about the API design inherited from Unix or compatibility with software written for it. We also weren't talking about why it was created but rather the design choices.

        • notorandit an hour ago ago

          Yes, smaller and verifiable kernels would help a lot against buggy and malicious code. Let alone stability and robustness.

          Then, I for one, would not change C for anything else. The problem is not the language (which is just a tool), the problem is the coding (and the coders).

          • 7373737373 41 minutes ago ago

            Having languages themselves be built like microkernels would help security a hell of a lot too however

            • yjftsjthsd-h 38 minutes ago ago

              > Having languages themselves be built like microkernels

              What does that mean? Like... small stdlib with everything moved to extra libraries? Languages don't really have a ring 0 so I'm not sure how to read this even though it feels like a maybe-interesting take

              • 7373737373 23 minutes ago ago

                Yeah, currently popular languages don't have any separation, internal isolation, any way to limit or monitor authority (and use of that authority) to access and use resources at all. Programs and any part of them usually have full ambient authority, meaning they can just name and use resources (importing libraries by name, opening any files by stating file paths, ...) without restrictions.

                Instead, (parts of) programs should be restrictable to pure computation by denying any external resource access by default, unless explicitly granted or approved more (to the minimum they need, following the principle of least authority).

                See: https://en.wikipedia.org/wiki/E_(programming_language) or any of the languages listed here: https://en.wikipedia.org/wiki/Object-capability_model#Langua...

                Having a microkernel OS isn't really sufficient if you want to "hollow out the attack surface" well, because many programs (including imported libraries) consist of hundreds of thousands of lines of code made by hundreds or thousands of people (and now also AI). So programs should be internally compartmentalizable as well. Only this, imported libraries being able to sandbox their imported libraries and so on recursively truly reduces the possible effects of vulnerabilities to a minimum.

                And only programming languages (or virtual machines i guess) can achieve these type of guarantees in a platform independent way.

                • yjftsjthsd-h 17 minutes ago ago

                  Oh, you want an object-capability language; I didn't connect those dots. Yes, that would be an excellent compliment and now that you've spelled it out I can see the analogy.

              • notorandit 2 minutes ago ago

                It does not mean anything to me.

      • yjftsjthsd-h 2 hours ago ago

        > Yeah I think they're conflating UNIX-like general philosophy and Linux.

        I don't think they are, actually; they appear to be arguing microkernel vs monolithic kernel, and we have unix-likes based on microkernels.

  • guywithahat 3 hours ago ago

    I love this discussion, because it demonstrates what the market/developers actually care about.

    Anyone who studies kernel development long enough will eventually say micro kernels are much safer, we have better languages now, or there are better ways to access OS resources, and they’re sort of right. But the reason Linux succeeds is because it focuses on being the fastest, fully featured kernel, and that’s what people actually wants. There are dozens of alternatives that nobody uses because at the end of the day, nobody cares if your language is “safer” and your drivers don’t have kernel access if it’s 10% slower when reading IO. They’ll just stick with Linux

    • 7373737373 2 hours ago ago

      I strongly doubt this is (still) true. Most devices are networked now. What is 10% less performance, in exchange for proper security? I would switch in a heartbeat. The only problem is that existing microkernel projects are not exactly usable yet. That their research, development and adoption are not more strongly funded and supported seems strange to me. As a programmer, OF COURSE i'd prefer to work with systems that gave me fine grained guarantees about and monitoring of resource (file system, network, CPU, memory) access, -isolation and -consumption. When driving, one doesn't go as fast as one can either, if it would risk others' and one's own lives - that would be irresponsible and reckless. Do we really want to live in a pedal to the metal world where even the smallest mistake means death? Or perhaps a little bit more chill one?

      • grapheneos 44 minutes ago ago

        Microkernels are incredibly widely used. They're used on many of the components used in a modern computer including radios for cellular, Wi-Fi/Bluetooth, GNSS, NFC, etc. Many components are now written in a more secure way than mainstream general purpose operating systems. macOS and iOS have also gradually been moving more towards microkernel design by moving code out of the kernel. They started from a foundation where that was part of the design but not heavily used.

    • zbentley 2 hours ago ago

      The main reason Linux succeeds is network effects. Once everyone has been coding to Linux APIs for upwards of 35 years, the ability to move to something else is incredibly limited. Even if a new OS attracted 100% mind share for all new development, it'd take many, many years for it to approach even the beginnings of ubiquity that Linux had in the early 2000s.

      Replacing Linux (and likely having to change some parts of POSIX as well) would be an even taller order than rewriting C code in some other language. At least for userland rewrites, you have parity and an API (POSIX, other libraries in userland) to code to.

      It might still be a good idea to do both of those, mind you. But let's not fool ourselves: the main reasons the incumbents are the incumbents is that it's hard, likely-to-fail, and incredibly slow work to replace them.

      • grapheneos 43 minutes ago ago

        Replacing the Linux kernel ABI isn't necessary to have a microkernel written in a memory safe language. It can provide the same ABI. gVisor is not what we mean but shows it's doable.

    • ReDress 2 hours ago ago

      [dead]

    • pjmlp an hour ago ago

      If they had to actually pay for Linux, I doubt it.

  • sayandip_sarkar 33 minutes ago ago

    [flagged]

  • yjftsjthsd-h 3 hours ago ago

    > Linux was created as a rejection of robust software architecture and tools. It's a monolithic kernel with no internal isolation written as memory unsafe code. A typo in an obscure driver for unused functionality can easily create a fully privileged code execution vulnerability.

    Which is, of course, why GrapheneOS is based on minix, right?

    Edit: Really, this is just GOS being GOS; only ever Security (by their own very specific, poorly defined definition thereof), with nothing else allowed to be a consideration. There is a reason the industry went with monolithic kernels when other options existed. Even today in 2026, we've merely worked out how to reduce the performance hit of microkernels, and in the 90s Torvalds was very justified in preferring to ship something that would actually run decently on extant hardware.

    Edit2: To be fair. I like minix. I have actually tried to make HURD into a usable system. I want these things to work. But there are harsh tradeoffs in play that are still painful even after decades of work, and this kind of post does not exactly convince people that GOS is making level-headed evaluations of technical choices.

    • undefined 37 minutes ago ago
      [deleted]
    • margalabargala 2 hours ago ago

      Arguably the only reason GOS is relevant is because they do exactly what you criticize them for.

      Lots of options exist for people who do what you describe as the "right" way. People who aren't in the security-at-all-costs group have plenty to choose from.

      Are you saying that software that promotes security at the price of usability should not be permitted to exist, nor that people should, whatever their use case, desire it?

      • rendaw an hour ago ago

        I think most users of GOS don't have a stick by which to measure the security claims of GOS. And I'm guessing most are there for privacy, not security.

      • yjftsjthsd-h 2 hours ago ago

        > Are you saying that software that promotes security at the price of usability should not be permitted to exist, nor that people should, whatever their use case, desire it?

        I'm saying maybe they could desire and work on their thing without having to constantly yell about how everyone and everything else is awful and sucks.

        • grapheneos 39 minutes ago ago

          You're falsely accusing us of what you're doing. You lie about what we've said and done. It's clear you can't participate in threads about GrapheneOS in a constructive way and should stop. Your posts are nothing more than malicious jabs and contribute negative value to the discussion.

          • yjftsjthsd-h 33 minutes ago ago

            We are literally having this conversation because you opened with

            > Linux was created as a rejection of robust software architecture and tools. It's a monolithic kernel with no internal isolation written as memory unsafe code. A typo in an obscure driver for unused functionality can easily create a fully privileged code execution vulnerability.

            Anytime anyone mentions other ROMs like LineageOS you immediately jump in to proclaim them insecure. The shoe fits. If you don't like being called out for slinging mud at other projects including those that your project is built on, feel free to stop doing it.

            • grapheneos 21 minutes ago ago

              We were participating in a discussion about a discussion with high importance to protecting people's privacy and security. You're participated in threads about GrapheneOS in bad faith misrepresenting and directly lying about what we've said and done. You're continuing vile personal attacks on our team including continuing to try to portray as being insane and delusional as you've done many times before. You aren't contributing anything constructive to discussions about it but rather are trying to use it as a platform to harm the project and our team.

    • grapheneos 36 minutes ago ago

      You're misrepresenting about what we've said and done. You're misrepresenting what we've built and are building. You're claiming our posts in that threads are somehow irrational which they're not. On the other hand, your posts in discussions about GrapheneOS are clearly irrational attacks on the project and our team. You post attacks on it in many threads about it and desperately try to spin things to harm the project and our team. You've consistently engaged in vile personal attacks towards our team and supported harassment. The post you've made only subtly masks that you're continuing to make those personal attacks. It's a clear reference to the libel and harassment you've supported for a long time.

  • nxobject 3 hours ago ago

    To be charitable, Linus initially called Linux "a hobby, won't be big and professional like GNU" and "NOT protable [sic](uses 386 task switching etc), probably never will support anything other than AT-harddisks".

  • huijzer 3 hours ago ago

    Linux was created around 1991. I think it has avoided many of the fads successfully so things could have been much worse (I’m looking at you C++).

    • guywithahat 3 hours ago ago

      I wouldn’t celebrate just yet they’re building some drivers in Rust now. I wouldn’t be surprised if in a few years Rust goes the way of Haskell

      • grapheneos an hour ago ago

        None of the core Linux kernel or drivers are written in Rust. Drivers can theoretically be written in Rust but there's immense resistance to landing the bindings needed to do it. In practice, a few core Android drivers were ported to Rust and in very rare cases new drivers for a previously unsupported GPU, etc. are using it. The positive impact from such a tiny portion of the kernel being written in Rust is negligible. A lot of the cost of supporting it has been paid without reaping the benefits.

  • nromiun 2 hours ago ago

    > What's simplistic about it? The industry could have heavily adopted microkernels and memory safe languages 30 years ago.

    Ignoring the pesky little problem that these microkernels and languages did not exist 30 years ago. It was Linux with their garbage drivers that enabled people to use it in their computers. It is very easy to imagine something rather than creating it in reality.

    • pjmlp an hour ago ago

      Linux only mattered to me in 1995, because doing the UNIX work assignments from the university DG/UX and Solaris timesharing servers wasn't possible on the joke of Windows NT POSIX subsystem.

      Had Microsoft been serious about their POSIX support, I would not have bothered one second.

      It wasn't FOSS nor hardware support, rather not having to travel to campus laboratory and fight for a terminal, losing a couple of hours.

  • lordkrandel 2 hours ago ago

    Doh, a dude's opinion about something done completely for free as a hobbyist 30 years ago, that had world success, actually killing the robust corporate "only a lab can afford" alternative. Give yourself some peace

  • ReDress 3 hours ago ago

    [dead]