Debian Drops SPARC Platform Support
jones_supa writes: SPARC isn't exactly a highly-used architecture anymore, so the Debian operating system is dropping support for the platform, according to Joerg Jaspert last week in the "debian-sparc" mailing list. He noted that this does not block a later comeback as "sparc64." Following that announcement, a new post today tells us that SPARC support was just removed from the unstable, experimental and jessie-updates channels.
I think the first version of Debian I'd ever used was Hamm on an old Sparcstation IPC.
Your hair look like poop, Bob! - Wanker.
I had a Sun Netra T1 200 for a bit over 10 years that ran Debian on Sparc. The hardware was reliable, the Debian as an OS worked well enough, less of a headache than Solaris IMHO. Occasionally had some weird kernel related quirks, but I generally just kept it tracking Debian sid.
I think it was just a matter of time that the Debian sparc port went away, the surplus of old sparc boxes has gone away more than anything. I'm not sure anyone used Debian on sparc for anything serious(read business use), though.
While Cell failed as a platform, the concept itself had merit, and the concept of pairing high-performance and low-performance processors can be found in the HPC market today (like Intel's Phi or GPGPU) and in the mobile market (like ARM's big.LITTLE architecture).
For more than just a couple of us here, I suspect, there was a time when "Sparc," "UNIX," "graphics," "Internet," and "science" were all nearly synonymous terms.
Simpler times. Boy did that hardware last and last and last in comparison to the hardware of today.
Well, I suppose it can finally no longer be said that the Sparcstation 10 I keep here just for old times' sake can still run "current Linux distributions." But it's still fun to pull it out for people, show them hundreds of megabytes of RAM, 1152x900 24-bit graphics, gigabytes of storage, multiple ethernet channels, and multiple processors, running Firefox happily, and tell them it dates to 1992, when high-end PCs were shipping with mayyybe 16-32GB RAM, a single 486 processor, 640x480x16 graphics, a few dozen megabytes of storage, and no networking.
It helps people to get a handle on how it was possible to develop the internet and do so much of the science that came out of that period—and why even though I don't know every latest hot language, the late '80s/early '90s computer science program that I went to (entirely UNIX-based, all homework done using the CLI, vi, and gcc, emphasis on theory, classic data structures, and variously networked/parallelized environments, with labs of Sparc and 88k hardware all on a massive campus network) seems to have prepared me for today's real-world needs better than the programs they went to, with lots of Dell boxes running Windows-based Java IDEs.
STOP . AMERICA . NOW
[...] and is now even more rare and given its proprietary nature [...]
I never got this: SPARC is probably the least least proprietary architecture out there.
First, anyone can license (www.sparc.org) and sell SPARC CPUs, just like you can license ARM. Try going to Intel and trying to license their latest architectures. They even use OpenBoot for their "BIOS" / firmware, which was available to anyone as IEEE 1275.
Second, you can buy SPARC servers (see above) from at least two vendors (Oracle and Fujitsu), and run Solaris (or anything else) on them.
You can even get GPL licensed HDL for some of the earlier T-series processors: https://lwn.net/Articles/243874/
If it's so easy, why don't you take over the port and show us how it's done? Debian has been very up front for years now that the sparc port was on its way out due to lack of interest; if anyone really cared, they would have stepped up to maintain it. The problem here isn't that it's impossible, or even a theoretical challenge, the problem is that the sparc hardware in general isn't really all that great and there isn't really a compelling reason to use it when people are literally throwing out higher-spec'd x86 gear. Only on the highest end is the sparc line potentially interesting, and nobody spends that much money to run a research project as an OS; by the time the hardware is available to hobbyist developers it's obsolete--and again, why bother plugging in a really power-hungry system and spend years developing for a platform that, by the time it's usable, will be outperformed by tomorrow's junk?