• Boomer Humor Doomergod@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 day ago

    Are Linux users really working in the kernel all that much? I’ve been doing support for Linux sysadmins for a decade and not once have I needed to touch the kernel.

    • Xatolos@reddthat.com
      link
      fedilink
      arrow-up
      0
      ·
      1 day ago

      I mis-phrased that, sorry. In the Android case, you can’t access a lot of networking functionality and other lower level access functions.

      Running ifconfig responses with:

      Warning: cannot open /proc/net/dev (Permission denied). Limited output.

      Even though it is based on Linux, and has access to the ifconfig app, it’s not really something you can do. There are other things to consider like that. While you could try to give yourself root access, it’s messy and not something that’s really easy or encouraged.

      In macOS’s case, it’s Unix to a point, but try installing NVIDIA cards in them (for CUDA cores). There are Unix drivers for Nvidia cards, for x86 and ARM, but even thought it’s Unix, it still won’t work.

      How about running native Vulcan? It’s a major API for 3D graphics. It has a Unix driver, but still can’t work on macOS. Best that can be done is workarounds, but that’s not native and has issues.

      There is Unix support for these, but macOS isn’t really Unix underneath.

      • Boomer Humor Doomergod@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 day ago

        Okay, that makes more sense. Though the amount of trouble I’ve heard Linux folks have with Nvidia stuff shouldn’t mean that it’s not Linux. Just that Nvidia sucks.

        Also, Vulkan seems to have a ton of support for Apple Silicon.

        And finally, Mac OS has been certified Unix 03 since 2009 except for version 10.7