srakaskin.blogg.se - Kindle for mac not registering el capitan

#Kindle for mac not registering el capitan how to#
#Kindle for mac not registering el capitan password#

When you’re done making changes, press Control-X to exit the editor, Y to save, and Return to overwrite the existing hosts file.Īs we mentioned earlier, make sure to flush your DNS cache if you notice that your new mappings aren’t working properly. Because we launched Nano using sudo, any changes will be authenticated and saved directly to the original hosts file, without the need to copy it outside of its home directory.Ĥ. Just as we did with the TextEdit method above, we can add, edit, or remove hostname mappings at will. To navigate and edit the file in Nano, use the arrow keys on your keyboard.ģ. You’ll now see the hosts file open in the Nano editor or vim or another editor of your choice.

#Kindle for mac not registering el capitan password#

As with all sudo commands, you’ll need to also enter your admin password to execute it: " sudo nano /private/etc/hosts“Ģ.

To get started, launch Terminal, type the following command, and press Return.

The steps in the previous section are easy enough, but if you want to avoid copying the hosts file you can edit it directly in Terminal using the UNIX Nano Text Editor, which is built into macOS.

#Kindle for mac not registering el capitan how to#

Your Mac will then come through the speakers saying “DNS cache has been flushed.” How to Edit Your Mac Hosts File In Terminal With Nano

To get your Mac to clear your DNS cache, then confirm it’s cleared your cache by echoing a confirmation, enter these two commands separated by a semi-colon as shown here: “ sudo killall -HUP mDNSResponder say DNS cache has been flushed“.

Note: You will need to enter your admin password to execute this command.

Now, type “ sudo killall -HUP mDNSResponder” and press Return.

To flush the DNS cache on your Mac, open Terminal and use the following command (sudo enables you to run this command as the admin of your machine):.

In most cases, the new mapping should work immediately, but if you’re not seeing the correct behavior, you may need to flush your DNS cache, forcing the browser to read from your hosts file to determine the mapping. With the modified hosts file now in place, fire up your Web browser to test the changes.

Choose Replace and then enter your administrative user password to authenticate the transfer.

When you drop the hosts file back in its original location, macOS will ask you what to do about the unmodified hosts file that’s already there.