RE: https://mastodon.social/@arstechnica/116251904542821545
We agree!
And if you want to learn more about our thoughts on this topic, check out our blog: https://quad9.net/news/blog/when-enforcing-copyright-starts-breaking-the-internets-plumbing/
RE: https://mastodon.social/@arstechnica/116251904542821545
We agree!
And if you want to learn more about our thoughts on this topic, check out our blog: https://quad9.net/news/blog/when-enforcing-copyright-starts-breaking-the-internets-plumbing/
#pkg will switch back from libcurl to libfetch (augmented with full http/1.1 support, and sugar that we used from libcurl).
There should be no loss for users, and it will save me headache at each libcurl updates.
This is not a rant against libcurl which is great, just bundling it was not a great idea maintenance wise.
My work on LLDB’s FreeBSDKernel plugin:
https://minsoo.io/future-of-the-freebsd-kernel-lldb-plugin/
The name FreeBSDKernel will be changed to FreeBSD-core, since it only provides functionalities to examine core dumps. Traditional live kernel debugging is done through gdb-remote plugin with FreeBSD’s gdb stub.

FreeBSD offers several approaches to kernel debugging: DDB, live kernel debugging, and core dump analysis. DDB is an interactive debugger built directly into the FreeBSD kernel, with syntax inspired by GDB — making it immediately familiar to most developers. Live debugging leverages FreeBSD's GDB stub (defined under sys/gdb); on the