Announcement

Collapse
No announcement yet.

Apple's OS X Launchd Being Ported To FreeBSD

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

  • Apple's OS X Launchd Being Ported To FreeBSD

    Phoronix: Apple's OS X Launchd Being Ported To FreeBSD

    There is new work within the FreeBSD camp to port Apple's launchd from OS X to non-Darwin systems...

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

  • #2
    Wonder if they'll port to OpenBSD, NetBSD, DragonFly BSD too?
    Perhaps even Linux?

    Comment


    • #3
      Isn't launchd like systemD? If so, why not port the latter since Gnome and probably soon other software will depend on systemD?

      Comment


      • #4
        Originally posted by mark45 View Post
        Isn't launchd like systemD? If so, why not port the latter since Gnome and probably soon other software will depend on systemD?
        Because systemd is at the moment (and probably will ever be) Linux-only and is also licensed GPL (LGPL v2.1). "launchd" on the other hand is taylored for a BSD-style system (OS X) and is "Apache License" licensed. The latter is much more preferable for FreeBSD. Remember FreeBSD ditched GCC in favour of LLVM mainly because of the license.

        Comment


        • #5
          AFIK systemD was developed because launchd couldn't coexist with legacy sysV init (and they didn't like Upstart), so porting it to FreeBSD could turn out to be a major task.

          Comment


          • #6
            Good since FreeBSDs current init system sucks monkey balls. It's the most slow thing I have ever used in my life. You totally forget that you have a SATA 3 SSD installed. My Arch Linux installation is able to boot faster than FreeBSDs init is able to set the hostname. I'm not kidding.

            It's systemd btw not Sytemd or SystemD or systemD.

            Comment


            • #7
              Could this be the break Debian needs in relation to their init system conundrum with kFreeBSD as a Debian variant?

              Comment


              • #8
                So, sysv init is now a bad guy for bsd?

                Comment


                • #9
                  Good news for the BSD guys

                  Comment


                  • #10
                    Originally posted by glasen View Post
                    Because systemd is at the moment (and probably will ever be) Linux-only and is also licensed GPL (LGPL v2.1). "launchd" on the other hand is taylored for a BSD-style system (OS X) and is "Apache License" licensed. The latter is much more preferable for FreeBSD. Remember FreeBSD ditched GCC in favour of LLVM mainly because of the license.
                    It was about control, license restrictions and design goals.

                    The world is better off with LLVM/Clang in it. It's what has gotten GCC to evolve.

                    Comment


                    • #11
                      Originally posted by Pawlerson View Post
                      So, sysv init is now a bad guy for bsd?
                      FreeBSD never used sysvinit. sysvinit is a clone of the init system used in UNIX System V. FreeBSD inherited bsdinit from its precusors (BSD 4.3 and 4.4-Lite).

                      With regards to running launchd on other platforms-- the port is currently focusing on isolating all parts of launchd that rely on OS X's Mach microkernel API. With those no longer a prerequisite a port to other BSDs and Linux would be fairly simple.

                      Comment


                      • #12
                        Originally posted by blackout23 View Post
                        Good since FreeBSDs current init system sucks monkey balls. It's the most slow thing I have ever used in my life. You totally forget that you have a SATA 3 SSD installed. My Arch Linux installation is able to boot faster than FreeBSDs init is able to set the hostname. I'm not kidding.

                        It's systemd btw not Sytemd or SystemD or systemD.
                        I think this plays into the aura of BS that surrounds the FreeBSD community. They constantly claim that their OS is "faster" than Linux, while the benchmarks claim otherwise. Even without systemd, sysv easily beats the pants off bsdinit. A recent interview with Marshall Mckusick shows just ignorant their leaders are. He claimed that "Windows teaches you to tolerate BSODs three time a week, so one time a week is welcome news". This is absolute horses***. I've been using Windows in home and office for a decade, on many machines, and I barely get one BSOD a year. The last time I got a BSOD that was not hardware related was three years ago for a GPU driver update.

                        Comment


                        • #13
                          Originally posted by garegin View Post
                          I think this plays into the aura of BS that surrounds the FreeBSD community. They constantly claim that their OS is "faster" than Linux, while the benchmarks claim otherwise. Even without systemd, sysv easily beats the pants off bsdinit. A recent interview with Marshall Mckusick shows just ignorant their leaders are. He claimed that "Windows teaches you to tolerate BSODs three time a week, so one time a week is welcome news". This is absolute horses***. I've been using Windows in home and office for a decade, on many machines, and I barely get one BSOD a year. The last time I got a BSOD that was not hardware related was three years ago for a GPU driver update.
                          Is sysvinit really faster than bsdinit? I'm pretty sure all init systems I've seen finish in about 2 seconds flat (on a 5400RPM hard drive no less). As for the interview, well, that kind of claim is something I expect from most FOSS prononents, whether Linux, BSD, or something else.

                          Comment


                          • #14
                            Originally posted by JX8p View Post
                            Is sysvinit really faster than bsdinit? I'm pretty sure all init systems I've seen finish in about 2 seconds flat (on a 5400RPM hard drive no less). As for the interview, well, that kind of claim is something I expect from most FOSS prononents, whether Linux, BSD, or something else.
                            It allows concurrent boot, so yes, its faster. Its also not much different from BSD init, one got links, other text entries. The only case where BSD init might win is slow file open operations.

                            Comment


                            • #15
                              Originally posted by JX8p View Post
                              Is sysvinit really faster than bsdinit? I'm pretty sure all init systems I've seen finish in about 2 seconds flat (on a 5400RPM hard drive no less). As for the interview, well, that kind of claim is something I expect from most FOSS prononents, whether Linux, BSD, or something else.
                              my hunch is that the slowness has to do with poor hardware support/optimization. on some computers Linux boots unnaturally slow too. Usually those are funky firmware handoff bugs. The slowness I encounter is usually in the early stages of boot which confirms my theory. I've had a vanilla install of pfsense take twice longer to boot than a full install of Fedora with Gnome.
                              At the end of the day, money talks and BS walks. If FreeBSD was superior to Linux, it's server marketshare wouldn't have been so terrible. And you can't give the "people just haven't heard of it" argument, because every Linux admin I have met has heard of FreeBSD and even played with it. Back in the early 90s FreeBSD actually had a lead over Linux, because the later was extremely immature (early Debian, Slackware), while the former was tried and tested for more than a decade (FreeBSD was just BSD without the AT&T bits)

                              Comment

                              Working...
                              X