Sometimes it seems like the first (and sometimes only) advice you get offered for almost any problem with a Raspberry Pi is "check your power supply". You think something like:
"hey, I'm using an official power supply sold as being matched with my Pi so how can there be any problem?"
You look up the specs then stick a controlled load across your supply and confirm that it can deliver the required number of Watts.
Yet your problems persist…
The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).
My take-aways are:
You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.
Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse
This was much trickier than I had originally anticipated and have spent a few hours testing.
The config from samba wiki absolutely works, but it wasn't ranked higher in search engine and it's not general enough. https://github.com/zfsonlinux/zfs-auto-snapshot/wiki/Samba
Tested on ubuntu 22.04LTS, samba 4.15.9 and windows 11.
Root.plist in source code, paste the code below to replace it,<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>PreferenceSpecifiers</key>
Unfortunately, xcode does not yet have support for importing OSX crash logs and symbolizing them. Therefore, you must use the command line and a little bit of manual work.
Here is easy steps to try Windows 10 on ARM or Ubuntu for ARM64 on your Apple Silicon Mac. Enjoy!
NOTE: that this is current, 10/1/2021 state.
| #!/bin/sh | |
| : <<'README' | |
| This is a fix for a well-known problem [1] with dropbear-initramfs+netplan | |
| combo. | |
| When dropbear starts, it enables networking [2]. This results in netplan configs | |
| for available ifaces created under /run/netplan. After unlocking, the configs | |
| are still there preventing networkmanager from picking ifaces up: by default, |
| NSDictionary *extensionInfo = [NSBundle.mainBundle objectForInfoDictionaryKey:@"NSExtension"]; | |
| NSString *extensionPointIdentifier = extensionInfo[@"NSExtensionPointIdentifier"]; | |
| if ([extensionPointIdentifier isEqualToString:@"com.apple.watchkit"]) { | |
| NSLog(@"WatchKit extension"); | |
| } else if ([extensionPointIdentifier isEqualToString:@"com.apple.widget-extension"]) { | |
| NSLog(@"Widget extension"); | |
| } else if (extensionPointIdentifier == nil) { | |
| NSLog(@"iOS app"); | |
| } else { | |
| NSLog(@"Unknown extension type"); |
