5 ms·

The three big BSDs aren't exactly obscure, they might not have the highest server market share compared to windows and linux but they are the next on the list a

by tomxor 9y ago

The three big BSDs aren't exactly obscure, they might not have the highest server market share compared to windows and linux but they are the next on the list and often a primary choice for a variety of companies critical infrastructure, the most commonly sighted example these days is netflix. I think the outrage is justified.

hah-muh-rabbi 9y ago
Don't mistake this as OpenBSD's concern for all BSD's. This is just OpenBSD rant because they isolated themselves by not respecting embargoes in the past. Some ARM CPU's are also vulnerable by the way.
- tomxor 9y ago
  That's an interesting point RE OpenBSD, especially if FreeBSD and NetBSD were included (which I do not know), I suspect this was just down to plain irresponsible incompetence though. ...I've no idea what your ARM comment has to do with it though. Meltdown is Intel specific. A relevant question however might be who coordinated the work between june 2017 and now for Meltdown mitigations? Project zero at google discovered it, but did they hand over the responsibility to Intel or decide who else to inform themselves?
  - djsumdog 9y ago
    Has FreedBSD/NetBSD made a statement. I know DragonFly has a patch on master. It's an odd world where Linux is in the "big three" and the BSD counterparts are more on the fringe. It's a far cry from the early world of the 2000s.
innagadadavida 9y ago
The language of the post is incredibly incendiary -- they sound no different than some of the extremists / terrorists talking about their enemies. At the end of the day, we are all humans and the chip designers screwed up in a big way. But this issue is so complex and obscure that it's been unknown for 20+ years.
- tomxor 9y ago
  That's not their argument, their issue is intel didn't bother informing them so they had adequate time to work on patches (you know like they did for linux and windows kernel devs).

by tomxor 9y ago

hah-muh-rabbi 9y ago

Don't mistake this as OpenBSD's concern for all BSD's. This is just OpenBSD rant because they isolated themselves by not respecting embargoes in the past. Some ARM CPU's are also vulnerable by the way.

tomxor 9y ago
That's an interesting point RE OpenBSD, especially if FreeBSD and NetBSD were included (which I do not know), I suspect this was just down to plain irresponsible incompetence though. ...I've no idea what your ARM comment has to do with it though. Meltdown is Intel specific. A relevant question however might be who coordinated the work between june 2017 and now for Meltdown mitigations? Project zero at google discovered it, but did they hand over the responsibility to Intel or decide who else to inform themselves?
- djsumdog 9y ago
  Has FreedBSD/NetBSD made a statement. I know DragonFly has a patch on master. It's an odd world where Linux is in the "big three" and the BSD counterparts are more on the fringe. It's a far cry from the early world of the 2000s.

innagadadavida 9y ago

The language of the post is incredibly incendiary -- they sound no different than some of the extremists / terrorists talking about their enemies. At the end of the day, we are all humans and the chip designers screwed up in a big way. But this issue is so complex and obscure that it's been unknown for 20+ years.

tomxor 9y ago
That's not their argument, their issue is intel didn't bother informing them so they had adequate time to work on patches (you know like they did for linux and windows kernel devs).