Out of the box, my SMB performance on macOS 12.3.1 would top out at around 20MB/s in short ~5 second bursts, which was absolutely horrendous, slow to navigate in Finder and slugish to interact with.
Since making these changes, I now get sustained ~80-100MB/s+ and instant Finder navigation which is superb and how things should be out-of-the-box (OOTB)!
May 2023 update: As of Ventura, the SMB issues were just horribly inconsistent and hard to maintain. Something in the combination of Unraid, macOS and SMB just doesn't play nice. I ended up binning NFS/SMB all together and heading to a locally hosted Nextcloud instance for file syncing, then using SFTP/Ansible Git flow for editing files within appdata.
Yes, I know—yet another attempt at bringing a ternary-like experience to Go. But hey, Go doesn’t have one, and I wasn’t around when the last million were written.
Because Go doesn't have a ternary operator, and according to the official FAQ, it likely never will. The reasoning? To prevent developers from writing "impenetrably complex expressions." But let's be real—poor coding practices exist in all forms. Instead of outright banning a useful construct, wouldn’t compiler warnings for overly complicated ternary expressions have been a more reasonable approach?
Since that's not happening, here’s go-ternary—because sometimes, a one-liner is just nicer than an if-else.
| package main | |
| import ( | |
| "exec" | |
| "log" | |
| "os" | |
| ) | |
| func main() { | |
| file, err := os.Open("/dev/tun0", os.O_RDWR, 0) |
| package main | |
| import ( | |
| "log" | |
| "os" | |
| "os/exec" | |
| "syscall" | |
| "unsafe" | |
| ) |
On March 29th, 2024, a backdoor was discovered in xz-utils, a suite of software that gives developers lossless compression. This package is commonly used for compressing release tarballs, software packages, kernel images, and initramfs images. It is very widely distributed, statistically your average Linux or macOS system will have it installed for
| # When i was faced with this warning in lvm when i run lvm command it works but it took | |
| # WARNING: Device /dev/dm-20 not initialized in udev database even after waiting 10000000 microseconds. | |
| # It look my problem is solved by reloading udev rules without reboot with this command: | |
| udevadm control --reload-rules && udevadm trigger |
| #!/usr/bin/env bash | |
| set -eou pipefail | |
| if [ "$#" -ne 2 ]; then | |
| echo "Usage: $0 input_file output_file" | |
| exit 1 | |
| fi | |
| input_file="$1" |