Re: Sparc64 doesn't care about you, and you shouldn't care about Sparc64

John-Mark Gurney <[email protected]>
Newsgroups gmane.os.freebsd.devel.sparc
Message-ID <20160805153236.GA16908__38468.2475742467$1470411188$gmane$org@funkthat.com>
Adrian Chadd wrote this message on Wed, Nov 11, 2015 at 07:29 -0800:
> > FreeBSD has an opportunity to fill the void in the secondhand Oracle
> > (Sun) Hardware market if people want to take it.... but I seriously
> > don't see why anyone would buy new Oracle boxes and shove FreeBSD on
> > them - unless their admins already manage FreeBSD on older + Intel hardware.
> >
> 
> As always, someone has to write and debug the code.
> 
> Users are only as good as the revenue to generate to cover
> development/debugging/deployment costs.
> 
> So if you're a sparc64 user, how much would you be willing to pay for
> freebsd/sparc64 support and development?
> 
> I'm all for keeping an architecture like sparc around, as long as
> there's active development and active users. MIPS has both. ARM has
> both. Powerpc has both. Sparc is missing some active developers, but
> it has plenty of FreeBSD users that speak up (and more users that only
> speak up privately.) So, if you want to see sparc64 support continue,
> this requires a grass roots effort to get more development happening -
> either users need to step up, or someone has to start contributing
> money.

If you care, then give donations to the FreeBSD Foundation, and say
you want/need sparc64 and/or sun4v support...

Or find a developer to pay for the work...  These are the straight
forward ways to keep sparc64 alive...

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.