Muffin comes with a command line tool aptly named muffin. To use Google App Engine as the backend stack, you need to install the Google App Engine SDK for Python. To use Node.js/MongoDB as the backend stack, you need to install MongoDB. The easiest way to install MongoDB on Mac OS X is using Homebrew. Liberally mist 1-2 standard muffin tins with nonstick cooking spray. Split the macaroni mixture among 20 muffin tins (about 1/4 cup mac and cheese in each). Sprinkle Parmesan cheese over the tops. Full release of 'Derpy and The hunting of the super tasty muffin (of awesomeness)' for Mac OS X 10.6+. Full Release (Win32) May 11 2018 Full Version 16 comments.
Today I got a new hard drive, and I wanted to do a backup of my laptop with it using Time Machine. Before the backup, I was prompted if I wanted to encrypt the backup as well. Well, I thought, why not?
Big mistake! The backup started, finished… and then Time Machine started to encrypt the backup drive. The ENTIRE drive. I was stuck at 1% for about 20 minutes when I got worried.
I couldn't eject the backup drive, I couldn't stop the encryption. I thought I was screwed.
I started looking on the internet for a way to stop or revert the process. One post claimed that it can take days to fully encrypt a drive. DAYS! I had been planning to take the laptop to a cafe just about right then. Guess that was not an option any more.
So long story short, lots of people claimed that an encryption in progress can't be canceled. Others said it could. Some people said to use Disk Util to decrypt. But I found no option do do this while the backup was still running.
I finally got the following command for the terminal from some site, and tried it:
diskutil cs revert /Volumes/my_drive_name -passphrase
where you can get the actual value for your disk (the ‘my_drive_name) using this command:
ls -al /Volumes
I entered this command while Time Machine was still encrypting. The terminal asked me for my encryption password. After that, it only took a moment, and the disk started to quiet down a bit. I checked the status of Time Machine, and it said nothing more about any encryption going on. The Terminal said that the decryption was going on. And this is important: Decryption is not instantaneous. Basically, the terminal was now reverting all the encryping that Time Machine had started.
After a couple of minutes more, the disk slowed down and then stopped spinning completely. I ejected it, and it worked. I reconnected it then, and checked the Time Machine settings. The checkmark for ‘encryption' was off! All looked well. So as a last test, I looked at the disk in Finder, and all the backup data was still there! So I guess this solved it, saving me maybe days of worry!
Mac Os Download
Another Catalina rant, this time about Ruby. As far as I know, on MacOS, it is advisable to leave system Ruby version to the OS For example users don't have write permission on the system's gems folder. , and install a separate version for development. I had one installed via Homebrew, and never had any issues with it.
But after Catalina upgrade, I couldn't run Jekyll. Every time it would fail with the following error:
I checked my bash profile and run which ruby to make sure I'm using the one installed by brew, and everything seemed to be in order.
After quick internet search I learned a lot of people are having similar problems after system upgrade, but I couldn't find the solution.
I've tried reinstalling ruby, setting GEM_HOME, altering PATH in /etc/profile and /etc/bashrc, removing and reinstalling gems, but nothing worked.
Then I tried to see which Jekyll binary is used and realized - for some reason gems were installed using the correct ruby version, but binaries weren't linked properly.
So the solution was pretty easy at the end, all I had to do is to find gems/bin folder and add it to my path.
Mac Os Mojave
It looks like a common sense, but it took me a couple of hours to figure it out. Hopefully this will save time people facing the same issue.
Big Sur update (December 2020)
I got the same error after updating to Big Sur, but this time I couldn't solve it. I still don't know what I was doing wrong. In the end I started using rbenv to manage ruby installations, and it works flawlessly.
Mac Os Mojave
It looks like a common sense, but it took me a couple of hours to figure it out. Hopefully this will save time people facing the same issue.
Big Sur update (December 2020)
I got the same error after updating to Big Sur, but this time I couldn't solve it. I still don't know what I was doing wrong. In the end I started using rbenv to manage ruby installations, and it works flawlessly.
Related Posts
