[x0x0]

or TimeMachine

"sparsebundle already in use" is the FOAD of error messages. I do love how the (now stale) tools to fix this are maintained by a volunteer on an external site unrelated to apple.

I try not to be too grumpy about it, but I paid $3k for a laptop not to have to fucking deal with windows-style normal operation of the OS and related tools is busted and you're gonna sink hours into debugging it. And least when linux breaks it tends to leave error messages and details in syslog...

[username223]

My latest pet peeve is `mds_stores` deciding it needs to spend forever using my iPod, so I can't unplug it without incurring a scolding. It's not hard for Mac OS to stay less terrible to configure than Linux, and less terrible to use than Windows, but that's a low bar.

[r00fus]

Do you have your iPod configured in iTunes with "Enable disk use"? Sounds like Spotlight is trying to index it or something...

[username223]

I probably do. Thanks to my partial understanding of how the software works, I can guess that `mds_` is Spotlight trying to index my music player, but I wouldn't want to try to explain it to my dad. Software that responds to "eject this" with "no, because f* you" because it is busy creating meta-data is user-hostile.

[13thLetter]

I switched from OSX Yosemite to Windows 8.1 a while back.

I have had substantially fewer problems with Windows 8.1.

[misterdata]

Just yesterday I performed a clean install of Windows 10 on my desktop work computer. After joining our domain (configured in the most standard way possible), the start menu stopped working and edge couldn't start anymore. All commands to fix this situation (through powershell) gave cryptic hexadecimal error codes. After a few hours it turns out the Windows Firewall service was disabled. How this causes the Start Menu to malfunction, I don't know...

Again this was a clean installation. Windows 10 is a joke.

[x0x0]

hmm. windows 10's inability to not talk to microsoft skeeves me out though.

[digi_owl]

> And least when linux breaks it tends to leave error messages and details in syslog...

Tends to. Not directly a Linux issue, but i was trying to figure out why one specific program was giving me corrupted MAC errors when connecting via sftp.

All searches indicated it was a network config issue, but no changes seemed to matter.

Eventually i checked the libs the program was compiled with and found the sftp one was "jurassic". One update later and no more errors.

that said, more often than not, a quick dmesg or tail /var/log/messages is all that i need to get something purring again.