Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 16 submissions in the queue.

Ubuntu Concedes Defeat in Upstart vs Systemd

posted by janrinok on Tuesday March 18 2014, @09:51PM   Printer-friendly
from the not-everyone-will-be-happy dept.

elias writes:

"A very public and sometimes acrimonious dispute in the Debian ecosystem about upstart versus systemd has been settled in favour of systemd. Some go as far as to brand it a new era after the Linux civil war [Beware popups].

We also had an asksoylentnews question on what the fuzz was all about. But what can upstart contribute to systemd now the war is over, or will it simply be a technology that we remember fondly, but do not see any more in a few years time?"

 
This discussion has been archived. No new comments can be posted.
Ubuntu Concedes Defeat in Upstart vs Systemd | Log In/Create an Account | Top | 41 comments | Search Discussion
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: 3, Interesting) by TheLink on Wednesday March 19 2014, @04:22AM

    by TheLink (332) on Wednesday March 19 2014, @04:22AM (#18402) Journal

    You're comparing with WINDOWS?! It's only in recent years they got preshutdown notifications compared to Unix init scripts which have been around for decades.

    AND even then it's not yet natively supported by .NET services: https://connect.microsoft.com/VisualStudio/feedbac k/details/641737/add-windows-service-preshutdown [microsoft.com]

    I've been considering writing a windows service to handle preshutdown notifications and then shutdown .NET services in an orderly manner. Maybe someone has written one already.

    As for logging, the Microsoft/Windows logging culture is below par. It's possible to log useful logs in Windows, but somehow the logging culture is such that more don't compared to the "unix/unixlike" logging culture. Perhaps due to pushes for internationalization they have made logs equally useless in all languages ;). e.g. instead of "Unable to read file: '/zzz/xxx/yyy.conf': access denied" you are more likely to get stuff like "Error [0x123]: FILE_ACCESS_DENIED".
    See also: http://support.microsoft.com/kb/307024 [microsoft.com]

    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  
    Total Score:   3  

  • (Score: 1) by Qzukk on Wednesday March 19 2014, @01:57PM

    by Qzukk (1086) on Wednesday March 19 2014, @01:57PM (#18538) Journal

    Having tried to debug a windows 8 computer that was unable to run windows update because the BITS service would not start, I can say that I never once saw an error code with the definition printed next to it anywhere in any log. Plenty of "Service failed to start with error -1892447375" or "Last error code 0x8f338b71".

  • (Score: 2) by Grishnakh on Wednesday March 19 2014, @04:12PM

    by Grishnakh (2831) on Wednesday March 19 2014, @04:12PM (#18597)

    I compared with Windows because more people are familiar with it than with something like Solaris.

    And yes, Windows logging sucks. I never said Windows was a gold standard in anything.

    Windows has a habit of taking really good ideas, and completely screwing them up with terrible implementations. Their service manager is an example of this I think. Unlike sysvinit, it'll actually tell you the current state of services (try kill -9ing mysql and seeing if sysvinit notices). But of course, the general way it's implemented sucks for many different reasons.