Announcement

Collapse
No announcement yet.

Debian Developers Take To Voting Over Init System Diversity

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

  • Terrablit
    replied
    Originally posted by monraaf
    removed post
    Could you speak a little louder, please? I don't think we could hear you over the sound of you shuffling your punch cards.

    Originally posted by monraaf
    you never reboot a linux box period
    If you're giving out this kind of advice, your opinion isn't worth the papyrus it was written on. Anyone who claims to have as much network admin experience as you should have hit their fair share of 0-day exploits by now (including kernel issues) or just got "lucky" enough to be overlooked and never bothered to learn enough infosec to be anything other than a liability in most companies. Nobody sane chases uptime scores on a machine that connects to the internet. And nobody competent gives out career advice that requires winning the lottery.

    Live kernel patching is a relatively new thing and it's rather hard to find outside of paid distro subscriptions. Which would mean that with your ancient advice, you've most likely been leaving unpatched boxes on the network for hackers and script kiddies to add to their botnets for years. Thanks for that. We probably have you to blame for some of the daily spam we get.

    It's sad because I know people in their 70s (likely older than you) who work hard to keep up with technology. Bitrot isn't constrained to digital mediums. Please try to make yourself relevant instead of holding the rest of us back with your Flintstone-era knowledge.
    Last edited by tildearrow; 12-07-2019, 01:55 PM.

    Leave a comment:


  • 144Hz
    replied
    Choice 1: F: Focus on systemd

    Bye Init Freedom!

    Leave a comment:


  • phoronix_anon
    replied
    Originally posted by microcode View Post
    There is no good reason to impose the cost of maintaining non-systemd init scripts on every Debian package maintainer, to satisfy a group of people who appear to have few or no valid practical concerns. If your init system is so great, go ahead and write the missing units/scripts for it yourself, like I did many years ago with systemd; if it's too hard for an intermediate user to accomplish that, is your init system even worth considering?
    Do you think systemd should be the only init available for containers? Do you want to see people stop using Debian-based images to build containers?

    Leave a comment:


  • Terrablit
    replied
    Let's be real. Even if there is a resolution, it doesn't mean an end to "further discussion" as we've seen. And if someone loses, they're still going to be pushing for another vote down the line. And trolling in the forums hoping that people believe their FUD.

    Might as well press FD to pay respects.

    Leave a comment:


  • microcode
    replied
    This is just sad. I had no idea there would still be people taking this ridiculous prejudice seriously so many years later. I used systemd on Debian since well before it was even part of the distribution, it was really quite good then, and now it enables like... half the important infrastructure for a decent workstation or desktop, including many things that didn't work well or at all when systemd was birthed. It isn't more memory-intensive than other init systems, it is generally faster, it is dead simple to configure, it is the default on every major distribution, it is maintained well by a dedicated team of developers.

    There is no good reason to impose the cost of maintaining non-systemd init scripts on every Debian package maintainer, to satisfy a group of people who appear to have few or no valid practical concerns. If your init system is so great, go ahead and write the missing units/scripts for it yourself, like I did many years ago with systemd; if it's too hard for an intermediate user to accomplish that, is your init system even worth considering?
    Last edited by microcode; 12-06-2019, 08:42 PM.

    Leave a comment:


  • tildearrow
    replied
    Typo:

    Originally posted by phoronix View Post
    and the interest/commiment to supporting systemd alternatives

    Leave a comment:


  • tildearrow
    replied
    Choice 9: Focus on systemd and leave the rest to Devuan

    Leave a comment:


  • Debian Developers Take To Voting Over Init System Diversity

    Phoronix: Debian Developers Take To Voting Over Init System Diversity

    It's been five years already since the vote to transition to systemd in Debian over Upstart while now there is the new vote that has just commenced for judging the interest in "init system diversity" and just how much Debian developers care (or not) in supporting alternatives to systemd...

    http://www.phoronix.com/scan.php?pag...Diversity-Vote
Working...
X