Why did you stopped using FreeBSD ?

[DonK]

The Jolitz family published 386BSD as a series in DR DOBBS JOURNAL. I started and stopped using it in 1994. Years afterward I learned how a ring buffer bug in the Adaptec AHA-1542B driver manifested itself when the system memory exceeded 4 MB - and my pricey PC had 8 MB at the time.

I subsequently segued to Slackware as a substitute for a few years. And even penned some LINUX JOURNAL articles. Up until a Linux release made my pricey Motif library worthless. Such waste made me return to BSD.

By the year 2000 FreeBSD became my primary OS after dithering between FreeBSD, NetBSD, and OpenBSD during the late 1990s. I've never looked back since.

 

[kpedersen]

Up until a Linux release made my pricey Motif library worthless.

Hah, for so long we were at the absolute mercy of sodding Motif. Which is why it is so strange now that so many in the UNIX/Linux community don't even know what it is. Or are horrified by its looks.

Operating systems would rise or fall based on this library. Motif was such a big thing!

 

[drhowarddrfine]

Well, that's a bit too much IMHO. There's no support for high speed wireless on FreeBSD and also USB3 is slow as hell,

Then I will immediately shut down all FreeBSD usage from here on out and throw everything I have out the window. 20 years of usage down the drain!

 

[dclau]

Never stopped, mate. Just skipped the desktop part.

 

[fmc000]

Then I will immediately shut down all FreeBSD usage from here on out and throw everything I have out the window. 20 years of usage down the drain!

Sorry, I don't get your point (language barrier on my side I suppose).

 

[Espionage724]

Wifi; I'm not a big fan of needing wifibox for faster speeds (it works but adds more complexity than I care for), and I didn't get confident enough in dealing with wpa_supplicant to want to do it on-the-go with random APs. wifibox was 40MB/s, whereas I can do 80MB/s with GUI AP clicks/config no problem Windows and Linux (Intel AC 9560). I'm very not used to cli wifi management.

Custom rc.d service scripts looked way more complex to make than Linux systemd scripts, but to be fair I didn't get around to trying (I looked at MariaDB's to try to fix what I thought was a simple issue and exited the editor real quick).

I'm also kind of skeptical about files after rsync gave errors on years-old files only on FreeBSD: https://forums.freebsd.org/threads/rsync-input-output-error-5-from-zfs-to-ntfs-ntfs-3g.96179/

And surprisingly adb for Android USB flashing didn't work https://forums.freebsd.org/threads/adb-android-tools.93731/#post-672085

Why did you stop using FreeBSD? But what is the answer on: Why are you still using FreeBSD Forum if you stopped using FreeBSD?

Keeping up with news (I'm still mostly interested in FreeBSD over other operating systems)

 

[DonK]

And surprisingly adb for Android USB flashing didn't work https://forums.freebsd.org/threads/adb-android-tools.93731/#post-672085

For what it's worth:

adb devices​

scrcpy​

adb shell ls​

adb shell ls​

Note - whenever adb shell ls hangs, open a new terminal session to invoke adb shell ls again. scrcpy eventually appears. Sometimes you need to restart the daemon with:

sudo killall -9 adb​

adb devices​

scrcpy​

In my experience, scrcpybugs manifest themselves regardless of OS.