Posts

Post not yet marked as solved
102 Replies
0 Views
I'd like to pile on :) Since I have upgraded to 11.5 beta (20G5042c) my MacBook Air has become so unstable it’s impossible to compile anything on it. Clang will crash, and then the system will panic at the earliest opportunity. I can’t even install MacOS 12 on it, the installer breaks at the very end. I’m pretty sure something is broken with the memory allocator, judging by what forensics I get (malloc/free inconsistencies, as others have mentioned). I assume the VM swapping mechanism is buggy. That would explain why the panics only happen when the memory gets almost full and the swapping mechanism kicks in. Anyways. I agree that as time passes on, MacOS gets pointlessly more complex, making it more prone to bugs. It’s high time Apple focussed on the kernel design rather than touting cosmetics features so few people care about.
Post marked as solved
2 Replies
0 Views
Hey Quinn,yeah, you're right. I had a pf routing problem on the FreeBSD side: no routing possible, so no CHILD SA phase. (TBH, I had put the debug level so high that particular error was buried into a lot of noise and had escaped my scrutiny).Still, the error messages are a bit weird on the MacOS side.But you were right, and I apologize for the noise. Thanks for being so watchful!V.
Post not yet marked as solved
2 Replies
0 Views
Replied In 10.14 Install
What kind of partition are you trying to install 10.14 on?
Post not yet marked as solved
4 Replies
0 Views
This is dumb. While I can grok the idea beyond this, it at least lacks subtlety, like a one-size-fits-all approach. There should at least be two options in csrutil to disable user files/system files protection separately
Post marked as solved
5 Replies
0 Views
Sorry I didn't answer you before. The thread seemed to have vanished. Glad you found a solution 🙂
Post not yet marked as solved
14 Replies
0 Views
This is bad. A simple utility like du(1) is unable to compute the space used by the Mail subdirectory.Make the directory read-only is one thing. Make it unacessible is another. If Apple is bothered by unauthorized accesses, they should encrypt the data and make the directory read-only.
Post not yet marked as solved
2 Replies
0 Views
Mine works, but I started from scratch creating new accounts (I installed 10.14 on a separate partition).That's the beauty of IMAP. You can have as many clients as you wish, they all keep in sync.
Post not yet marked as solved
4 Replies
0 Views
Same thing here. Have filed a bug report. I suspect this might be caused by some sort of CSR-linked new protection. Like, a virus cannot tamper with your mail or web browser anymore.
Post not yet marked as solved
3 Replies
0 Views
That's right. I suppose if you used grey buttons on a dark baground, the contrast would be insufficient.
Post not yet marked as solved
34 Replies
0 Views
Pixelmator works.PyCharm also.Coda works also.
Post not yet marked as solved
2 Replies
0 Views
There's a mysterious ⌘5 shortcut, but it doesn't seem to do much except taking a still screenshot. Might not be working yet?
Post not yet marked as solved
2 Replies
0 Views
See what others experience when trying to boot from a USB drive. I’m pretty sure the USB drivers are buggy in this version.
Post not yet marked as solved
8 Replies
0 Views
Can you open a terminal and use dsenableroot? (see man dsenableroot for more info). One you’ve a root account working, it should be easy to get your own account working with the other utilities such as dsconfigad -add (see the manpage, too)
Post marked as solved
38 Replies
0 Views
As I briefly mentioned, intial boot relies on the EFI USB drivers. Those might work. Then when the kernel is loaded, the EFI drivers are killed and the kernel's take over. That's why, if your phone is connected to your Mac, you can see it powered at start, then the power fails, and turns up again a few seconds later.
Post marked as solved
6 Replies
0 Views
Apparently this software uses kext to work. No wonder it fails with a new kernel. It's like hoping Valgrind to work out of the box.You can always use pfctl(1) if you're worried about your ongoing connections, no?