this post was submitted on 13 Jan 2025
278 points (98.9% liked)

linuxmemes

21877 readers
886 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] partial_accumen 2 points 6 days ago (1 children)

    It is more like ‘involuntarily end up riding the risks of using unsupported old software’.

    Involuntarily? An org choosing to use an EOL OS to keep running an application is a business choice that accepts the risk of compromise/lack of support of an EOL OS. Any org in this situation has 3 choices:

    • deprecate the application entirely closing down that line of business the application was supporting
    • rewrite/replace the application to maintain the line of business on a modern supported OS
    • continue to run the EOL OS and accept the risks

    There's nothing involuntary here.

    [–] akash_rawal 1 points 6 days ago (1 children)
    1. Struggle to come to a conclusion on what to do with the EOL OS because of internal political factors and the reality of how enterprise works.

    This is the involuntary choice. If you cannot choose from the first three, you end up implicitly choosing the fourth.

    [–] partial_accumen 1 points 5 days ago* (last edited 5 days ago)

    Your #4 is the same as my #3. Play out your #4 and it ends up as my #3:

    1. Struggle to come to a conclusion on what to do with the EOL OS because of internal political factors and the reality of how enterprise works.

    Security or Compliance teams raise the concern with continuing to run the EOL OS, they demand the App team power down the offending servers or upgrade. App team escalates to leadership advocating for the upgrade and they ask for the funding. Leadership asks for a business case justifying the large spend requiring the ROI numbers. App team mostly shrugs because the ROI are intangibles of security or support-ability. Leadership sees no immediate monetary benefit being realized in the next 2 quarters from a costly upgrade and instead chooses to accept the risk. They send an exception order to Security or Compliance teams that this EOL OS should continue running as is and the App team shouldn't be bothered anymore.

    ...and we end up with my #3.