On 04/17/2013 03:00 PM, Scott Sullivan wrote:
On 04/17/2013 02:47 PM, Robert Moskowitz wrote:

On 04/17/2013 01:52 PM, Peter Robinson wrote:
On Wed, Apr 17, 2013 at 6:09 PM, Till Maas <opensou...@till.name> wrote:
On Mon, Apr 15, 2013 at 11:28:12PM -0400, Robert Moskowitz wrote:

which talks about F18-beta.  So what do I have to do to build a F18
production image and is there anything else I need to do?

Oh, the primary use of this system will be as a backup/archive server.
AFAIK it will not be supported anymore starting with Fedora 19,
therefore you might consider setting up a different distribution.
That's correct, F-18 will be the last supported armv5tel release. It
will be supported for the entire mainline support cycle so until a
month after the release of Fedora 20.

Facinating.

Any writeups as to why Fedora is exiting what will be a major part of
the computing landscape in coming years?

What other options are there out there?

Their only referring to the armv5tel architecture which the Marvel Kirkwood is built on. The arm7hfp and aarch64 architecture will continue and be the primary focus for ARM hardware going forward.

Oh, yes. Now I see. So in perhaps a year, I will have to see what is hitting ebay with these chips.

A very bad analogy is like dropping i286 support and only focusing on i686 and x86_64.


Ah, yes I remember well..... I was on a Comdex breakfast panel in '87? On why to abandon your i286 for the i386. The panel was David House of Intel, Gates of .... (well you know), Cheryl Curid of General Foods (? I think I remember), and me of Chrysler. They say my point on the simplified memory map to support large spreadsheets and word documents (though it was not Word at that time!) was the 'winning' point. Particularly to this young guy who was seated at my table: Michael Dell...

Yes, OS/2 2.0 was a GREAT operating system!  :)'  Long live LU6.2 SNA!


_______________________________________________
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm

Reply via email to