Slashdot Mirror


A FreeBSD "Spork" With Touches of NeXT and OS X: NeXTBSD

There are a lot of open source operating systems out there; being open source, they lend themselves to forks, clones or near clones, and friendly offshoots. There are even services to let you customize, download, and (if you choose) bulk-install your own OS based on common components. Phoronix notes a new project called NeXTBSD that might turn more heads than most new open source OSes, in part because of the developers behind it, and in part because of the positive thoughts many people have toward the aesthetics of NeXTSTEP and Mac OS X. (And while it might be a fork of FreeBSD, the developers would rather call it a spork, instead.) NeXTBSD was announced last week by Jordan Hubbard and Kip Macy at the Bay Area FreeBSD Users Group (BAFUG). NeXTBSD / FreeBSD X is based on the FreeBSD-CURRENT kernel while adding in Mach IPC, Libdispatch, notifyd, asld, launchd, and other components derived from Apple's open-source code for OS X. The basic launchd/notifyd/asld/libdispatch stack atop their "fork" of FreeBSD is working along with other basic components of their new design. You can watch a recording of the announcement as well as a longer introduction linked from Phoronix's story.

79 of 165 comments (clear)

  1. Hmm... by EmeraldBot · · Score: 5, Interesting

    Kind of interesting. From what I gather it's supposed to be the unstable rolling release branch of FreeBSD (-CURRENT), which presumably some Apple enhancements? Maybe the interface? I don't know, they're rather vague with what their ultimate goal is. The progressive part sounds like they intend for this to be something like Arch for Linux, but -CURRENT is not exactly a bastion of stability. It's the beta branch. Users won't want it because it's too unstable, and all the extras are going to make it unappealing for testing, I think. A neat idea, but I think this would be much better off if pulled from -STABLE or better yet, -RELEASE. THEN we'd have something quite interesting on our hands.

    --
    "Set a man a fire, he'll be warm for the rest of the night. Set a man afire, he'll be warm for the rest of his life."
    1. Re:Hmm... by Anonymous Coward · · Score: 5, Informative

      The targeted usecase is FreeNAS, and previous presentations by Jordan Hubbard made clear that he want to restructure the project to better manage daemons and configuration. Don't expect any graphical display stuff, they are from the proprietary stuff from apple, the only things that can be imported are bits from Darwin. Expect at some point wayland port depending on how much upstream is deep in their little linux world, but I don't think that'll come from a iXsystems. Expect maybe some graphical stuff from the lumina project, but not a complete DE like KDE, Gnome or MacOSX (more likely a nice "lightweight" Qt desktop).

    2. Re:Hmm... by myowntrueself · · Score: 1

      The targeted usecase is FreeNAS, and previous presentations by Jordan Hubbard made clear that he want to restructure the project to better manage daemons and configuration.

      Don't expect any graphical display stuff, they are from the proprietary stuff from apple, the only things that can be imported are bits from Darwin.

      Expect at some point wayland port depending on how much upstream is deep in their little linux world, but I don't think that'll come from a iXsystems. Expect maybe some graphical stuff from the lumina project, but not a complete DE like KDE, Gnome or MacOSX (more likely a nice "lightweight" Qt desktop).

      Ohhhh so its going to be systemd for BSD?

      --
      In the free world the media isn't government run; the government is media run.
    3. Re:Hmm... by wkcole · · Score: 5, Informative

      Ohhhh so its going to be systemd for BSD?

      Yes and no.

      Some of the legacy Unix issues that systemd is supposedly intended to address have been attacked by Apple in the tools NeXTBSD is adopting: ASL, LaunchD, GCD/LibDispatch, NotifyD, etc. Note that unlike systemd, the Darwin replacements for traditional init, cron, & syslog aren't monolithic and are relatively mature. LaunchD & ASL have been evolving for over a decade in mass-market OS releases and it is apparent to anyone using them attentively in MacOS over that time that Apple has been working to make them actual improvements for admins and developers interacting with them over the legacy tools, rather than merely replacements. They were both problematic in their earliest releases, but they both have been developed over time to the point where they no longer seem like the products of CS theoreticians who've never managed real systems.

      Beyond that, I think it is safe to assert that there is MUCH more well-earned community goodwill towards Hubbard & Macy than there ever has been or ever could be for Poettering, so the social drama isn't preset for tragedy in the event that the project is unremarkable for a while.

    4. Re:Hmm... by JPyObjC+Dude · · Score: 1

      When I read the description, I saw the exact same thing as It sounded just like the discussion points for the upcoming FreeNAS 10. Its so wicked that Jordan now works for iXSystems :)

      The new iXSystems FreeNAS 10 platform would be a great foundation as a general application server platform. I'm not sure how well it would behave as a desktop OS. You sure cannot go wrong with root ZFS though, which is something that is not trivial on linux.

    5. Re:Hmm... by caseih · · Score: 1

      Systemd is not monolithic. It's highly modular and only a few small parts are mandatory for systemd's init to function. Saying systemd is monolithic does not make it so.

      As for the evolution of launchd and it's current usability, the same exact things can be said of systemd. systemd is not a creation of theoretitists. It actually solves practical problems in a practical way, as does launchd.

      It's just ironic to me that slashdotters will come to launchd's defense while lambasting systemd.

  2. Will it run Windowmaker? by Anonymous Coward · · Score: 1

    Afterstep? Or utilize Enlightenment for that composited OSX feel?

  3. Would love a modern NeXTstep by jregel · · Score: 4, Interesting

    I'd love to see a desktop OS that builds on what NeXT did. I know Mac OS X is that to some degree, but I'm thinking of something more like the original NeXTstep GUI.

    It's somewhat ironic that when GNUstep first started, one of the reasons why it didn't get much traction was the use of the "non-standard" Objective-C. As a result, effort was instead spent on KDE and then GNOME. If GNUstep became the standard, it could have changed Linux on the desktop as porting Mac OS X apps over would have been much easier. Of course, no-one knew that then.

    1. Re:Would love a modern NeXTstep by laffer1 · · Score: 5, Interesting

      That's why I started MidnightBSD. I just didn't keep enough developers around after the initial push to finish it.

      I've been looking at their code for a few weeks (it was in the trueos repo on a branch) and it's rather interesting. The Mach IPC layer is actually a port from code in NetBSD up to around 5.0. Then they've brought in patches for libdispatch workqueue support and a bunch of apple code.

    2. Re:Would love a modern NeXTstep by swell · · Score: 2

      This appears to be the vision of a very small number of developers. One? Of course they welcome help but the single vision is important.

      A person I greatly respected (my mommy) used to say, when she saw an ugly building, "It looks like it was built by a committee."

      Have you ever noticed this effect in a software project?

      --
      ...omphaloskepsis often...
  4. Re:Use-case? by ChunderDownunder · · Score: 2

    Apple are no longer interested in maintaining xnu/darwin and see strategic benefits from re-basing iOS and OS/X upon FreeBSD?

  5. NeXT by pr0nbot · · Score: 1

    I'd assume Apple still owns the trademark for NeXT, so I expect they'll rename it if it gets any traction.

    Maybe NextBSD or nxBSD or something wouldn't fall foul of the trademark?

    1. Re:NeXT by ChunderDownunder · · Score: 1

      it's a crappy name designed to create confusion with NetBSD in any case.

    2. Re:NeXT by Anonymous Coward · · Score: 1

      Just like everyone knows that XWindows and Windows are so easy to confuse.

    3. Re:NeXT by Anne+Thwacks · · Score: 2

      I vote for "Backstep"

      --
      Sent from my ASR33 using ASCII
    4. Re:NeXT by Anonymous Coward · · Score: 1

      You mean that Apple is a trademark of NeXT.
      Apple was sold for very cheap to NeXT, I mean it is the CEO of NeXT with their flagship product NeXTStep but renamed Apple and OS X.

    5. Re:NeXT by hummassa · · Score: 1

      it's XWindow

      --
      It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
    6. Re:NeXT by myowntrueself · · Score: 1

      An ancient FAQ written by users is hardly authoritative, but if you accept those kind of credentials:

      X was named after an earlier window system called "W". It is a window system called "X", not a system called "X Windows".

      I've always referred to it as 'The X Window system'

      --
      In the free world the media isn't government run; the government is media run.
    7. Re:NeXT by Blaskowicz · · Score: 1

      It's X11. No, it's Xorg. Wait, it's X11 since there are a few non-Xorg systems. Wait, if you run it raw it doesn't manage windows so perhaps that's why it is an "X Window system".

    8. Re:NeXT by Pikoro · · Score: 1

      FreeBastard or NextBastard

      --
      "Freedom in the USA is not the ability to do what you want. It is the ability to stop others from doing what THEY want"
  6. Doesn't this already exist? by nathana · · Score: 1

    Why not just run / fork (okay, fine, "spork") Darwin?

    -- Nathan

    1. Re:Doesn't this already exist? by Anonymous Coward · · Score: 1

      They are FreeBSD users and developers that want to push the FreeBSD ecosystem further than the Current branch is able to go. They don't want a new kernel that works like Apple's OS X, they want a modernized in it that keeps the UNIX principles firmly in mind, while paving the way for mobile form factors and many others.

  7. Re:Use-case? by Anonymous Coward · · Score: 3, Funny

    NetCraft wanted to confirm a fresh, new BSD corpse.

  8. adding Libdispatch, notifyd, asld, launchd... by Anonymous Coward · · Score: 5, Funny

    Systemd can replace all of that.

    1. Re:adding Libdispatch, notifyd, asld, launchd... by Anonymous Coward · · Score: 2, Insightful

      You're getting it whether you like it or not!

    2. Re:adding Libdispatch, notifyd, asld, launchd... by fnj · · Score: 1

      You're getting it whether you like it or not!

      No I'm not. I'm running FreeBSD.

  9. OpenSource NeXTSTEP == Apple Darwin by Anonymous Coward · · Score: 1

    Wait, didnt' Apple open source the base OS as Darwin?

    1. Re:OpenSource NeXTSTEP == Apple Darwin by Bing+Tsher+E · · Score: 3, Interesting

      Apple killed Darwin. I ran it for a little while, though I prefer NetBSD. Darwin wasn't very interesting compared to an OS that has a vibrant active user/developer community.

    2. Re:OpenSource NeXTSTEP == Apple Darwin by guruevi · · Score: 1
      --
      Custom electronics and digital signage for your business: www.evcircuits.com
  10. launchd not as bad as systemd by drinkypoo · · Score: 1

    But also nearly universally reviled.

    Why does everyone care about saving five seconds during boot that will be completely overshadowed by the time you spend in BIOS POST?

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    1. Re:launchd not as bad as systemd by Blaskowicz · · Score: 1

      Haven't used a UEFI system?
      The other day, there was a forum thread by a guy who had assembled a new PC and thought that it didn't work. The thing went so quick as to not show anything on the display then monitor would get put on stand by. You pretty much have to mash keys before turning the thing on to get in the setup screen.

    2. Re:launchd not as bad as systemd by _merlin · · Score: 2

      He obviously has no option ROMs. I have to wait through the LSI SAS controller, Chelsio NIC, Intel management engine and Broadcom network boot option ROMs booting and displaying their messages before my workstation can start loading an OS.

    3. Re:launchd not as bad as systemd by Anonymous Coward · · Score: 1

      But also nearly universally reviled.

      Why does everyone care about saving five seconds during boot that will be completely overshadowed by the time you spend in BIOS POST?

      Because Cloud.

    4. Re:launchd not as bad as systemd by m4rtink · · Score: 1

      But also nearly universally reviled.

      Why does everyone care about saving five seconds during boot that will be completely overshadowed by the time you spend in BIOS POST?

      Um, ever heard about containers, cloud images, disposable VMs, instant-on embedded appliances, etc. ?

    5. Re:launchd not as bad as systemd by drinkypoo · · Score: 3, Interesting

      Um, ever heard about containers, cloud images, disposable VMs, instant-on embedded appliances, etc. ?

      None of which require the full suite of services which cause boot to be so slow. None of which will boot faster with launchd because the limited set of services depend on one another and so have to be started serially anyhow. None of which we are talking about right now, since we're discussing a desktop OS. None of which is relevant right now, so why did you bother?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:launchd not as bad as systemd by Anonymous Coward · · Score: 1

      I remember Steve Jobs found it important to save 5 seconds on the boot of one of the first Apple machines, because you save lives.

      Say that there are about 10 M people who have OS X. Each reboots their machine once a month (because everyone is using standby these days). That is 10 M * 5 seconds * 12 = 3 Gs.

      If you then look at how many seconds someone lives for 75 years. 3Gs / (75*365*24*60*60) = 1.26 lives per year saved.

    7. Re:launchd not as bad as systemd by U2xhc2hkb3QgU3Vja3M · · Score: 2

      If we think that way then videogames are killing millions of people every day.

    8. Re:launchd not as bad as systemd by laffer1 · · Score: 2

      It isn't about saving 5 seconds at system startup. People use that as an excuse because it's user visible. People constantly complain to me about MidnightBSD boot speed though. The real reason to do launchd (or maybe the one good thing about systemd) is that it allows you to make intelligent power decisions. If you know you're running on battery, you can avoid running background tasks that take a lot of CPU or disk IO. For example, the locate database could be updated next time you're plugged in. You could turn off services that are not needed when traveling.

      If you had intelligent events sent as messages throughout the system, you could change graphics modes on low battery or tweak settings on wifi. If you think about it, OS X and Windows both act differently depending on power modes. It could all be done automatically. You can't build a good desktop OS without these features. They also have some value on servers when running on UPS backup, etc.

    9. Re:launchd not as bad as systemd by drinkypoo · · Score: 2

      I remember Steve Jobs found it important to save 5 seconds on the boot of one of the first Apple machines, because you save lives.

      How about a computer that doesn't need to reboot so often? I used most of the early Apple machines, Apple I and /// aside, including the ][gs, Lisa, Macintosh 512k (sorry, missed the 128k) and Plus, I think I still have a SE with an accelerator in it just for the nostalgia value, had a IIci, etc etc. And I've had a lot of free reboots, most of them from Macs, and most of those reboots occurring between the era when Macs started getting MMUs, and when they started actually using it.

      The Amiga would be done booting up while the Mac was still thinking about whether the mac was happy or sad... You had to reboot it a lot, but at least it genuinely rebooted quickly. Especially if you had "a lot" of RAM, by which I mean an extra MB or so. Then you could put the whole OS (ROMs aside) into a recoverable ramdisk... talk about a quick boot.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:launchd not as bad as systemd by Moridineas · · Score: 2

      If you watch the last 20 minutes or so of the BAFUG video, Jordan Hubbard talks about launchd. I don't believe that boot time comes up a single time as a reason for making the switch.

    11. Re:launchd not as bad as systemd by Billly+Gates · · Score: 1

      But but its not init!!! Get out the tar and feathers

    12. Re:launchd not as bad as systemd by PPH · · Score: 1

      allows you to make intelligent power decisions.

      init run levels. Old news.

      --
      Have gnu, will travel.
    13. Re:launchd not as bad as systemd by PPH · · Score: 1, Flamebait

      It's not about saving 5 seconds. Its about not having a registry. Windows users and admins are stamping their little feet because no registry. And its about writing and installing start/stop scripts. Shell scripts. Windows doesn't have (practical) shell scripts. Windows is not made up of lots of little single purpose utilities than can be piped together, call other shell scripts or executables, handle I/O and return values. And all without having to worry about whether the utility was implemented as a binary executable or a script. And you can read and process logs (text logs) using shell scripts. You can raise alarms or run special handlers based on the contents of those logs.

      If the goal of systemd creators is to slowly move users back to Windows, these are all capabilities that need to be eliminated. So UNIX/Linux users can't use them as reasons not to move.

      --
      Have gnu, will travel.
    14. Re:launchd not as bad as systemd by laffer1 · · Score: 1

      Run levels don't solve the problem for desktop users. You can't ask a typical user to manually switch run levels. Not to mention rc.d in freebsd isn't setup like that.

    15. Re:launchd not as bad as systemd by Anonymous Coward · · Score: 1

      Launched is NOT about speeding up boot, it is about a highly reliable daemon dependency system, which allows keeping running process to the minimum, and allows new events to register themselves i8n a uniform manner that is simple and doesn't introduce the complexity not SystemD. It is also production proven in both he mobile space a it is on every iPhone ever shipped, as well as all OS X systems in the last five+ years.

    16. Re:launchd not as bad as systemd by squiggleslash · · Score: 1

      Honestly, you can't rebut someone's point about a feature of systemd simply by stating a random, completely unsuitable, feature of init. Arguments don't work that way. To rebut something you need to actually deal with your opponent's argument.

      BTW init sucks. systemd isn't perfect, but at least it isn't init.

      --
      You are not alone. This is not normal. None of this is normal.
    17. Re:launchd not as bad as systemd by PPH · · Score: 1

      stating a random, completely unsuitable, feature of init.

      But the parent poster stated:

      you could change graphics modes on low battery

      that's all supported by init. From the init man page:

      If init is not in single user mode and receives a powerfail signal
      (SIGPWR), it reads the file /etc/powerstatus. It then starts a command
      based on the contents of this file:

      F(AIL) Power is failing, UPS is providing the power. Execute the powerâ€
      wait and powerfail entries.

      O(K) The power has been restored, execute the powerokwait entries.

      L(OW) The power is failing and the UPS has a low battery. Execute the
      powerfailnow entries.

      My laptop has co-opted these modes for line/battery/low battery conditions. The screen backlight and blanking are controlled by power state, as well as an orderly shutdown on a low battery. Not exactly the original intent of these signals (which was UPS status handling for servers). But smart people who can read man pages got it to work quite nicely. Without systemd or launchd. So, no. Its neither random nor unsuitable.

      --
      Have gnu, will travel.
    18. Re:launchd not as bad as systemd by exomondo · · Score: 1

      If the goal of systemd creators is to slowly move users back to Windows, these are all capabilities that need to be eliminated. So UNIX/Linux users can't use them as reasons not to move.

      Yes it's all a big conspiracy! Red Hat isn't actually a supporter of Linux, despite being one of the top contributors to the Linux kernel and creating and supporting client and server distributions of Linux systems from which most of their revenue is derived they are actually trying to destroy Linux and drive people to Windows so they can kill their own business and profitability!

    19. Re: launchd not as bad as systemd by _merlin · · Score: 1

      I kinda do have to boot from my SAS controller - that's how my disks are attached. But even if you aren't booting from them, you need to wait for them. Each of these cards has an embedded computer on it and you have to wait for that to be booted and configured before you can get into a state where you're ready to let an OS loose on the host machine.

    20. Re:launchd not as bad as systemd by adolf · · Score: 1

      Then you could put the whole OS (ROMs aside) into a recoverable ramdisk... talk about a quick boot.

      I've heard of this trick, though I never owned an Amiga or any manner of useful Apple (though there is ostensibly a useless pizza-box-shaped Mac over there on the table, and an example of the Last Hoorah of the PPC 24" iMacs working fine and being useless in my garage waiting for me to figure out how to ship it because they're still valued at hundreds of dollars, but not to me because it largely fails at Spotify and Youtube, which are two things I need from a fixed PC in my garage.).

      It was certainly a clever hack: A loader that linearly (FAST!) loaded the OS into a RAM disk, and then booted from that RAM disk, and then would pivot back to the disk and free the RAM it was using.

      Folks don't do anything clever like that anymore.

      I remember scoring a 2MB EMS card (an Everex card that would use Intel drivers) for an XT that I ran a BBS from, and then scoring the 72 individual DIP RAM modules to populate it. Half was used as a RAM drive; frequent and generally read-only boot and BBS stuff would live there. I even toyed with optimizing it: Some of the TSRs would load overall-faster from the RAM disk, but once loaded they were resident so they could be flushed to make room for other things that would be used later. The other half was disk cache, at a time when disk cache was a thing that wasn't often done. The rest of the machine lived within its 640k of base memory.

      Optimizing, tweaking. Pushing the edge to get booting faster, and regular operations going faster. I miss that.

      Nowadays, we (or at least I) just throw parts at the problem:

      Oh, your machine boots slowly? Here, try this SSD.

      You're having a hard time switching between big programs? Here, let me plug in an extra >half-dozen gigabytes of RAM.

      The answers these days are so easy, and so much less rewarding. (I should be able to chooch that G5 iMac in my garage into the modern world, but it's been forgotten for the purposes I want it for.)

    21. Re:launchd not as bad as systemd by drinkypoo · · Score: 1

      1986 Amiga 1000 booting - 15 seconds from power to disk prompt, over 60 seconds to usable desktop

      That's the worst case, not using the means I described above. You may try again when you learn to read, not until.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    22. Re:launchd not as bad as systemd by drinkypoo · · Score: 1

      Okay, show me your video. I don't doubt it's fast, but there's no way it's faster than the Happy Mac icon.

      I dunno, I've had some inexplicable waits for that icon to show up. It just doesn't show up as quickly as you suggest every time. And I've used a very broad range of Macs, they were just sneaking into the schools while I was being forced to be in them, but I also come from Santa Cruz which is a very nerdy college town, and also full of liberal arts and graphic arts and whatnot and thus full of macs.

      The only Amiga I have handy to make a RRD on is an A1200. It's kind of too new, it might invalidate the point. But if you insist, I'll see if it still powers up. I have a DV Bridge so I can get video into my PC, in theory. Hmm, and a camcorder with the same functionality, now I think of it.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  11. Re:Use-case? by jellomizer · · Score: 1

    The direction that a project is going, is further away than where you want it to go.

    Lets consider Android vs. GNU/Linux (Now I personally hate calling Linux "GNU/Linux", but I need to differentiate it ). They both use the Linux kernel, but the rest of the Operating systems are very different.
    Android was forked so it can better suit a mobile system market. GNU/Linux was more towards the server and workstation.
    As Android uses more direct frame-buffer technology, GNU/Linux focuses around X windows.
    Android doesn't need to detect every piece of hardware, GNU/Linux does.
    Android expect more gestures for its control, GNU/Linux is more keyboard and mouse.

    Now on the BSD level. That is mostly server vs server, so the needs are not as large. However there is a fair amount of discussion on how defaults should be setup, what type of hardware should be supported, as moving to a virtual environments how many tasks needed to be running optimally....
     

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  12. Funny. by Runaway1956 · · Score: 1

    I downloaded the ISO on Friday night. Yesterday, I installed it ot a VM. Just got out of be a few minutes ago, and the VM is open in my right hand display, waiting for me to configure it. The network works right - I pinged Google from it. That's about all I know right now, since I've never installed a BSD before. I need to refer to some installation and setup guides next!

    --
    "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    1. Re:Funny. by Bing+Tsher+E · · Score: 2

      One time I installed NetBSD on a box and configured and used it as my desktop machine. A few weeks later I needed to reboot it and was confused why it didn't have a hostname. It turned out that it was because I had installed it, done the first boot after install, and configured everything, but had never booted it a second time and had forgotten to add a hostname in the /etc/rc.d/rc.conf file. In other words it ran for weeks as a useful desktop machine but had only been booted a single time.

      NetBSD is that easy to install, configure, and use, if you understand the classic startup sequence for BSD UNIX.

    2. Re:Funny. by c4757p · · Score: 1

      Am I just stupid, or is their website crap? I couldn't find any indication that there is an ISO, let alone download one.

    3. Re:Funny. by Runaway1956 · · Score: 1

      Yeah, the website is pretty crap. It took a bit of perseverance to actually grab the ISO. Want the link?
      $ wget http://www.optimcloud.com/disc...

      So far, I've installed bash, and configured it as my default shell, then installed nano, and configured as default editor. One step at a time, if/when I feel like it, I should have a working system before 2115 . . . .

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
  13. More Accurately DarwinBSD by tomxor · · Score: 1

    ... but that name was taken

    I was thinking something similar, and to be fair it is called "NextBSD" but as far as i can tell from the GitHub repo it's some combination of FreeBSD and Darwin, the open-source base system that OS X runs on top of. I think the Next name just fit well.

    Maybe this one will be more successful than the previous short lived attempts to make the Darwin sources into something useful... I'm not sure what exactly they are doing that is different though.

  14. Re:Use-case? by Eunuchswear · · Score: 5, Funny

    systemd envy.

    --
    Watch this Heartland Institute video
  15. Re:Hail! by Anonymous Coward · · Score: 1

    He knows what is best for us. Unix was broken so he is fixing it.

  16. Mach messages vs sysv messeges by halfdan+the+black · · Score: 1

    How exactly are Mach messeges different from sysv messeges in Linux? I've used Mach messeges before, but sysv messeges look pretty similar

    1. Re:Mach messages vs sysv messeges by thogard · · Score: 2

      Mach messages are much faster than SysV but not up to the speed of Solaris doors (which have some odd security issues but drop context swtiches). The SysV streams message system is based on the SysV IPC which is based on SysV shared memory and SysV semaphores. That stuff came from the early 1980s when a 2 CPU WE32000 in a 3B20 (or 5 or 15?) was the reference design for the biggest hardware Real UNIX (TM) would run on. Since that came from AT&T who wanted to make mainframes but had to have phone switches so their semaphore system was designed to work with things like a 5ESS phone switch where doing the right thing on failing hardware was better than doing anything fast.

    2. Re: Mach messages vs sysv messeges by halfdan+the+black · · Score: 2

      The reason I'm interested is we're developing an agent based modeling language which makes very heavy use of IPC messages, so low latency and low overhead is super critical. Currently on OSX, it used Mach messages which works extremely well, I'm porting the system to Windows, and I'm using Windows ALPC messaging, http://www.zezula.net/en/prog/... Which is also working very well, it's actually very similar to Mach messages. Makes sense, as both OSX and Windows are hybrid micro/monolithic kernel OSs so it makes sense to have a fast messaging system. I'm going to port the system to Linux, but still need to research what is the lowest latency IPC system to use there. From my testing, Mach messages are faster on OSX than named pipes, I'm not sure how Linux sysv messaging compares to named pipes yet.

    3. Re: Mach messages vs sysv messeges by fnj · · Score: 1

      I would be pretty confident that shared memory using atomic compare/exchange for notification and pickup would be the fastest on any hardware/software architecture. Definitely faster than Mach messages I would assume. Rather primitive, though. I would benchmark both named pipes and unix domain sockets as well, because they are architecturally nice.

    4. Re: Mach messages vs sysv messeges by halfdan+the+black · · Score: 1

      Yes, shared memory for data transfer is the fastest, no copying and nothing goes through the kernel. I'm looking into what would be the fastest in terms of lowest latency for notifications, i.e. signaling another process. I'm kind of surprised that there's not a lot of benchmarks of posix messages vs unix domain sockets vs pipes out there.

  17. Re:Use-case? by Bing+Tsher+E · · Score: 1

    I wouldn't call Android a 'fork' of Linux. Linux is just a kernel, a plug-in component used in many different operating systems, i.e. Debian, Slackware, SuSE, Ubuntu. Android didn't 'fork' from any of those operating systems. It just incorporated the Linux kernel. It isn't a linux 'distribution' because it's for the most part a unified whole, not a dogs-breakfast of misc. userland programs from all over, which is what most (all?) of the operating systems that call themselves 'Linux' are.

  18. Re:Will it include systemd? by armanox · · Score: 4, Informative

    No systemd - they're using Apple's launchd instead.

    --
    I'm starting to think GNU is the problem with "GNU/Linux" these days.
  19. Re:Wait, what happened to GNU OpenStep? by Anonymous Coward · · Score: 1

    Do you mean GNUStep? It's alive and kicking.

    The GNU has most of the stuff to make NeXTSTEP now, but nothing is quite right.

    * GNUStep
    * GNU Mach
    * GNU HURD
    * GWorkspace ...

    Richard Stallman was obviously trying to copy NeXT for a very long time.

  20. About time by ArchieBunker · · Score: 1

    My job keeps buying these shitty Gateway boxes and they used to have the slowest BIOS on the planet. I mean a good 15 seconds by the time it gets to the OS.

    --
    Only the State obtains its revenue by coercion. - Murray Rothbard
  21. Re:Use-case? by ShanghaiBill · · Score: 2

    A different asshole wanted to be in charge.

    1. Jordan Hubbard was one of the original founders of FreeBSD. He didn't need to fork to be in charge.
    2. Jordan is not an asshole. He is a friendly, outgoing, and helpful person. Perhaps you have him confused with Theo de Raadt.

  22. Re:Use-case? by dgatwood · · Score: 2

    Perhaps you don't understand what the word "harbor" means. It means to give a home or shelter to someone; in this usage, it implies doing so in secret. Allowing someone to contribute code openly (not in secret) is precisely the opposite. It keeps the person talking, thus revealing that person's location, and making it easier to bring that person to justice.

    Besides, it's a bit like the ethical question of "tainted" money. If someone earns money through doing bad things, is it ethical to use that money for good? Maybe. To me, the answer comes down to whether doing so would encourage continued bad behavior. For example, it would be unethical to accept evidence obtained through an illegal search (fruit of the poisonous tree) because doing so would encourage police to ignore the legal process and get the evidence through any means necessary. But in this case, if what you described is accurate, it is one step removed from that, even. The coding wasn't gained through illegal or unethical means; accepting the code would probably not make the person more likely to do bad things in his personal life, because the two are largely unconnected aspects of the person in question.

    --

    Check out my sci-fi/humor trilogy at PatriotsBooks.

  23. Re:Use-case? by aaronb1138 · · Score: 1

    Except the part where socially, we should shun unrepentant criminals. Being allowed to continue contributing allowed Kip to belong to a community and likely gave a lot of solace and sense to him that he wasn't a "bad guy".

    One of the key points of prison time is being removed from community, much more so than lacking freedom.

  24. Re:Use-case? by dgatwood · · Score: 1

    We've seen what happens when you treat unrepentant criminals as outcasts. They remain unrepentant criminals. The recidivism rate in American prisons should be proof enough that such tactics don't work. Or take a look at countries that try to imprison the opposing forces after a civil war. Things never stabilize. Sometimes, forgiveness by others is the first step towards repentance—turn the other cheek, and all that.

    --

    Check out my sci-fi/humor trilogy at PatriotsBooks.

  25. But until it has a GUI.. by doccus · · Score: 1

    Then even people who should know better will see it as just another CLI based OS. All the "Good feelings" garnered for pre 2009 OSX and NextStep etc, were based on their human interface component. The fact in this case, however, is that there'a a huge opportunity here to create a far better interface. Something less blocky than OSX and the "Next" interface, Something with all the good improvements of Finder and Explorer, as well as all the different Linux GUIs. Something that REALLY "just works" .. like Macs used to... Now *if* that can be smoothly integrated into a solid BSD underpinning..we'd have another BeOS ;-)

  26. Re:Obligatory Bad Car Analogy by exomondo · · Score: 1

    GM saw itself as the premier auto/truck maker in this country. And yet, they made some stupid mangament and engineering decisions that are slowly leading them into the corporate graveyard.

    So you're saying the goal of these management decisions was to move people away from GM cars? I don't think so, just like RedHat's goal isn't to move users to Windows.

  27. Re:Use-case? by epine · · Score: 1

    The FreeBSD Project has a problem harboring unrepentant douche bags like Kip Macy, and also Randi Harper.

    You do know that there is such a thing as false conviction, and the standard of "repentance or permanent ostracization"—remaining in glorious effect long after punishment by the state has run its course—effectively demands the the wrongfully convicted confess to crimes they never committed, in order to have any hope of returning to productive society ever again?

    In general (absent subsequent evidence), we don't actually know who are the wrongfully convicted, or we wouldn't have convicted them in the first place.

    Sometimes (for a value of "sometimes" with no fixed address) the rush to judgment really sucks ass. That ought to give you at least a moment's pause before this kind of sentiment as an anonymous coward. It's why we allow the state to assign punishment rather than throwing blemished produce at the town pillory (e.g. a perfectly edible cucumber that's not quite straight, or harbours somewhere a small scab).

    Sure, he sounds like a royal douche. But is it really my job to see that he suffers forever-after on nothing but a thin gruel of second-hand story telling?

    Has it never occurred to you that there's a downside to your unthoughtful bitterness?

  28. Re: Happy Sunday from The Golden Girls! by Meski · · Score: 1

    It's "confidant" not "cosmonaut."

    :sigh: another newbie... and since you posted AC, so also shall i...

    Perhaps they forked it.

  29. It's perfect by morgauxo · · Score: 1

    I think this would be a perfect new home for Leonart Poetering. It's a place were he could be productive and apreciated and the rest of us could be rid of him.

  30. Re:PC-BSD is a better approach for desktop users. by Plumpaquatsch · · Score: 1

    http://itsfoss.com/97-percent-worlds-top-500-supercomputers-run-linux/

    97 Percent Of The World’s Top 500 Supercomputers Run Linux

    Percentage of Supercomputers on the Desktop: 0%.

    --
    Of course news about a fake are Fake News.