- #MAC TERMINAL COMMANDS USEFUL MAC OS X#
- #MAC TERMINAL COMMANDS USEFUL FULL#
- #MAC TERMINAL COMMANDS USEFUL SOFTWARE#
- #MAC TERMINAL COMMANDS USEFUL PC#
This sends an AppleScript to set the volume to an audible level. In the Terminal, first remotely login to the system by using ssh logged in, enter this command: sudo osascript -e "set Volume 20"Īnd then press return. Assuming your friend or co-worker’s Mac meets these requirements, you can play a heck of an April Fools’ joke. This one requires you to have a administrative login account on a remote Mac that has Remote Login (SSH) enabled.
#MAC TERMINAL COMMANDS USEFUL FULL#
To get a full list of keyboard shortcuts, press the escape key, and you’ll get a menu bar with all the options and their keyboard equivalents. The G key will bring up a URL box for when you’d like to browse to a different site. Use the up and down arrows to scroll among the links on the page, and press return on a highlighted link to follow it.
#MAC TERMINAL COMMANDS USEFUL MAC OS X#
Of course, it doesn’t load any pictures, animations, or Flash movies, but it’s great for low-bandwidth connections and for just reading on the Web.Īfter you download and install the Mac OS X installer package, just open up your Terminal and type links, such as to visit Low End Mac in text-only mode. The fastest browser on the Mac is without a doubt Links. Here’s a rundown of five fun things to do in the Terminal: Browse the Webįorget Firefox, Safari, and Camino. If there isn’t, it won’t be long until somebody builds one in XCode.īut that doesn’t mean there still isn’t some fun to be had. The bugs that sent you to the command line in those days are long gone, and there are now GUI front-ends for nearly everything in the Unix underpinnings. Now I wouldn’t do without the Terminal, although in today’s OS X it’s not needed near as much as it was with earlier versions. Around the same time, I’d also started to tinker with Linux, and that certainly helped my familiarity with and acceptance of the command line. After a while, I had learned enough and actually started to like it. In the days before Apple supplied a “Repair Permissions” feature in Disk Utility, it sure helped to know the chown and chmod commands, which change file ownership and permissions.Īnd so on, until one day the Terminal became one of my regular applications. (You may remember how sometimes you just couldn’t empty your Trash in the early versions of OS X.) The next thing I learned to do was delete files with root power, using the sudo command.
#MAC TERMINAL COMMANDS USEFUL SOFTWARE#
The first thing I learned to do was compile software from source, because there was a video poker game that would run on OS X when compiled straight from source – and I was desperate for a game other than Apple’s Chess program. Technically there wasn’t any need to use the Terminal, but it helped to gain some functionality out of the OS and fix things for which there was no graphical program. I wasn’t very happy with the prospect of having to learn some Unix when I first installed Mac OS X 10.0. My first two years in college, we got email by dialing a terminal program into the university’s Unix servers, but I only knew the commands to get and manipulate my mail.
#MAC TERMINAL COMMANDS USEFUL PC#
I’d hardly ever used a PC until I occasionally got stuck with them in the labs at college, so I’d never used DOS for more than a few minutes. When OS X debuted, I had very little command line experience. Apple is now quite proud to promote its command line environment (see Based on Unix on Apple’s website). Of course, since 2001 we’ve had a Unix variant under the hood of the Mac OS. It was a big selling point for Apple in the early days of the Mac, with their literature often belittling Unix and DOS/Windows systems for their reliance on “obscure commands”. Like many Mac users, part of the reason I started using a Mac was the graphical interface and not having to use a command line.