- This topic has 5 replies, 5 voices, and was last updated Aug 25-8:42 pm by DeepDayze.
-
Posts
-
rokytnji
What the title says. So if running their repos. No more support.
Timeframe
Wheezy Long Term Support starts on 26 April 2016 and will end on 31 May 2018, five years after Wheezy’s release.
https://wiki.debian.org/LTS/Wheezy
I got the inside scoop on what might have happened to Wheezy.
- This topic was modified 4 years, 11 months ago by rokytnji.
- This topic was modified 4 years, 11 months ago by rokytnji.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problems
sleekmason
Love the joke.
I’ve been face to face with black bears a couple of times, and advise those penguins to run! Don’t even want to imagine staring up at a polar bear:) last view ya get.
–
On a more serious note, For what reason would anybody want to stick with wheezy anyway? Server use? Just wondering.DeepDayze
Love the joke.
I’ve been face to face with black bears a couple of times, and advise those penguins to run! Don’t even want to imagine staring up at a polar bear:) last view ya get.
–
On a more serious note, For what reason would anybody want to stick with wheezy anyway? Server use? Just wondering.Most likely for a server that is hosting rather old applications/services. With the end of Wheezy’s LTS support that will mean no further updates and there’s always will be new vulnerabilities found that will NEVER be patched unless some enterprising souls dig deep into the source for the kernel and manually backport patches (if possible).
In short, server admins need to plan to migrate servers (and the applications/services they host) running Wheezy to Jessie or Stretch.
Real men use Linux 🙂
fungalnet
Since enterprise server admins are likely to have done loads of work customizing init scripts and services, wouldn’t it be easier to move from wheezy to antix, mx, devuan, rather than scrap all their init system custom work and start from scratch?
anti-X - Adélie - obarun - systemd Free Space
Brian Masinick
Since enterprise server admins are likely to have done loads of work customizing init scripts and services, wouldn’t it be easier to move from wheezy to antix, mx, devuan, rather than scrap all their init system custom work and start from scratch?
It certainly WOULD be easier to use either antiX or MX for just about anything. For one thing, both of them have Debian repositories in addition to their own. Debian would provide any additional software that a server admin might want that they may not see installed by default in our distributions, but our versions have great tools for backup, administration, support, snapshots, and upgrades.
--
Brian MasinickSince enterprise server admins are likely to have done loads of work customizing init scripts and services, wouldn’t it be easier to move from wheezy to antix, mx, devuan, rather than scrap all their init system custom work and start from scratch?
It certainly WOULD be easier to use either antiX or MX for just about anything. For one thing, both of them have Debian repositories in addition to their own. Debian would provide any additional software that a server admin might want that they may not see installed by default in our distributions, but our versions have great tools for backup, administration, support, snapshots, and upgrades.
It’s possible to migrate to a new stable but there may well be gotchas that can cause issues so server admins would certainly be doing some testing before they actually make the move.
Real men use Linux 🙂
- You must be logged in to reply to this topic.
