>>  
Command line to show installed office 2004 version
16/07/12 @ 10:40:45 pm, Categories: Mac OS X, 41 words   English (AU)

This is not fool proof, but seems to work pretty well:

ls -1rt /Applications/Microsoft\ Office\ 2004/Updater\ Logs/ | tail -n1

It will give output like:
11.6.2 Update Log.txt

it just gives you the newest file/folder in the Updater Logs

Trackback (0) | Permalink
Get application version from command line
16/07/12 @ 10:39:57 pm, Categories: Mac OS X, 82 words   English (AU)

This works with many applications. Most applications are .app bundles, and have an Info.plist with the version number. You can pull this out directly with PlistBuddy (if you know the key name).

With some apps, you need to know also where to look.

/usr/libexec/PlistBuddy -c "Print CFBundleVersion" /Applications/Microsoft\ Office\ 2008/Office/MicrosoftComponentPlugin.framework/Resources/Info.plist

Handy, if you want to do a bulk update, but want to know which packages to install first, or which computers need updating.

Trackback (0) | Permalink
ASR multicast restore
16/07/12 @ 10:33:36 pm, Categories: Mac OS X, 264 words   English (AU)

Full article here

You do this from terminal. So you can do it from at least 10.4+ install media.

You will need an image (dmg) ready, and accessible from the computer running asr. First prepare the image with:

asr -imagescan image.dmg

For unicast, you can now chuck the image on a share and run:
asr -source afp://fileserver.example.com/image.dmg -target /Volumes/MacintoshHD -erase

The tricky bit:
You need to create a plist config file. It needs bugger all inside it, but is a necessary step.

Two keys are required—Data Rate and Multicast Address—but additional keys are supported to specify functionality. You can create it in property list editor, or just fire up pico and make sure you create all the necessary headers by hand.
It should look something like:

Code:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Data Rate</key>
        <integer>600000</integer>
        <key>Multicast Address</key>
        <string>224.77.2.121</string>
</dict>
</plist>

Now you have created the plist, you can start your asr multicast server

asr -source multicastimage.dmg -server configuration.plist

And from the client computers, you can join the multicast with:

asr -source asr://myserver.com -target /Volumes/MacintoshHD -erase

The rest of the article discusses sensible network considerations (multicast traffic is something which needs to be managed carefully), and GUI front ends (what's the point? ;) )

Trackback (0) | Permalink
Logout user via terminal
16/07/12 @ 10:29:51 pm, Categories: Mac OS X, 238 words   English (AU)

Yes, sometimes you need to log people out (tidily), and sometimes you don't have access to their screen. This is a one liner that does it.

/bin/launchctl bsexec $(ps -xawwo pid,command | grep "/System/Library/CoreServices/Finder.app/Contents/MacOS/Finder$" | awk '{print $1}') /usr/bin/osascript -e 'tell application "System Events" to log out';

Taking it apart, we are using bsexec option of launchctl to execute the osascript in the same "Mach bootstrap namespace hierarchy" as Finder. The whole middle bit (the bit in $(...)) is just doing a ps, grepping out the Finder process, and then awking the pid for the Finder process. What if there are multiple users with Finder processes? Then it breaks. But really, how often does that happen.

Please don't ask me what a "Mach bootstrap namespace hierarchy" is. The basic idea, is that if you just try to the osascript to log out, the osascript won't reach "System Events" (which belongs to Finder), and it doesn't work.

Now, the quick and dirty way to do this is to kill the loginwindow process. But that doesn't prompt users to save work, or close out apps properly or any of the other house keeping that actually Logging Out is meant to do.

Also, using AppleScript (via the terminal's open scripting architecture support) to quit Applications is handy:

osascript -e 'tell application "Microsoft Outlook" to quit';
osascript -e 'tell application "FireFox" to quit';

Trackback (0) | Permalink
Cisco console to Mac?
16/07/12 @ 09:58:09 pm, Categories: Mac OS X, 429 words   English (AU)

So, Cisco being an old and venerable company, have a few quirks. One of these is the use of serial console cables. Basically, an RS-232 dealio. You remember RS-232? If you owned a computer in the 80s or early 90s, likely you had an RS-232 port and probably used it once or twice. They used to have lots of cool stuff, including Modems. Which was a good thing, since it meant that you didn't need to worry too much about what flavour computer you had. RS-232 is pretty simple, easy to implement in hardware and software and thus ubiquitous.

On the Amiga, I used the serial port for two things: MIDI (it's nearly the same thing as RS-232, except a slightly odd clock and some optical isolation, and a different pin out), and hooking up the dial up modem.

The serial port was also popular among hobbyists and in industrial automation. Many computers also used the serial to output debug info during POST. Sun boxes used (still use?) serial for initial set up and configuration.

So, a venerable history. The downside is that its large form factor and low speed mean that it has lost favour with computer manufacturers. It has become a challenge to find a laptop with a real Serial port.

But Cisco still use it as the connection of last resort on the bulk of their products. They've designed their system with the assumption that if you can get access to the serial port, then you are legit. This means that if you've stuffed up your conf, or need to unlock someone elses (perhaps you like 2nd hand gear), then you may well have to resort to that serial cable.

So, you can hook it up to a PC (or something else) with a 'real' serial port, or use one of the known working USB to RS-232 dongles.

From memory, the only 'Mac' products Apple ever supplied with genuine RS-232 ports were the Xserves. And yes, you can use the serial port on an Xserve to hook up a Cisco console cable. And why not? (Apart from the fact that the newest Xserve is years old). In all likelihood they are living together in a rack somewhere.

It also possible to use one of the known working USB to RS-232 dongles with a Mac.

And how to fire it up and get it working? Well, on an Xserve running 10.5:

Code:

/usr/libexec/serial/SerialTerminalSupport stop
screen /dev/cu.serial

Or if you have a Keyspan USB to RS-232 adaptor:

screen /dev/tty.KeySerial1 9600

Of course, there's more.

Trackback (0) | Permalink

:: Next Page >>

WTF?
blogs
Categories
Archives
November 2017
Mon Tue Wed Thu Fri Sat Sun
 << <   > >>
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      
User Functions

Management

Misc

Search

Skins

XML Feeds

links
Credits