CentOS - Jan 2016 - Centos 3.8 Server Questions, SeaMonkey Mozilla and Java

On 01/09/2016 11:43 AM, John R Pierce wrote:
> On 1/8/2016 2:21 PM, H wrote:
>> That was not helpful - I explained that I had to run this version.
>
> you WANT to run something completely unsupported from about 10 years 
> ago which apparently requires software thats known to be insecure and 
> buggy as all heck.       its 2015, not 2005, 10 years is an eternity 
> in the computer industry.
>
> whatever this 10 year old application is you're trying to get running, 
> it needs to be dragged into a present day state of support.   if this 
> requires reimplementing the clientside applet entirely, so be it.   Do 
> note, Java applets running in web browsers are an almost entirely 
> deprecated technology as there's been a non-stop stream of security 
> problems with the whole java applet concept and implementation.     
> J2SE 1.4, a version that was new in 2002, was desupported in 2008.
Just for your information
I was working for a local ISP a few months ago, that uses microwave 
radio links to connect various hilltop radio access points and thus 
provide high speed internet access to rural clients in hard to reach 
terrain. Some of the kit used had a management interface that ONLY ran 
on an old, very specific version of java. No, the supplier was not 
interested in providing updates, what they provided - worked. The 
network was essentially private, thus difficult for the great unwashed 
to gain access and then in some way compromise the system. BTW, the 
particular version of java was only supported on WindozeXP and an old 
version of IE - thus it ran in a virtualbox and was only made alive when 
access to the radio system was required. welcome to the real world of 
2016, there are lots of bespoke systems providing real value and 
definitely not affordable  to replace in the cut throat world of a local 
ISP.
>
> re; EPEL, as I understand, EPEL drops old versions like a rock the 
> minute they are desupported.
>
>

On Jan 8, 2016, at 10:03 PM, Rob Kampen <rkampen at kampensonline.com>
wrote:
> welcome to the real world of 2016, there are lots of bespoke systems
providing real value and definitely not affordable  to replace in the cut throat
world of a local ISP.
This is a sad truth, but it doesn?t mean that CentOS or EPEL should even *try*
to support them.

If you?re going to run an unsupported, out of date, insecure system, you will
have to run your own infrastructure to support it.

Also, if it were me, I?d be trying to get the bare minimum requirements running
on a supported OS, perhaps in a VM or container.


--
Jonathan Billings <billings at negate.org>

That is very similar to my usecase. Thank you.

On January 8, 2016 10:03:16 PM EST, Rob Kampen <rkampen at
kampensonline.com> wrote:
>On 01/09/2016 11:43 AM, John R Pierce wrote:
>> On 1/8/2016 2:21 PM, H wrote:
>>> That was not helpful - I explained that I had to run this version.
>>
>> you WANT to run something completely unsupported from about 10 years 
>> ago which apparently requires software thats known to be insecure and
>
>> buggy as all heck.       its 2015, not 2005, 10 years is an eternity 
>> in the computer industry.
>>
>> whatever this 10 year old application is you're trying to get
>running, 
>> it needs to be dragged into a present day state of support.   if this
>
>> requires reimplementing the clientside applet entirely, so be it.  
>Do 
>> note, Java applets running in web browsers are an almost entirely 
>> deprecated technology as there's been a non-stop stream of security
>> problems with the whole java applet concept and implementation.     
>> J2SE 1.4, a version that was new in 2002, was desupported in 2008.
>Just for your information
>I was working for a local ISP a few months ago, that uses microwave 
>radio links to connect various hilltop radio access points and thus 
>provide high speed internet access to rural clients in hard to reach 
>terrain. Some of the kit used had a management interface that ONLY ran 
>on an old, very specific version of java. No, the supplier was not 
>interested in providing updates, what they provided - worked. The 
>network was essentially private, thus difficult for the great unwashed 
>to gain access and then in some way compromise the system. BTW, the 
>particular version of java was only supported on WindozeXP and an old 
>version of IE - thus it ran in a virtualbox and was only made alive
>when 
>access to the radio system was required. welcome to the real world of 
>2016, there are lots of bespoke systems providing real value and 
>definitely not affordable  to replace in the cut throat world of a
>local 
>ISP.
>>
>> re; EPEL, as I understand, EPEL drops old versions like a rock the 
>> minute they are desupported.
>>
>>
>
>_______________________________________________
>CentOS mailing list
>CentOS at centos.org
>https://lists.centos.org/mailman/listinfo/centos

But I did not ask for a current version of Centos to support my usecase, did I?

On January 9, 2016 1:04:33 PM EST, Jonathan Billings <billings at
negate.org> wrote:
>On Jan 8, 2016, at 10:03 PM, Rob Kampen <rkampen at kampensonline.com>
>wrote:
>> welcome to the real world of 2016, there are lots of bespoke systems
>providing real value and definitely not affordable  to replace in the
>cut throat world of a local ISP.
>
>This is a sad truth, but it doesn?t mean that CentOS or EPEL should
>even *try* to support them.
>
>If you?re going to run an unsupported, out of date, insecure system,
>you will have to run your own infrastructure to support it.
>
>Also, if it were me, I?d be trying to get the bare minimum requirements
>running on a supported OS, perhaps in a VM or container.
>
>
>--
>Jonathan Billings <billings at negate.org>
>
>
>_______________________________________________
>CentOS mailing list
>CentOS at centos.org
>https://lists.centos.org/mailman/listinfo/centos