@hynek@mastodon.social2024-03-29 05:30:01
The race to replace Redis
https://lwn.net/SubscriberLink/966631/4b519a536bfc7644/
@hynek@mastodon.social2024-03-29 05:30:01
@kernellogger@fosstodon.org2024-05-01 05:12:44
The Kernel Report - Jonathan Corbet (@…), @…
The recording of this recent talk is now available on the #ossna2024 schedule page:
@hynek@mastodon.social2024-03-01 10:09:48
Just renewed my LWN subscription and let me use that as the opportunity to remind y’all that #iOS has built-in print-to-PDF hidden behind a cheat code:
Choose share, Print, and then zoom into the preview (spread fingers on it).
@grifferz@social.bitfolk.com2024-04-20 14:34:01
"How do you think he will react?"
The email that Tridge sent that triggered Larry McVoy into rescinding the Linux kernel's license to use BitKeeper.
#Linux
@andres4ny@social.ridetrans.it2024-04-17 06:35:00
I'm still salty about BikeNYC staying over on xitter, but at least the linux nerds are here. https://lwn.net/SubscriberLink/969908/71265cb4636cb6b9/
![Two paragraphs from the article , with two instances of "Mastodon" highlighted. Text below:
The systemd project had actually already been moving away from directly linking optional dependencies — but not for security reasons. In Poettering's explanation of his proposal on Mastodon he noted: ""The primary reason for [using dlopen()] was to make it easier to build small disk images without optional components, in particular for the purpose of initrds or container deployments."" Some people h…](https://mastodon-usw-cache.b-cdn.net/media_attachments/files/112/285/168/327/360/248/original/1f4c0952ecd1922f.png)
@grifferz@social.bitfolk.com2024-02-19 03:54:42
I hope we've all got our popcorn ready for the coming Linux kernel CVE apocalypse. CISOs may wish to allocate a budget for burn lotion.
https://lwn.net/SubscriberLink/961978/29079857bea3abe7/
@kernellogger@fosstodon.org2024-02-22 09:28:12
@grifferz@social.bitfolk.com2024-04-11 12:33:33
Content warning: Mental health stigma in tech
Mental health stigma alive and well in 2024 and those with a lack of empathy still happy to publicly broadcast it.
This is part of the reason why people don't ask for help when they need it.
https://lwn.net/Articles/968056/
@mgorny@social.treehouse.systems2024-03-07 07:45:57
"""
#OpenRC […] has been in a state of bureaucratic decay for a decade now, having all been hoarded by a random corporate contractor about as responsive to the outside universe as OpenOffice (while taking up as much space; they're the entire reason for the farcical metadata/AUTHORS file in the main package repo).
"""
#Gentoo copyright policy (AKA #GLEP76) has been a long time in the making. More specifically, as you can guess from the author list, it has been a long time in fruitless debate, followed by a short period of creative activity. In its original form, it has been unanimously approved both by the Council and the Trustees in September 2018.
https://bugs.gentoo.org/653118
Not a month later, once we've actually started requiring signoffs per the new policy, one of the Council members requested a "transitional period", to give their company's legal team more time to approve it. Like, they've actively influenced the policy, they've actually voted for approving it, but they didn't mean for it to actually apply at the time — and they've never bothered telling anyone about the problem earlier. Fortunately, they've managed to get a quick approval and started using it.
https://bugs.gentoo.org/667602
As a side effect of using it, attribution lines to said company started popping up in random ebuilds that their employees touched (malicious compliance or just corporate bullshit?). This heralded a maintenance nightmare. Two months later, metadata/AUTHORS was proposed as a compromise to stop that.
https://bugs.gentoo.org/672962
All these years later, I'm thinking that we had a simpler solution to all these, and many later problems, at our disposal back then…
@grifferz@social.bitfolk.com2024-04-11 20:20:36
"At the very least we now have a clearly defined avenue for getting code that matters for Linux only merged into OpenSSH upstream: just get some nation state actor to use it as a vehicle for an exploit, and bam, there's your window of opportunity to get something merged!" – Lennart
https://lwn.net/Articles/968130/
@grifferz@social.bitfolk.com2024-04-11 22:22:02
Radicle: peer-to-peer collaboration with Git
"With a peer-to-peer system, if your node is down, you may have to stop working, but nobody else needs to. More importantly, you don't need permission to run a Radicle node. Your access can't be revoked. Your repositories can't be deleted from your node by others. Nobody will force you to accept an "updated" set of terms and conditions."
@kernellogger@fosstodon.org2024-04-04 09:21:56
Do you want to know which changes and new features #Linux 6.9 will bring when its released on May 12 or 19?
Then check out part 1 and 2 of @…'s great articles on the #LinuxKernel
@kernellogger@fosstodon.org2024-03-18 09:57:21
66 Minutes between submission of a #Linux docs patch (or more precisely: a patch-set with 4 patches!) and the merge to the subsystem specific Git tree. 😮
That was amazingly fast, apparently due to lucky timing. I doubt that I'll ever beat that record…
Thx @…
@jtk@infosec.exchange2024-02-16 14:00:21
Weekend Reads
* DNS-OARC 42 recap #DNS #ChatGPT #Fragmentation #IETF #IAB
@grifferz@social.bitfolk.com2024-04-11 21:09:08
Yes, instead of reading The Register I do indeed read LWN and then provide the shitposting myself, why do you ask?