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.
You're right! I rather use my version of it.
I mean I was wrong, it's the other way, FreeBSD is based on NetBSD instead, sorrywhat do you mean.
FreeBSD was a patchkit ontop of 386BSD.I mean I was wrong, it's the other way, FreeBSD is based on NetBSD instead, sorry
Whoa. That is quite a bug.Alpine Linux has a https://sshhole.com/ - so AlpineBSD must be cursed.
Root ssh login with 256 random characters? That can't be true. They would close the project page and repository.Whoa. That is quite a bug.
Alpinesshole
Howling fsck, that Bug ist ... "interesting". How very convenient, yes?Alpine Linux has a https://sshhole.com/ - so AlpineBSD must be cursed.
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 UP
You're still wrong.I mean I was wrong, it's the other way, FreeBSD is based on NetBSD instead, sorry
am I?You're still wrong.
![]()
History of Unix - Wikipedia
en.wikipedia.org
how bad that is for FreeBSD?
Zero impact.how bad that is for FreeBSD?
HyprBSD uses mainly FreeBSD packages, you can check this from: /usr/local/etc/pkg/repos/*.conf files. Also runningYou'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 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.
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.HyprBSD uses mainly FreeBSD packages, you can check this from: /usr/local/etc/pkg/repos/*.conf files. Also runninghyprbsd verifyafter 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.
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.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.