AlpineBSD: why not Free[BSD]?

I mean I was wrong, it's the other way, FreeBSD is based on NetBSD instead, sorry
FreeBSD was a patchkit ontop of 386BSD.
NetBSD was a fork of 386BSD**

** Forked from v0.1 combined with patchkits and Berkeley's Net/2 sources. Now the patchkits (UPK - Unofficial Patch Kits) were the same that later became FreeBSD. So you might say that both FreeBSD and NetBSD were forked from UPK.
 
You're still wrong.
am I?
1794148886472.png

there are diagrams where that's true and some that is not true but anyway, nevermind.
Thanks for the graph.
 
After all, no one is actually going to use this—except for the person who created it, and perhaps a few of their friends. Consequently, the idea itself and the motivation to keep the project going will soon fade away. It’s just a waste of time for those who end up working on it; they could have spent that time on something more constructive, or joined a project that is already well-known and widely used.
 
Yampress, I pretty much agree, except, it might help the creator(s) learn something, become better than they were at something. So I'd rephrase that as it probably won't be useful to more than its makers and perhaps some of their friends, but I wouldn't say waste of time. Maybe, it's their way of getting better at their craft so that they CAN do something more constructive and/or get on a project more widely used. I don't even know why I'm nitpicking your post, I guess I'm bored and killing time before doing something a bit more constructive. I'll freely admit that I'm nitpicking. :)
 
You're right! I rather use my version of it. :)
But that's it, another flavor but not another OS, package management and releases are from the exact same source.
HyprBSD uses mainly FreeBSD packages, you can check this from: /usr/local/etc/pkg/repos/*.conf files. Also running hyprbsd verify after installing from ISO will show you what has changed. The only files I actually host are what's needed, drivers built from source, patches for linux compat layers, thunar and work around bugs for ejecting disks etc.

After all, no one is actually going to use this—except for the person who created it, and perhaps a few of their friends. Consequently, the idea itself and the motivation to keep the project going will soon fade away. It’s just a waste of time for those who end up working on it; they could have spent that time on something more constructive, or joined a project that is already well-known and widely used.

It came from that fact I wanted to move from my Arch + Hyprland setup to FreeBSD, once I got the things working I required to continue doing YouTube videos - such as OBS and DaVinci Resolve with hardware acceleration, the few games I play with my kids I released it should others find it useful.

Here's is how HyperBSD started, as for my motivation, it's not a side project for me it's my daily driver and allows me to patch things that don't work myself.
 
HyprBSD uses mainly FreeBSD packages, you can check this from: /usr/local/etc/pkg/repos/*.conf files. Also running hyprbsd verify after installing from ISO will show you what has changed. The only files I actually host are what's needed, drivers built from source, patches for linux compat layers, thunar and work around bugs for ejecting disks etc.



It came from that fact I wanted to move from my Arch + Hyprland setup to FreeBSD, once I got the things working I required to continue doing YouTube videos - such as OBS and DaVinci Resolve with hardware acceleration, the few games I play with my kids I released it should others find it useful.

Here's is how HyperBSD started, as for my motivation, it's not a side project for me it's my daily driver and allows me to patch things that don't work myself.
Thank you for showing everyone how to leverage AI to quickly manifest a vision into reality, and that this is just a fraction of what is possible.

I see lots of commits co-authored by Claude in the FreeBSD src repo, so pragmatism won.
 
Thank you for showing everyone how to leverage AI to quickly manifest a vision into reality, and that this is just a fraction of what is possible.

I see lots of commits co-authored by Claude in the FreeBSD src repo, so pragmatism won.

Absolutely. Compiling ports from source is not hard, nor is configuring FreeBSD or creating an ISO.

What has been, is finding and reporting or fixing bugs, such GLib (now merged) preventing file copy progress on FreeBSD. Multiple inotify kernel bugs (one now fixed upstream), Thunar etc.preventing USB drives being ejected.

Linux compat patches which break new drm drivers.

AI has absolutely been used to help find, understand and fix these things. I have a business, a family, and I am not paid to do this 😃
 
I just don't agree on how kmod packages are getting managed in pkg repositories.
It keeps happening to me after updating those video driver packages my system doesn't boot and this happens because the packages are compiled to another kernel version.
The solution is to recompile the packages and those are some of the few packages I build in my system as most of the packages are installed from pkg repositories.
 
I just don't agree on how kmod packages are getting managed in pkg repositories.
It keeps happening to me after updating those video driver packages my system doesn't boot and this happens because the packages are compiled to another kernel version.
The solution is to recompile the packages and those are some of the few packages I build in my system as most of the packages are installed from pkg repositories.
This is a real issue and pain in the butt. Exactly what I posted about on LinkedIn, and was tols to do something about it rather than complain.
 
Back
Top