why the move from freebsd to debian (or any other linux kernel for that matter).

I still don't buy the vendor app store argument
Agreed. Whilst it is a problem, it certainly isn't a new problem. We have never been able to run Exchange, Lotus Domino, Sage or any other classic business servers on FreeBSD and yet here it is... still not dead ;)

I think Docker and containers confuse things a bit but Docker containers are still literally the same non-compatible binaries from i.e Exchange, Lotus Domino, Sage and many other precompiled binaries for incompatible platforms that never ran. The only difference is effectively the glorified init scripts.
 
another reason for going Linux (not necessarily Debian) is:

Yet another. If you want to evangelise Linux, you will find endless reasons. Bigger, wider, thicker, more colourful, shinier, faster, more popular, fits more sizes, some government agencies prefer it ...

Even moreso, of course, for Windows. Why not go 'the whole hog'?

What I don't understand is why you don't just go there? Do you need FreeBSD developers and users to come along too?

Genuine question: what do you really want? How can we help?
 
Bigger, wider, thicker, more colourful, shinier, faster, more popular, fits more sizes
slower

and flashy instead of better at its core.

The only thing would be more features, but the ratio of features to bloat isn't good. FreeBSD is getting there with features.

Some things I can see about Linux is for embedded and rescue CDs. It can be done with BSD's too. There's rescue Pen drives that are in BSD. The FreeBSD install CD is one, but not for a quick desktop. It would take DIY for an embedded BSD system though with a miniBSD, but a lot of DIY would be needed for an embedded OS on the Linux kernel too.
 
but a lot of DIY would be needed for an embedded OS on the Linux kernel too.
That is part of my dayjob. The dependency hell is absurd. Update openssl? Good luck! Even updating bash on the build host will make the build fail as one component there depends on an exact version. The HW vendor only supports some old kernel version, so as a matter of fact the whole build machine is stuck in 2012. Fisher Price OS. </rant>
 
I wonder if users as this OP are genuinely asking the question or just trying to steer up flame discussion. Judging mostly due to lack of further responses, as it usually is.

To ask why developers moved from A to B you need to ask those developers.
 
Linux is an half-death horse constantly doped... BigG has already prepared its replacement for the time when maintaining the Linux kernel will be unsustainable. Capitalism is very good at exploiting stuff and the Linux kernel is just exploited!
 
It won't die, though, it seems stagnant. It has a user base that's dedicated to it, that's not going away. The biggest thing, may be features that people need and aren't on FreeBSD. There aren't many of those. The other thing, is FreeBSD is better at its core, but it's a popularity contest. I believe FreeBSD can break out, and will do so when a few features are updated. It's already doing so, as Bluetooth and HID devices are getting better, and video drivers have already improved greatly.


One reason a few people don't stay on FreeBSD was about Samba. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263874. From that, it says that the version changed so much making it difficult to port. TrueNAS has it, because the upstream ported it to there. We assumed it was an implementation that worked with Sambas on other machines, but we didn't realize how old the existing port was as Samba wasn't discussed enough, and the incompatibility was only mentioned on here until more recently.

Another reason would be for GPU processing not having to do with video display.

Not everyone needs those features. Also, if someone's not sharing data with a Windows machine, they should just use NFS, and be made aware of Samba's state. Looking at it this way, most users don't need Samba, and most users don't use GPU processing that's not for their video display. We don't notice what specifically may be lacking on certain ports, unless we try them, dig into them, document it and discuss it for others to see.

The main strength is those who like a good system and like to set it up themselves, and for professionals who don't need those features. FreeBSD needs to get stronger on a few niches, even if it's on the newest features it has.

It may be odd to see me say this, as I'm one of many who are dedicated to use FreeBSD. I thought this for a while, but didn't write it until now.
 
Some things I can see about Linux is for embedded
I have to disagree.
Have you ever built embedded Linux? Yocto is a nightmare compared to NanoBSD.

  • Major changes to the rust toolchain build process were merged and this enables target rust, cross SDK and automated SDK testing. Sadly some issues remain and are stopping enabling the tests by default.

The OpenWRT toolchain is better. buildroot has really become my favorite embedded Linux build toolkit.
 
I still don't buy the vendor app store argument; it sounds too much like "I just want to load an app on my phone to play Angry Birds". Containerized applications may work fine for some percentage of users, but you are still at the mercy of whomever created the container and how it is set up. If the defaults don't work for you, you need to understand how to change it or is the expectation that the vendor creates a new container version to suit your needs?
it’s not really about buying container on any appstore. But now most companies want to reuse hw. installing a supported container or vm is just as easy as buying a device on linux.And it’s easier to ship a container or vm on linux these days unfortunately. Some companies like stormshield wich are doing their product using freebsd only ship linux compatibles vms. Using them under bhyve is a nightmare. Even networking lacks some modern features: sr-iov is not fully working on all nics and no vlan support anyway.

So some subtle touches are missing on freebsd without any clear roadmap for their support. This is why imo some companies decide to choose linux today.
 
certification: sometimes your products environment changes. A governmental organisation approached us for our crypto software (it was also the hardware, but that was not noteworthy: consider it a black box those orgs put in their high security bunker to do some sort of crypto stuff - offline of course), however, told us that they need a certified product, EAL4+ and passing the CIS benchmark seemed obvious. We had to switch to one of the namely Linux enterprise editions because of course supporting two platforms did not make sense for us. Furthermore, they wanted us to add PCI-based HSM cards to use for the crypto stuff, so we additionally had the driver issue with FreeBSD.

I'm curious about this. I haven't heard of EAL, but I don't see any BSD mentioned on Wikipedia's examples. It looks like FIPS is related to crypto and easy to comply with, so FreeBSD might be ineligible for certain corporations if it doesn't meet specific certifications?

Was searching around a bit and found a US Veterans of Affairs page about FreeBSD; did anything come of it or is it planned? https://www.oit.va.gov/Services/TRM/ToolPage.aspx?tid=15002
 
Back
Top