5 ms·

>We asked repeatedly, but Intel provided no advance notice. We did not even receive replies to our requests for dialogue. Intel's treatment of *BSD is frankly

by adtac 8y ago

>We asked repeatedly, but Intel provided no advance notice. We did not even receive replies to our requests for dialogue. Intel's treatment of *BSD is frankly quite insulting, especially so given that they serve a _huge_ portion of the internet traffic, with Netflix using FreeBSD for content delivery.

raverbashing 8y ago
Do other manufacturers have a better relationship with *BSD? To be honest the attitude of "everything sucks and everything is broken" doesn't help OpenBSD though they are right to complain about some things.
- protomyth 8y ago
  "everything sucks and everything is broken" Well, looking at all the chips I've bought in servers for the last 5 years, they are not wrong.
  - raverbashing 8y ago
    Then why did you keep buying them?
    - protomyth 8y ago
      What exactly was the alternative?
- earenndil 8y ago
  I know that nvidia provides native drivers for freebsd, making nvidia gpus the best ones for the platform. I don't know of anything beyond that.
- snaky 8y ago
  Not really. But sometimes they send a patch or two https://lists.freebsd.org/pipermail/freebsd-amd64/2011-March/013740.html https://lists.freebsd.org/pipermail/freebsd-amd64/2011-March...
protomyth 8y ago
The next message in the thread adds to the insult https://marc.info/?l=openbsd-tech&m=153434075003703&w=2 https://marc.info/?l=openbsd-tech&m=153434075003703&w=2 What's funny is that LWN, a Linux news outlet, might have:
Twirrim 8y ago
Certain parts of the BSD community keeps leaking stuff early, either by doing commits in public, or by talking about stuff in advance, before all the bits are in place to protect systems. Hell, they already leaked one this year, forcing a huge scramble all round to get patched out of the door. It has been a persistent issue for years. Why on earth would they still expect to be trusted? It may well be just one or two people doing it, but their actions are screwing things up for an entire set of operating systems. It's especially critical for coordination to happen on vulnerabilities like this one, where it requires a combination of microcode and kernel patches to be done in sync. If one distribution leaks early, all are put at nearly immediate significant risk.
__bjoernd 8y ago
OpenBSD's history of leaking embargoed information might be a reason here. If you don't play by the rules, the adults don't let you play anymore.

by adtac 8y ago

raverbashing 8y ago

Do other manufacturers have a better relationship with *BSD? To be honest the attitude of "everything sucks and everything is broken" doesn't help OpenBSD though they are right to complain about some things.

protomyth 8y ago
"everything sucks and everything is broken" Well, looking at all the chips I've bought in servers for the last 5 years, they are not wrong.
- raverbashing 8y ago
  Then why did you keep buying them?
  - protomyth 8y ago
    What exactly was the alternative?
earenndil 8y ago
I know that nvidia provides native drivers for freebsd, making nvidia gpus the best ones for the platform. I don't know of anything beyond that.
snaky 8y ago
Not really. But sometimes they send a patch or two https://lists.freebsd.org/pipermail/freebsd-amd64/2011-March/013740.html https://lists.freebsd.org/pipermail/freebsd-amd64/2011-March...

protomyth 8y ago

The next message in the thread adds to the insult https://marc.info/?l=openbsd-tech&m=153434075003703&w=2 https://marc.info/?l=openbsd-tech&m=153434075003703&w=2 What's funny is that LWN, a Linux news outlet, might have:

Twirrim 8y ago

Certain parts of the BSD community keeps leaking stuff early, either by doing commits in public, or by talking about stuff in advance, before all the bits are in place to protect systems. Hell, they already leaked one this year, forcing a huge scramble all round to get patched out of the door. It has been a persistent issue for years. Why on earth would they still expect to be trusted? It may well be just one or two people doing it, but their actions are screwing things up for an entire set of operating systems. It's especially critical for coordination to happen on vulnerabilities like this one, where it requires a combination of microcode and kernel patches to be done in sync. If one distribution leaks early, all are put at nearly immediate significant risk.

__bjoernd 8y ago

OpenBSD's history of leaking embargoed information might be a reason here. If you don't play by the rules, the adults don't let you play anymore.