Announcement

Collapse
No announcement yet.

A Look At The Most Promising Next-Gen Linux Software Update Mechanisms

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • A Look At The Most Promising Next-Gen Linux Software Update Mechanisms

    Phoronix: A Look At The Most Promising Next-Gen Linux Software Update Mechanisms

    With traditional software package management solutions like APT and Yum showing their age and not adapting well to the embedded world and the slew of new areas for Linux like IoT, a new generation of atomic-based Linux software update solutions continue to be worked on. Matt Porter of the Konsulko Group is presenting at this week's Embedded Linux Conference Europe 2016 with a comparison of these update technologies...

    http://www.phoronix.com/scan.php?pag...ftware-Updates

  • #2
    Are those "atomic updates" like transactions that can be rolled back?

    Comment


    • #3
      It's nice that you can rollback. OSTree is nice, it is better, but they don't solve the problem that well.
      I think Habitat solves the problem properly and it doesn't care about the distro you have. It's a static binary that has 1 single requirement: Linux Kernel 2.6+.
      Their website: https://www.habitat.sh/
      Here is for example how the GDB package looks like in Habitat: https://app.habitat.sh/#/pkgs/core/g...20160926185837
      Pay attention how specific it is about it's dependencies. Full reuse between applications, while still being completely isolated when needed.

      I understand that it does not have exactly the same goal as OSTree, but I don't see why it couldn't update your entire system.

      Comment


      • #4
        It would be cool, if modern package managers would be written in modern and more secure programming languages. Well, yes, one is writte in Go, but the rest still in C!
        Hey guys, there is C++ 11, C++ 14 and rust, too!

        Comment


        • #5
          Originally posted by Steffo View Post
          It would be cool, if modern package managers would be written in modern and more secure programming languages. Well, yes, one is writte in Go, but the rest still in C!
          Hey guys, there is C++ 11, C++ 14 and rust, too!
          Newer != better

          Also, C11 is a thing if you believe that newer is better.

          Comment


          • #6
            Originally posted by Alliancemd View Post
            It's a static binary that has 1 single requirement:
            Why from one extreme to another one?

            Comment


            • #7
              Originally posted by atomsymbol View Post
              Are those "atomic updates" like transactions that can be rolled back?
              kinda
              atomic in IT means that the operation is either successful 100% OR fails 100%.
              You don't get silly situations where the operation fails in the middle of updating files/records and leaves the system/filesystem/database in an inconsistent state.

              Comment


              • #8
                Originally posted by Nille View Post

                Why from one extreme to another one?
                I imagine that when it's statically linked it cannot be screwed up by a borked library that it depends on.

                Comment


                • #9
                  "... similar to OSTree but does not require reboots to activate bundles."

                  I am beginning to wonder about RedHat's management when I read that they are in support of this. Call APT old, but not needing to reboot for 99% of all updates has always been a big win for me. I hate how Windows always wants to reboot and forces people to close running applications, to log back in and to start over. And here we have RedHat supporting just this kind of crap.

                  My picture of RedHat is changing and I'm hoping M$ is going to buy them up. I bet RedHat's management would be excited about the takeover and make them feel like a reboot.

                  Comment


                  • #10
                    Originally posted by sdack View Post
                    "... similar to OSTree but does not require reboots to activate bundles."

                    I am beginning to wonder about RedHat's management when I read that they are in support of this. Call APT old, but not needing to reboot for 99% of all updates has always been a big win for me. I hate how Windows always wants to reboot and forces people to close running applications, to log back in and to start over. And here we have RedHat supporting just this kind of crap.

                    My picture of RedHat is changing and I'm hoping M$ is going to buy them up. I bet RedHat's management would be excited about the takeover and make them feel like a reboot.
                    As a commercial enterprise, Red Hat is worrying about the 1% of updates that do screw up. In order to make it bullet proof, they perform the update in a special pre-boot environment, since reboots only happen at scheduled maintenance. Desktop users are OK with something that works 99% of the time, so this doesn't apply to them.

                    Comment

                    Working...
                    X