macos

I’m not a fan of such ‘solutions’ because they hardly qualify as genuine fixes. however, if you find yourself working in MacOS-heavy environment that’s plagued by radio frequency interference, you’ve probably experienced the erratic behavior of Bluetooth-connected accessories. on my mega-desk, I have numerous devices scattered about, not to mention the abundance of Macs themselves. as a result, I encounter this issue quite frequently—almost on a daily basis. some might suggest employing various ‘voodoo’ tricks like “quickly disabling and enabling the mouse, which worked for me” or “updating firmware, shutting down awdl0, and then reading a fairy tale to your children....

ever since the initial tuning of the FreeBSD TCP/IP stack around version 4.x, I’ve found myself occasionally tinkering with the contents of /etc/sysctl.conf just to fine-tune things, you know over time, numerous changes have been made to the FreeBSD TCP/IP stack, including the introduction of modularity. however, MacOS X, being based on FreeBSD, is more conservative and lacks certain options. therefore, on my MacOS systems, I make use of the following /etc/sysctl....

if you have to pack a lot of things, using sheer power of modern multi-core/multi-threaded CPUs may come handy. unless… the tools you’re using are not enabling that by default, and you suffer running everything on one core/thread. as I spend most of my time recently with FreeBSD and MacOS the tools I typically use are command line. therefore, for every gzip - consider using pigz. and for bzip2 - consider using pbzip2....

FreeNAS is special edition of tuned-up FreeBSD, with GUI available over WWW to enable easy setup and maintenance. i had to migrate recently my old Synology 1815+ thanks to well known Intel SNAFU with Atom CPUs. interestingly enough, even Synology own service department declined to RMA the NAS, without even discussing the situation. so i managed to setup quickly 12x 3.5" bay server. i had five 3.5" 8TB HDDs from Synology that i wanted to rescue data from....