Recently, two articles appeared on TechRadar documenting various command line tweaks for various apps and functions of Mac OS X. While I didn’t find anything new there, it’s nice to have two articles that summarize a bunch instead of tracking them down one by one across countless bookmarks.

To be honest, most command line tweaks don’t appeal to me. For example, I’d sooner go back to running DOS than go back to using Safari’s “standard” tabs; I love the tabs on top. Still, it’s nice to know I could make the change if I felt so inclined.

What’s surprising to me is that some of the tweaks I do like are incredibly simple — for example, the command that turns on stack highlighting even when using the mouse (No. eight in the first article above). Obviously, having the cursor over an item tells me which one will be activated if I click, and yet I like the highlight as a further indicator.

I also like the one to remove the arrows from iTunes’ interface (No. seven in the second article). Again, this is a little thing, yet I value it in a manner that’s completely out of proportion to the actual change it makes. Put simply, I hate those arrows.

Meanwhile, there’s a tweak for Safari I really like that’s not in either article. It’s one that forces a click to open in a new tab (instead of a window). You can find that one here. Though documented for Safari 3.1, I use it for the Safari 4 beta with no issues.

I’m curious what you think. Which tweaks do you really like? Do you have any to add, and do they seem like major or minor changes to you?

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Why iPad 2 Will Lead Consumers Into the Post-PC Era
• The Near-Term Evolution of Social Commerce
• Content Farms: The Players, The Benefits, The Risks

I rebooted my Macbook Pro about four days ago, and lo, to my surprise, the icon for my boot drive had vanished. I was, too say the least, slightly perturbed. (To the right, the culprit.)

I tried all the quick-fix things – changed what showed in Finder, tried to get it back through Finder – it was gone there too – and finally, I sucked it up and called Apple. Three calls to Apple – and two instances of being hung up on – a clean install of Leopard, and multitudinous Google searches later, I had found two things: a lot of other people were having these issues, all starting about the same time as mine, and, more importantly, a solution.

So first, the solution, and then the explanation of what it is, what it does, and what that means for all of us Mac users.

To get your startup drive back, you need to run two Terminal commands. One of them requires that you have an Administrator password. I’d generally try to give you a solution that didn’t require Terminal, given some peoples’ squishiness about that, but I can’t find another frontend to this. (There’s an Applescript running around, but it doesn’t work, really.)

First, run xattr -d com.apple.metadata:kMDItemFinderComment /***

In this case the *** signifies the name of your missing drive, as this command will work for any drive. If you want your startup drive, all you need is the slash.

Next, run sudo chflags nohidden /*** Same deal with the asterisks, though in this case, another important modification is that it doesn’t need to be run as sudo unless you’re running it on your root drive.

Log out and/or restart, and your icon should be back to stay.

Now, what that all means. As it turns out, the culprit in all this is a simple metadata flag, the hidden flag. This is the same flag that hides the .DS_store files and other things that you’d rather not see floating about your operating system all the time. The problem, in this case, is a change in how Leopard handles that flag, and metadata in general.

Leopard marks a very interesting shift in how Apple’s chosen to deal with the increasing amounts of complicated metadata that we’re all generating. In past years, this has been stored in .DS_store files, for the most part. Tiger added the xattr function family and API’s to play with some, and some people, namely Marquis Logan and John Siracusa, then wrote up some nice little tools that made this accessible to all of us.

In Leopard, there is now a native command for this. There are four flags to the xattr command, at least so far as I’ve been able to tell. (There is no man page for this, but -h works.) They are -l, -p, -w, and -d, and all of them are written out as xattr -flag file [file path]. -L lists the names of all extended attributes on the file. -P, used with -l, prints them. -W is written out as xattr -w attribute_name attribute_value file [file path], and changes the chosen value to whatever you specify. -D, the important one for the above command, simply deletes all extended attributes. The first command, then, deletes all the extended attributes on the given file. The com.apple.metadata.kMDItemFinderComment contains, among other things, the flags for drives in Finder.

The second command, the chflags command, resets the hidden flag on the given file. Two different methods of getting at two different types of metadata, in essence. The second command is found in a couple of places if you google this, but it by itself doesn’t keep the job done. Without the xattr command, the hidden flag resets every time Finder does.

Now, how this happens? I don’t know. I’m working on that – but I suspect that Apple may be too. And in the meantime, I’ve already found some neat things people are doing with it now. Anyone for a way to kill that annoying ‘this program has been downloaded from the internet’ message?

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Why iPad 2 Will Lead Consumers Into the Post-PC Era
• The Near-Term Evolution of Social Commerce
• Content Farms: The Players, The Benefits, The Risks

However, many of us would also like ways to change the frequency of its backups. By default, Time machine runs once an hour, saving a daily backup at the end of the day and a weekly backup at the end of the week. This behavior continues until the drive it was pointed to is full, at which point it begins to delete the oldest backups. Almost immediately, people wanted a way to change the frequency – even if, like me, half the reason was the annoyance of those bright-blue, flashy LED’s on the external hard drive as it spins up every hour in the middle of the night.

An earlier hint at Mac OSX Hints had users editing a .plist file to change the frequency of backups. This hack consisted of editing com.apple.backupd-auto.plist, specifically the following lines:

StartInterval
3600

A change to that integer value – which is in seconds, by the way – and Time Machine would theoretically back up on your schedule, not Apple’s. However, that seems to cause more problems than it solved, in my experience. Specifically, now Time Machine backs up whenever it likes. (It seems to be about once a day, give or take an hour or so, not once every three hours, as I set it to be.) Upon inspection, it appears that the file’s permissions are broken. Repairing permissions in Disk Utility hangs, and attempting to manually do so, even on a duplicate, causes Finder to crash.
…Let’s just say that method is Not Recommended, then.

Alternatively, there is now this – Time Machine Scheduler.  Time Machine Scheduler does not meddle with the .plist files – it simply runs its own daemon to create a backup.  It can be set for any length of time between 1 and 12 hours, as well as optionally running a backup upon loading.  You have the option of either installing Scheduler and its daemon, in which case you do not need to open TMS, or simply running it from the .app when you want to make a backup. It is also fully compatible with existing Time Machine backups – the preference pane will show that Time Machine is off, but it reads the TMS-created backup and date of last backup without trouble.

There is also the option to mount and unmount the Time Machine backup drive automatically, although I have not tested this.  (I have a partitioned drive, and the other partitions are in frequent use, so I don’t bother.)

This method works very well for me, at a reliable three hours.  It takes the same amount of time to run backups, as well as to load and unload the normal Time Machine interface, and, thank heavens, it actually does it every three hours.  Why Apple didn’t include the option to change the backup frequency all along boggles me.

I will note that a third way to do this is to use Lingon to edit the plist files.  I have not tried it, but I thought I would mention it, for  those who might be interested.  How about you?  Have you tried Lingon?  Time Machine Scheduler?  Did the original .plisthack work for you?

(Time Machine Scheduler and Lingon are both free utilities, available at the links above.)

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Why iPad 2 Will Lead Consumers Into the Post-PC Era
• The Near-Term Evolution of Social Commerce
• Content Farms: The Players, The Benefits, The Risks

Apple has discovered that many of the unauthorized iPhone unlocking programs available on the Internet cause irreparable damage to the iPhone’s software, which will likely result in the modified iPhone becoming permanently inoperable when a future Apple-supplied iPhone software update is installed.

They specifically mention the “unlocking” programs which leads us to believe they are only referring to the hacks that unlock your phone and not the hacks for things like ringtones.

Could this just be a scare tactic? Or could Apple be making some changes to the iPhone software that actually will cause the iPhone to be irreparable if it finds hacks were used? Both of those options seem a bit bullish, but Apple hasn’t exactly played nice the past few weeks.

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Mobile Q4: All Eyes Were on Android, 4G and the Rising Tablet Tide
• Report: A Mobile Video Market Overview
• In Q3, the Tablet and 4G Were the Big Stories