On Mon, Jan 28, 2013 at 11:06 AM, Garrett D'Amore <[email protected]> wrote: > I'm sorry to open a thread that I'm sure will cause a lot of discussion most > of which will probably be fruitless and pointless. And yet, I feel compelled > to do this. Please think before you respond, and only reply if you have some > thing useful to add to this conversation. > > Recently, I advocated (as in RTI advocacy), a change to a program - kstat. > After I integrated this change, another advocate pointed out that the SPARC > port was broken by this otherwise worthwhile change. In that particular > instance, the advocate took it upon himself to fix the problem. > > However, its clear to me that this particular advocate (Richard Lowe) may be > the only advocate with regular access to SPARC. Its also clear to me that > the vast majority of ordinary developers lack such access to SPARC.
In thinking about this, a question comes to mind? What did this "SPARC breakage event" cost you? My impression is that keeping SPARC around has not cost us much. Sure, it gets broken more often than intel, and it stays broken until someone with time and interested comes along to fix it. So? My suggestion would be to just relax a little, rather than treat each SPARC breakage event as some emergency. We can give all these SPARC fans who eagerly respond to your thread a chance to come help keep SPARC alive if they want. I hope they will. -- Gordon Ross <[email protected]> Nexenta Systems, Inc. www.nexenta.com Enterprise class storage for everyone ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
