The answer is buried behind the lede a bit (in that you’ll only find it by looking at who’s the user behind the source code), but it’s a project from Drew.
Drew uses Alpine as his daily driver and for all his servers, and has also been vocally critical of Linus accepting LLM contributions into the kernel.
This probably is his way of resolving that criticism; moving over to BSD as it categorically hasn’t accepted LLM code in its kernel, while still getting to keep the specific userland he prefers. At a glance, it’s a neat idea although I’m also curious to see how it’ll confront reality if he opts to move Sourcehut to AlpineBSD as well. (This isn’t sarcasm, I’m genuinely curious; Linux distros and BSD have very different philosophies on how a system is assembled, and the nature of Linux has always lend itself to being more “choose the parts you want”, with distros acting mostly as curators, compared to BSD shipping much more “complete” elements in terms of userland.)
Note: I’m linking through mastodon prime as the original instances requires authentication to view.
if he opts to move Sourcehut to AlpineBSD as well. (This isn’t sarcasm, I’m genuinely curious; Linux distros and BSD have very different philosophies
Might be painting communities with too broad a brush, but afaict Drew is already more philosophically aligned with the BSDs. If you’ve looked into how SourceHut does deploys, you’ll notice that Drew already does things the ‘sysadmin’ way. As in to deploy they package the repository and push a new version to their self-hosted apk repository (similar to an Ubuntu PPA) and uses sshs into the production boxes to update to the new version through apk. An average Linux user is much more likely to use a container registry instead.
Personally, although I’ve been playing with vanilla NetBSD I’m hoping the AlpineBSD projecs because popular so that it helps revitalize NetBSD. Which has plenty of cool features (rumpkernels) to stand on its own merits.
The answer is buried behind the lede a bit (in that you’ll only find it by looking at who’s the user behind the source code), but it’s a project from Drew.
Drew uses Alpine as his daily driver and for all his servers, and has also been vocally critical of Linus accepting LLM contributions into the kernel.
This probably is his way of resolving that criticism; moving over to BSD as it categorically hasn’t accepted LLM code in its kernel, while still getting to keep the specific userland he prefers. At a glance, it’s a neat idea although I’m also curious to see how it’ll confront reality if he opts to move Sourcehut to AlpineBSD as well. (This isn’t sarcasm, I’m genuinely curious; Linux distros and BSD have very different philosophies on how a system is assembled, and the nature of Linux has always lend itself to being more “choose the parts you want”, with distros acting mostly as curators, compared to BSD shipping much more “complete” elements in terms of userland.)
score 1 · canonical
Good find.
score 1 · canonical
AFAIU Alpine’s council actions are much more relevant than Linus. Case in point: https://mastodon.social/@drew@social.freebitcoin.gay/117358303430810583
Note: I’m linking through mastodon prime as the original instances requires authentication to view.
Might be painting communities with too broad a brush, but afaict Drew is already more philosophically aligned with the BSDs. If you’ve looked into how SourceHut does deploys, you’ll notice that Drew already does things the ‘sysadmin’ way. As in to deploy they package the repository and push a new version to their self-hosted apk repository (similar to an Ubuntu PPA) and uses sshs into the production boxes to update to the new version through apk. An average Linux user is much more likely to use a container registry instead.
Personally, although I’ve been playing with vanilla NetBSD I’m hoping the AlpineBSD projecs because popular so that it helps revitalize NetBSD. Which has plenty of cool features (rumpkernels) to stand on its own merits.
score 1 · canonical