LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   End of life for 12.* (http://www.linuxquestions.org/questions/slackware-14/end-of-life-for-12-%2A-4175475294/)

vulcan59 08-30-2013 06:24 AM

End of life for 12.*
 
The changelog for 12.1 and 12.2 contains this message

Code:

Fri Aug 30 06:26:06 UTC 2013
####################################################################
# NOTICE OF INPENDING EOL (END OF LIFE) FOR OLD SLACKWARE VERSIONS #
#                                                                  #
# Effective December 9, 2013, security patches will no longer be  #
# provided for the following versions of Slackware (which will all #
# be more than 5 years old at that time):                          #
#  Slackware 12.1, Slackware 12.0.                                #
# If you are still running these versions you should consider      #
# migrating to a newer version (preferably as recent as possible). #
# Alternately, you may make arrangements to handle your own        #
# security patches.  If for some reason you are unable to upgrade  #
# or handle your own security patches, limited security support    #
# may be available for a fee.  Inquire at security@slackware.com.  #
####################################################################

Should it not be referring to 12.1 and 12.2? 12.0 reached EOL last year.

onebuck 08-30-2013 07:20 AM

Member Response
 
Hi,

I really think PV made the right decision here for EOL of 12.*. As Slackware progresses along with hardware situations/designs that do change then why provide releases for legacy hardware when the user can hopefully upgrade and use a newer release successfully.

Most members do have older hardware running a newer release of Slackware. I do have some older ThinkPads that are still running various releases of 13.

One must remember that security releases for Slackware over the years have been for a broad spectrum of earlier releases. Load of work!

No problem for me to see EOL for 12.*.

GazL 08-30-2013 07:29 AM

Quote:

Originally Posted by vulcan59 (Post 5018824)
Should it not be referring to 12.1 and 12.2? 12.0 reached EOL last year.

Yep, I think you're right. 12.0 Changelog didn't even contain a notice: it just stops in July 2012.

vulcan59 08-30-2013 07:35 AM

Quote:

Originally Posted by GazL (Post 5018844)
Yep, I think you're right. 12.0 Changelog didn't even contain a notice: it just stops in July 2012.

Actually it did. Scroll down to June 14th in the changelog.

GazL 08-30-2013 07:37 AM

My mistake. You're quite right. :)

hitest 08-30-2013 08:54 AM

Quote:

Originally Posted by onebuck (Post 5018837)

No problem for me to see EOL for 12.*.

Agreed. I am happily running Slackware 14.0 and Slackware-current on older hardware.

AlvaroG 08-30-2013 09:02 AM

It used to be a matter of nerdy pride to see how for long the Slackware releases were supported. But of course it takes a lot of work to do that, and we all want the team to work in making the current distribution work as well as possible, in a time where the Linux ecosystem is getting more and more complex. We are still getting 4 years of support considering Slack13 was released in 2009

Of course this doesn't mean that one can't run one of the old releases in old hardware. With an external firewall configured properly, the security issues for a local server are probably not going to be very important. Just for fun, one can still install Slackware 11 in that proverbial "old Pentium II lying around" we all have, just don't connect it to the internet directly (and check the RPi, it will be cheaper to run and more powerful).

Also, I don't think that right now there is a lot of working hardware that is old enough to not be able to run Slackware 13.

GazL 08-30-2013 09:13 AM

I no longer have it, but I used to have a P3-800 with 128MB ram that was just about borderline usable with Slackware 12.2 under a light environment such as Windowmaker. 13.0 pushed it over the edge. Don't know whether it was the kernel, x.org or libraries (or a combination of all 3) that pushed it over the edge, but the difference was noticeable. it was the low memory rather than the slow CPU that was the culprit. Unfortunately it used RIMM memory modules so trying to upgrade it wasn't cost effective.

12.2 was one of my favourite Slackware versions, but to quote Riddick: "...had to end sometime."

Jenni 08-31-2013 05:47 AM

I didn't think it was still being supported, honestly. For such a small team it's impressive they keep rolling out updates for old versions for so long..

It doesn't really hurt me at all, the oldest Slackware I'm still using is 13.1 on my netbook, and I could pretty easily sync that up to 13.37, 14.0, or -current with slacpkg if I need the security fixes.

jtsn 09-01-2013 02:09 AM

Quote:

Originally Posted by AlvaroG (Post 5018896)
Of course this doesn't mean that one can't run one of the old releases in old hardware. With an external firewall configured properly, the security issues for a local server are probably not going to be very important. Just for fun, one can still install Slackware 11 in that proverbial "old Pentium II lying around" we all have, just don't connect it to the internet directly (and check the RPi, it will be cheaper to run and more powerful).

Slackware was always tailored towards low-maintenance. So it's not that hard to build and roll out your own security patches.

astrogeek 09-01-2013 02:51 AM

Quote:

Originally Posted by GazL (Post 5018903)
12.2 was one of my favourite Slackware versions, but to quote Riddick: "...had to end sometime."

Slackware 12.x was my all-time favorite GNU/Linux of any flavor! I am typing on my perfect laptop, a Toshiba circa 2006, 32 bit single CPU 1.7Ghz, 1GB RAM, still going strong with 12.1! I have had to work to keep free space on the drive the last couple of years but otherwise it runs all day every day about 16 hrs and has done since new.

I also still have 12.1/12.2 running on assorted hardware from 800Mhz CPU and as little as 256MB RAM, mostly from necessity.

Sorry to see it reach EOL, but I will continue to run it for some time to come I am sure!

Thanks again to Pat and crew and SBo for the incredible value they provide!

One of my favorite movies as well! "Me? I'm just passing through..."

GazL 09-01-2013 03:04 AM

Quote:

Originally Posted by astrogeek (Post 5019653)
I also still have 12.1/12.2 running on assorted hardware from 800Mhz CPU and as little as 256MB RAM, mostly from necessity.

Just out of interest, what did you do when upstream EOL'd the 2.6.27 kernels?

astrogeek 09-01-2013 03:15 AM

On my laptop I had built my own from 2.6.28 at one point to get real ext4 support and am still running that.

HAH! I can't say I pay a lot of attention to things ELO'd upstream unless there is a major security/stability hole I become aware of, or if I encounter some other problem or need - which has been rare. None of my boxes has to operate outside my LAN except through their own firewalls and the router firewall, all of which I monitor so pretty safe from outside attack.

I am running -current on my few newer boxes and plan to more-or-less freeze them at 14.1 and see if that will stretch as far as 12.x has. I "might" then try to bring some of the better old boxes up to that point as well.

zbreaker 09-02-2013 03:46 PM

Ah nostalgia! My Slackware journey began with 12.1. Fond memories...goodbye old friend.
Slackware -current is my preferred new friend now days.

ottavio 09-02-2013 05:22 PM

I started with v. 11 (2007) and stayed with that until 2011.


All times are GMT -5. The time now is 10:57 PM.