Installing openbsd is cumbersome. Foremost, the partitioning/slicing. Mostly it wants the whole drive. And the text-gui is not friendly.
Wait, are we talking about zealots or veterans?
So you agree then that the current curses-style iso image should never change so that veterans can continue to be able to use what they normally use?
This is the part that seems odd. If someone can't read text or if they think text is unfriendly, then they must really hate computers. In that case, no need to break them for "veterans" or people who do like text. Luckily, the OpenBSD guys will strongly push back against such ideas. I am hoping the FreeBSD project will too (or at least not replace it entirely with a GUI installer aka Microsoft Windows).
Asus does make good boards, yours can be found on Amazon for $228 ? , even used. But even so - that board came out in 2010, and the chipsets came out earlier. There's a good chance that some drivers got deprecated, and split off into ports/packages. In all honesty, though, I'm surprised that a special ethernet driver is even needed there - unlike wifi... That makes installation of anything pretty awkward.
??? What was the point of something like that?
The "veterans" ITT are really just zealots with the "works for me" mentality, barring everybody else off and scaring them away. Might not like to admit it but that's the truth.
I never said the default ISO should change, I only said there should be an optional non-free ISO similar to how Debian has an unofficial one but they point to it for new users who might need it. I feel like newbies would not trust some random torrent with the non-free firmware or even find it, but if it pleases the zealots then it's better than nothing.
That is where I strongly disagree. They are simply more skilled than you. They are simply more skilled than me. The best thing we can do is get out of their way and make the best of what we can out of their scraps.
Skilled, yeah, but lack of adaptability will come back later to bite everyone when nobody understands what's been done, or how to troubleshoot the problems.
I don't disagree with this, but I'm trying to convey in relation to the original post how it could be avoided with things like a firmware installer. If we can't help new users then FreeBSD won't be anything but a passion project years down the road and I don't want that, I don't think anyone here does.
Oh, I have to correct myself. I named the board of my previous computer. I currently have the Asus TUF Gaming B550 Plus, with an AMD Ryzen 5 3600, hence the issue with the Realtek driver.
In theory, perhaps but in practice; well, I feel FreeBSD is good evidence that keeping some more traditional ideas alive does age well compared to Linux. There is a thin line between adaptability and volatility.
I suppose I jump the gun a little bit but from experience, I do see that this has the potential to lead up to some of the mistakes as seen in Linux (or other user-friendly platforms). Ultimately I even feel a mere passion project would end up a more useful bit of software than Linux has become. I say, let the veterans keep their passion project, for those who don't like it; Linux is there for the more wild west style bucket of ideas and friendliness.
That's indeed difficult. When I tried to install OpenBSD, it could not read the installation medium - it didn't have device nodes for it. So it was impossible to read the distribution packages. I started FreeBSD, created another partition on the target disk and copied the archives there. But it wouldn't install from there either, because that was outside the OpenBSD slice. Finally I copied them into the intended /home filesystem, and then it worked. Luckily the ufs filesystems are still somehow compatible.
I didn't bother to try and understand that. I'm running these boards. They're indeed good, never had an issue. This one has the same network chip as one of mine, and that did work for years with the re driver in GENERIC.
This is similar to mine, I use a Gigabyte B550M DS3H (big mistake) with the same Ryzen processor. I have constant popping sound issues on Linux because of the Realtek sound chip this motherboard uses but in FreeBSD with OSS instead of ALSA the audio works flawlessly.
Good luck. ports-mgmt/pkg is extremely basic so there's not really any way to tell it to install something if it conflicts with another package due to the maintainer's build options, so this means as of now you have to go down the line and build whatever port without an option that conflicts with what you're trying to install. You ran into the same luajit vs. luajit-openresty problem as I did, but I had it with Minetest and OBS Studio. I had to go and build Minetest without its luajit-openresty support so that I could install OBS Studio which used the other. Its a real PITA but perhaps one day we'll see a way to tell
pkg to blacklist certain packages or prioritize ones in the future.FreeBSD does have spinoffs that the Foundation actually mentions, like DragonflyBSD, MidnightBSD, NomadBSD and the like... So this is really par for the course - everybody does this, so does FreeBSD. It takes some brains to read such comments to mean "You have options", as opposed to "Ehhhh just go find something else kid."
./configure, make and make install usually does not work on FreeBSD out-of-the box simply means that the GNU-autotools are not portable.cmake. All stuff I am compiling has been working fine so far, i.e. there was no need for ports-tree integration!
