Updates recommended for all users. They finally address problems with using 12-hour and other clocks. Log handling code has been refactored to improve performance.
Big Sur
This update is recommended for all users. It finally addresses problems with using 12-hour and other clocks. It also reveals a more useful version of the log command used to get a log extract.
iOS and iPadOS apps run on M1 Macs in an environment managed by RunningBoard, FrontBoard, FuseBoard, and several assistants.
App translocation was introduced to stop malicious software exploiting relative file paths. So how come every time an iOS/iPadOS app is run, it’s translocated?
Slow performance when backing up to a network share is mainly down to SMB. Without its improvement, Time Machine over a network is still dead in the water.
With extensive refactoring in the code to display logs extracts, this update should be faster and require less memory on all supported versions of macOS.
How can it take over 5 hours to back up 79 GB of files to a network share? That’s an average transfer rate of 4 MB/s, probably slower than your Internet connection.
Provided it doesn’t have to back up large folders containing many small files, Time Machine backing up to APFS on a network share works well.
The first full backup is performed as a manual backup, and largely occurs in file-by-file copying from source to the backup store. It is more efficient than to HFS+, but differences could be less than 10%.
Addresses problems with time formatting, so you should now be able to use Ulbow with a Buddhist calendar, 12-hour clock, set to summer time in Mongolia.
