Viewing profile — emaste

Not quite; one FreeBSD community member who isn't a developer edited the FreeBSD wiki to suggest this, and that was picked up by a variety of tech press sources.

The comment I left on a Reddit thread four years ago still applies: > This link gets shared around every now and then, and my response is always the same: there is some useful insi…

The (original) headline is backwards; this is about Anthropic's interest in FreeBSD, not the other way around.

A lot of Linux kernel drivers are permissively licensed, or dual-licensed with a choice of GPL and a permissive license. This is especially common for vendor-developed drivers. Fro…

32-bit x86 CPUs haven't been made in years, companies building products based on FreeBSD switched to 64-bit x86 or to other architectures long ago. It's not that work on i386 is be…

Perl was removed from the FreeBSD base system over 20 years ago.

Note that the bug that is the topic of discussion here predates OpenZFS. Whether or not there has been a slide in disciplined development in OpenZFS, this bug does not support that…

This is a longstanding tradition from FreeBSD. A list of our commit message trailers: https://docs.freebsd.org/en/articles/committers-guide/#_incl... . "Sponsored by:" search in Fr…

I suspect your question is essentially "why is this 14.0, and not 13.3?" And the answer to that question is that this is a new release from our development branch, not an update to…

I'm sure Colin's results can be reproduced, but it will take some effort. Colin has been doing a lot of work so that Firecracker can boot FreeBSD -- see https://www.daemonology.net…

Not really sure how this comment relates to mine.

The FreeBSD Foundation and FreeBSD Project members have been investing in and working on improving FreeBSD security for at least the last several years. Much of that "FreeBSD – A L…

> I did just try to use etcupdate for the 13.2-RELEASE upgrade and it hung forever trying to grep for something in /etc/default/devfs.rules Would you be willing to submit a bug for…

> The only orgs that tend to use BSD tend to not want to give back. This isn't true. Looking at the last year of git commits I see significant contributions from a large number BSD…

Very interesting, but it looks like you're only targeting the Linux kernel right now?

The blog post offers the linked reply to support the claim that FreeBSD "blatantly disregards security in favor of performance and appeasing their enterprise consumers."

> Many of the claims on this page are supported with links to commits, mailing lists posts, etc Their links to commits, mailing list posts, etc., are cherry-picked and taken out of…

tcp_wrappers is still there because it provides functionality not otherwise available that is still used, and has a relatively small impact on the attack surface.

That's not true - it is in all supported releases, but not enabled by default. It will be enabled by default in the upcoming 131.1

The linked blog post gives the impression that little has changed, but it is very much not the case. Taking a look at the first section, "OpenSSH Modifications" - rather little of …

It used to have a section at the bottom that described changes made in FreeBSD (negating some of the points made above), but it has since been deleted.

This link gets shared around every now and then, and my response is always the same: there is some useful insight, but there's also information that's so outdated it provides no va…

Please share an example.

FreeBSD 13.0

Previous submissions (that have comments): https://news.ycombinator.com/item?id=11314648 https://news.ycombinator.com/item?id=11318508 https://news.ycombinator.com/item?id=12484248…