Announcement

Collapse
No announcement yet.

OpenWRT 14.07 Features Its New Init/Event System

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

  • OpenWRT 14.07 Features Its New Init/Event System

    Phoronix: OpenWRT 14.07 Features Its New Init/Event System

    Version 14.07 "Barrier Breaker" of OpenWRT has been released with many changes for this popular wireless/router Linux platform...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Originally posted by phoronix View Post
    Phoronix: OpenWRT 14.07 Features Its New Init/Event System

    Version 14.07 "Barrier Breaker" of OpenWRT has been released with many changes for this popular wireless/router Linux platform...

    http://www.phoronix.com/vr.php?view=MTgwMjk


    Michael, please fix your copypasta skills

    Comment


    • #3
      Does anyone know how procd works and that it does differently from other init systems?
      Their documentation is still basically non existent (see http://wiki.openwrt.org/doc/techref/procd)

      So why procd? What does it do better/differently?

      Comment


      • #4
        Originally posted by pininety View Post
        Does anyone know how procd works and that it does differently from other init systems?
        Their documentation is still basically non existent (see http://wiki.openwrt.org/doc/techref/procd)

        So why procd? What does it do better/differently?
        Well, systemd doesn't support Musl, so that wasn't even an option.

        Comment


        • #5
          Originally posted by pininety View Post
          Does anyone know how procd works and that it does differently from other init systems?
          Their documentation is still basically non existent (see http://wiki.openwrt.org/doc/techref/procd)

          So why procd? What does it do better/differently?
          See my post in the previous discussion: http://www.phoronix.com/forums/showt...431#post429431

          Comment


          • #6
            Originally posted by Zajec View Post
            See my post in the previous discussion: http://www.phoronix.com/forums/showt...431#post429431
            So to summarise:

            Why not systemd:
            -too heavy
            -to tightly integtraded with other stuff

            What is procd:
            -reload, process tracking etc.
            -scripts only send stubs
            -somehow plays an important role in applying configuration to the services without knowing any state

            For the systemd part -> There are some people who are running systemd on openwrt but I am not sure if they are using the smallest openwrt devices or not.

            And for procd -> basically systemd without all the bells and whistles but also adds some configuration management into the mix?
            I really did not understand that he meant by "the restart everything if something changed". Isn't this what systemd (and sysV btw) do already?

            I still would like some more information beside a old chat log. Will there be something like procdctl? Or something else? I have not the slightest idea?

            Comment


            • #7
              I built from the barrier_breaker branch a couple of days ago. Wonder if I missed any changes. This is my first time trying OpenWRT on an ALIX board. I've used a very cut-down configuration but it's working perfectly. Very pleased.

              Comment


              • #8
                Very nice distro for routers!

                My favorite distro when it comes to routers. And finally they ditched their awful bunch of shell scripts in favor of something small and light and far easier to change. Procd is something like systemd which is implemented in small and compact way, suitable for embedded system. Smaller system bus - ubus, smaller libs, lighter procd. Looks really promising to my taste.

                And I really love their sense of humor:
                "Of course, NetworkManager should be renamed to "unetwork", dbus to "ubus", PulseAudio to "usound", and X.Org-Server/Wayland-Compositor to "udisplay"; and then indescribable happiness would come down to all people of this world." ? Lennart Poettering
                Shamelessly stolen here.

                Comment


                • #9
                  Originally posted by xeekei View Post
                  Well, systemd doesn't support Musl, so that wasn't even an option.
                  well, nobody cares about musl, so that's irrelevant
                  what is relevant is that they need to fit whole distro into 4 megabytes of flash, which is not systemd's target audience.

                  Comment


                  • #10
                    Originally posted by pal666 View Post
                    well, nobody cares about musl, so that's irrelevant
                    what is relevant is that they need to fit whole distro into 4 megabytes of flash, which is not systemd's target audience.
                    Correction: They need to fit a full functioning system into 4 MB of flash. They certainly can't fit the *whole distro*, since all of the add-on packages (which are part of the distro) certainly won't fit and add up to hundreds of MB.

                    Comment

                    Working...
                    X