emaste

6 ms·

1.
by emaste 2mo ago
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.
2.
by emaste 4mo ago
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 insight, but there's also information that's so out
3.
by emaste 6mo ago
The (original) headline is backwards; this is about Anthropic's interest in FreeBSD, not the other way around.
4.
by emaste 7mo ago
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. From a hardware vendor’s perspective, broad license compatibili
5.
by emaste 3y ago
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 being done but kept in private repos and not upstrea
6.
by emaste 3y ago
Perl was removed from the FreeBSD base system over 20 years ago.
7.
by emaste 3y 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 assertion.
8.
by emaste 3y ago
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 FreeBSD commit messag
9.
by emaste 3y ago
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 an existing branch used for the 13.x releases. Fr
10.
by emaste 3y ago
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/blog/2022-10-18-FreeBSD-Fire
11.
by emaste 3y ago
Not really sure how this comment relates to mine.
12.
by emaste 3y ago
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 Lesson in Poor Defaults" blog post is outdated&#x2F
13.
by emaste 3y ago
> 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 etcupdate issue? Or, just reply here
14.
by emaste 3y ago
> 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-using companies and organizations. Looking at the
15.
by emaste 4y ago
Very interesting, but it looks like you're only targeting the Linux kernel right now?
16.
by emaste 4y ago
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."
17.
by emaste 4y ago
> 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 context to present their view. For one example, they sug
18.
by emaste 4y ago
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.
19.
by emaste 4y ago
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
20.
by emaste 4y ago
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 is current. With respect to ciphers disabled by
21.
by emaste 4y ago
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.
22.
by emaste 4y ago
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 value, outright misinformation, and self-contradicti
23.
by emaste 5y ago
Please share an example.
24.
by emaste 5y ago
FreeBSD 13.0
25.
by emaste 5y ago
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 http
26.
by emaste 5y ago
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 value, outright misinformation, and self-contradicti
27.
by emaste 5y ago
This is quite far off the mark. Many companies using FreeBSD, including Juniper, NetApp, Netflix, Netgate (pfSense), iXsystems (TrueNAS), Dell (Isilon) contribute significant code to FreeBSD. It's very expensive to maintain long-lived
28.
by emaste 5y ago
The difference is that binary packages for Tier-2 and lower are on a best-effort basis, and might be more or less out of date depending on the available package build hardware. For arm64 we now have multiple high-end arm64 servers and can g
29.
by emaste 6y ago
Ed Schouten presented "Running CloudABI applications on a FreeBSD based Kubernetes cluster" at EuroBSDCon 2017. Some really cool ideas, it's unfortunate that it didn't go further. https://www.youtube.com/
30.
by emaste 7y ago
Tylenol / acetaminophen is not an NSAID.

More ›