AlpineBSD builds a NetBSD-based OS with as little AI-generated code as possible

AlpineBSD pairs the NetBSD kernel with an Alpine Linux-inspired userspace, aiming to keep AI-generated software out of the base system and main package repository. It ships apk-tools, busybox, and a more GNU-oriented toolset, uses s6 init with OpenRC planned, and is a work in progress with no installer yet. Expect spotty hardware support inherited from NetBSD.

There is no LLM output included in the base system or main package repository.
  1. iamnothere

    Interesting to watch the rapid fragmentation of FOSS into “hard” anti-AI, AI-neutral-to-discouraged, AI-supplemented, and AI-driven camps, akin to the early GPL vs BSD wars. Suddenly I don’t see as many complaints about licensing, and some of the die-hard GPL stans are silently dropping that position as Linux adopts AI-supplemented development.

    On one hand it’s unfortunate, because it hypothetically dilutes developer efforts, but on the other hand the most extreme groups already had incompatible personalities and weren’t working well together. This self-sorting may actually result in a better cadence and less energy wasted on arguing.

    The downside is that a lot of loud and annoying people seem to be converging on BSD land. I am AI-nonaligned (I just care about Quality) but I’m very much in favor of OpenBSD’s heads-down focused dev culture. I hope that doesn’t change.

  2. kev009

    These types of projects tend to have a flash of appeal, especially to people used to Linux, because it lessens one degree of unfamiliarity, but they don't seem to stick around for to me obvious reasons.

    It's hard to get involved with something like a BSD project because you have to learn a lot and put in enough effort to get committer rights. And then if you want to move the needle you have to do even more work and build consensus without getting overly emotional when people disagree with you. But it is the path I would recommend to have a lasting impact, and I am speaking from experience as a FreeBSD and NetBSD src committer.

    Also, pkgsrc is one of the strong points of NetBSD, coupled with pbulk and pkgin. Wrapping that all up in an opinionated installation (like Omarchy recently did to Arch) would be a more survivable effort. But as my friend Larry McVoy would say, it means you don't always get to drive the big red fire truck by yourself.

  3. yjftsjthsd-h

    > AlpineBSD is not a fork of Alpine Linux, its package collection is original (though many packages are ultimately based on aports).

    > Alpine Linux uses the OpenRC init system. Currently, AlpineBSD uses s6 and we intend to add OpenRC as an alternative.

    I'm not sure where exactly the line should be, but that feels like it's not an Alpine* then. Like, if you're starting your package collection separately and use a different service manager, you're further from Alpine Linux than Adélie Linux is.

    (To be clear, I'm a big fan of making a new OS from a *BSD core and a new userspace. I'm just quibbling about naming semantics)

  4. hoppp

    The whole "as little AI code as possible" is tribalism.

    I want software that is brilliant and well audited, no matter who or what produced it.

    No AI guarantees nothing, especially if it's a C codebase like netbsd, why not also join the rust tribe then?

  5. thenthenthen

    Alpine is also the codename of the first iOS, hence the default root pwd ‘alpine’.

    https://mashable.com/archive/apple-ios-codenames#9.CLuUuywuq...

  6. seethishat

    Back in my day, we didn't have artificial intelligence. We had actual ignorance. And we liked it that way.

  7. against_epistem

    I can respect this. Looks like AI auditing code is fine and I can't imagine why auditing would ever be a con. As for the lack of reasons given I guess they leave that for the users which seems completely fine to me. If you are chimping out over not getting a justification then you should probably do some soul-searching.

  8. cturner

    After reading the web page, I am left with some questions unanswered,

    * Is it a goal for AlpineBSD to run on native hardware, or is it intended for containers (a major use-case for Alpine itself)?

    * For users who want to avoid AI-generated code, why run this rather than netbsd itself?

    If the team want to attract interest, they should give more context.

    The mission is unclear. The team could address this by stating goals and milestones on the front page.

    There is a link to a tool s6 on the page. The description of that tool opens with a circular definition. It would be clearer if it stated why it exists in the opening paragraph. Near the bottom it talks about "One of the design goals of s6-frontend". It would be better to state all of the design goals.

More from this day

2026-10-28