Click " Skip Ads " to view this page
Saferich.biz

OS X Daily: “Force iOS Devices to Recalculate “Other” Capacity in iTunes” plus 2 more

OS X Daily: “Force iOS Devices to Recalculate “Other” Capacity in iTunes” plus 2 more

Link to OS X Daily

Force iOS Devices to Recalculate “Other” Capacity in iTunes

Posted: 12 Apr 2012 09:05 AM PDT

iTunes Other Capacity

The “Other” capacity in iTunes is supposed to estimate the size of system software, contacts, Messages data, and things that are not listed elsewhere in the capacities list. Sometimes other data will become mislabeled or misappropriated to the “Other” category, and suddenly it’s reported as being much larger than it actually is. Though this has no impact on device performance some people find it annoying, so here’s an easy fix:

  1. Connect the iPad, iPod, or iPhone to a computer
  2. Launch iTunes
  3. Hold the Power and Home button until the device forcibly reboots

The Other space should recalculate to be a reasonable amount, though you may need to relaunch iTunes to see the change.

If the above method didn’t work for you, try the traditional approach to fixing a gigantic Other category size, you may need to restore the iOS device though.

Thanks to hironaka and alan for the tip

Change Length of Bash Command History or Disable Bash History Completely

Posted: 12 Apr 2012 08:54 AM PDT

Bash History

A users .bash_history file keeps a running tab of command line history, logging every command that has been entered into the bash prompt. These command history files make it very easy to find and recall past commands that may have been forgotten, and they’re also extremely useful for system administration. We will cover how to change the stored length of these files, how to disable it, and also how to quickly check a users bash history.

Changing Bash History Length

To increase the history length of a users command history, add the following line to .bash_profile:

HISTFILESIZE=2500

The example above will increase the history size to 2500 commands, that can be changed to any other number as deemed appropriate.

Disable Bash History

Setting the HISTFILESIZE number to 0 within .bash_profile will disable bash command history completely:

HISTFILESIZE=0

Having the history file disabled does not effect command recall, but it does prevent a super user from easily seeing the commands entered into another users shell.

Checking Bash History

There’s a few quick ways to see command history, to see your own type:

history

You can also export that command history to a file with the -w flag:

history -w pastbash.txt

To see another users command history, use cat with their .bash_history file instead:

cat /Users/USERNAME/.bash_history

Remember that if USERNAME has set their history file size to zero, nothing will be shown.

Practical Applications for Mac Users
Two of the most common applications for a Mac user is to keep track of defaults entries that have been entered into the Terminal and to quickly find past commands. Query command history and you won’t have to guess what that obscure command was that you entered four months ago that started with a ‘s’.

Disable the File Extension Change Warning in Mac OS X

Posted: 11 Apr 2012 11:41 AM PDT

File Extension change warning in OS X

Assuming you have file extensions shown in the OS X Finder, attempting to change a file extension causes a warning dialog with a confirmation box to appear. This is annoying if you know what you’re doing and you have a compelling reason to change extensions, so let’s turn it off using the command line and defaults write.

First, open the Terminal, located within the /Applications/Utilities/ directory, then copy and paste in the following command:

defaults write com.apple.finder FXEnableExtensionChangeWarning -bool false

Follow that up by relaunching the Finder with killall:

killall Finder

To reverse the change and get the warning back when you attempt to change file extensions, use the following defaults write command:

defaults write com.apple.finder FXEnableExtensionChangeWarning -bool true

Kill the Finder again for changes to take effect.

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)
top