Stories
Slash Boxes
Comments

SoylentNews is people

posted by LaminatorX on Friday February 21 2014, @07:45AM   Printer-friendly
from the Gnomes-for-Theo dept.

joekiser writes:

"Antoine Jacoutot has given a status update for GNOME users of OpenBSD, including a short video. The GNOME release has been updated to 3.10.2, and auto-mounting of devices is now supported through a new helper program, toad. Now is a great time for desktop users to test the upcoming OpenBSD release. The ports tree was recently locked for stability testing ahead of the 5.5 release, meaning that recent -CURRENT builds are very close to what will be released in May. Antoine also addresses the upcoming issues non-Linux systems face with GNOME, such as the upcoming hard dependency on systemd."

[ED Note: I ran an OpenBSD router box years ago when tinkering about with an old PII with four NICs seemed worthwhile. The OS lived up to it's rep, but it never occurred to me to use it for a desktop system. Are any Soylentils using OpenBSD for a GNOME-based workstation?]

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Informative) by TheRaven on Friday February 21 2014, @02:46PM

    by TheRaven (270) on Friday February 21 2014, @02:46PM (#4329) Journal

    FreeBSD has /etc/rc.d and /usr/local/etc/rc.d, where packages can install scripts to start, stop, and control daemons. You use rc.conf to define which ones should be started (and what other arguments they're given). On OpenBSD you just have /etc/rc.local, which is a shell script. This means that there's no way for a package uninstall to remove an rc entry, so you end up having to bracket everything in tests to see if the daemon that you're trying to start exists, which means that turning on a service in OpenBSD involves copying a few lines of shell script into rc.local. In FreeBSD, you just set the {package name}_enable variable to YES and it runs. When it's uninstalled, that line is dead code, but it's just setting a variable, so it's safe (it just slows things down slightly).

    While speeding up the boot is nice, the most important reason for replacing init systems is that you want something that can be managed at scale. Adding and removing files is easy, as is running a command that (atomically) updates some structured format. Modifying a text file, especially one that contains code written in a Turing-complete language (e.g. POSIX shell), is not something that scales well when you're trying to manage thousands of machines.

    --
    sudo mod me up
    Starting Score:    1  point
    Moderation   +2  
       Informative=2, Total=2
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 0) by Anonymous Coward on Friday February 21 2014, @11:20PM

    by Anonymous Coward on Friday February 21 2014, @11:20PM (#4597)

    Running services from packages is not something you do on a regular OpenBSD system. Anything I care about can be set as a variable in rc.conf.local. Of course the article is about Gnome, so you are going to get everything and its grandmother running as an insidious service. Good luck.

  • (Score: 0) by Anonymous Coward on Saturday February 22 2014, @01:15AM

    by Anonymous Coward on Saturday February 22 2014, @01:15AM (#4646)

    Your information is out of date. OpenBSD also has scripts in /etc/rc.d, and enabling, say, saned is just a matter of setting "pkg_scripts=saned" in /etc/rc.conf.local. rc.d scripts first appeared in OpenBSD about three years ago.

    • (Score: 2) by TheRaven on Saturday February 22 2014, @10:30AM

      by TheRaven (270) on Saturday February 22 2014, @10:30AM (#4773) Journal
      Ah, thanks. I've not used OpenBSD for a few years - I had a colocated Mac Mini, which was cheaper than a VM at the time, and ran OpenBSD because it worked well on G4 PowerPC machines. Your.org gives out free VMs to FreeBSD committers now though, so I replaced that machine with an x86-64 VM running FreeBSD a few years ago.
      --
      sudo mod me up