osascript -e 'tell app "ARDAgent" to do shell script "whoami"';

http://darwinports.com/ 

Created on Apr 10, 2007, 23:25 by Rui Carmo, not updated since.

Update: Mark Wilson has gone through this with a more recent version of VMware, and his article is likely to be more useful.Regarding this piece, thanks to Chris Dagdigian for pointing out the need for trusted Xforwarding.

One of the biggest issues with managing VMware Server for me has always been not having a native Mac OS X remote administration client (or a Mac OS X anything, but that’s another story).So, with every release, I kept trying to find a way to both see and control my virtual machine consoles by running vmware-console on the server and forwarding the X display to myMac - which never seemed to work due to various X11 quirks - either the application bombed instantly, or there were masses of debug logging - but never a working remote console.However, after months of virtual head-banging, Chris Dagdigian e-mailed me a note saying that he had got his vmware-console running by using trusted X forwarding, and after a while I had the rest figured out - keyboard mappings and all.The following notes assume you have a Linux-based VMware Server host (running build 22088) and that you can access it over SSH from a Mac with X11 installed.

On The VMware Host

Keyboard detection doesn’t work properly when you’re using X11.app, so you have to go to/usr/lib/vmware/xkeymap and pick a suitable keyboard map (see this for more info).You then have to edit ~/.vmware/preferences to set that keyboard map:

xkeymap.language="pt104"

…and pay attention to the vmware-console output.

On Mac OS X:

Start X11.app, open an xterm and SSH to the VMware Server using trusted X forwarding:

monotith:~ user$ ssh -Y user@vmware Last login: Sun Mar 12 21:42:49 2006 from monolith.internal.taoofmac.com [user@vmware ~]$ vmware-console

And presto, it should appear on your X11 display. There is a very important point that needs stressing, though -

If VMware is unable to detect your keyboard settings, you won’t be able to control guest virtual machines properly - you won’t even be able to see the console.

Hence the importance of setting the keymap properly. You might also want to remember that some key combos are slightly different on the Mac - for instance, Ctrl+Alt to exit a VM is actually Ctrl+Command, etc., etc.Regarding xauth and X11.app in other contexts, some people have noted that xauthusually works for them after issuing the following command in xterm:

xauth generate :0 . trusted

Although I’ve yet to establish a relationship, it seems to have helped me as well.

Terminal solutionIf you don’t mind using Terminal, you can kill all pending print jobs with one simple command:

cancel -a -

Every time you execute a command by using only the command’s name (for example, ls or pwd), your shell looks for the command in a list of directories. That list is stored in the PATH environment variable. The PATH list provides a shortcut for finding commands.

If it weren’t for the PATH list, you would have to type /bin/ls instead of ls, and /usr/bin /vi instead of vi. The command-line utilities supplied with the Mac OS X Developer Tools are located in /Developer/Tools (some of those utilities, such as CpMac and MvMac, are described in Chapter 2, “Using the Command Line”). The /Developer/Tools directory is not normally in your PATH, so if you use any of the commands in /Developer/Tools, you need to type their full pathnames, unless you add the directory /Developer/Tools to your PATH. Here’s how to do that.

Adding a directory to your PATH in tcsh:

1. Start by editing your ~/.tcshrc file. (Review Chapter 5, “Using Files and Directories,” about editing files from the command line.) If you are using vi, the command is vi ~/.tcshrc
2. Add a line that says

   set path = ( $path /Developer/Tools )

   This may seem a little odd. After all, you are trying to set the PATH environment variable, not path. What’s going on? Well, tcsh uses an unusual method to set the PATH variable.

   Tcsh requires that you set the shell variable path, and then tcsh sets the actual PATH environment variable. As discussed earlier, shell variables are variables created in your shell that are available only in the shell you are currently using. They are not passed on to child processes as environment variables are.

   Also notice how the command line includes the existing $path value in the new definition, thus adding the new directory to the list. Without $path in the command line, the result would be to replace the old PATH with the single new directory—not at all what you want.

3. Save your file (the command will depend on which editor you’re using).
4. Quit the editor (this command will also depend on which editor you’re using). The change will take effect in the next shell you start.
5. Open a new Terminal window to test the change.
6. echo $PATHYou’ll see the new directory at the end of the list.
7. Test using one of the developer tools without typing its full path—for example,

   GetFileInfo "/Applications (Mac OS
    →9)/SimpleText"

   Figure 7.7 shows the output from the GetFileInfo command.

   Figure 7.7 Using the GetFileInfo command once it is in your PATH.

   If you are using the bash shell or the sh shell, then you add a directory to your PATH by directly setting the PATH environment variable. Putting this setting in your ~/.profile ensures that it takes effect each time you start a new shell.

Adding a directory to your PATH in bash or sh:

1. Edit your ~/.profile file.If you are using the vi editor, the command is

   vi ~/.profile

2. Add a line to the file that says

   export PATH="$PATH:/Developer/Tools"

   Notice how the new value includes the current value of $PATH, then a colon (no spaces!), and then the new directory.

3. Save the file.
4. Quit the editor.The change takes effect immediately.
5. You can check it with

   echo $PATH

Adds native support for many popular video formats.
http://perian.org/

Full Screen

Command + Shift + 3 Completa
Command + Shift + 4 Partes
Command + Shift + 4 + Space Bar     Camera

PATH=”$PATH:/Library/Application Support/VMware Fusion”

  ex 4: vmware-vdiskmanager -x 36Gb myDisk.vmdk

Heres a recap for everyone to Install HP LaserJet 1020 on Mac OSX. 1)

Download; http://www.narc.ca/1601-LJ_1022_Series_OSX.dmg (Old version)

2)If you have anything for the HP 1020 in “/Library/Reciepts” delete it.

3) Delete anything for the HP 1020 in Printer in “Printer Setup Utility”

4) Add new printer in “Printer Setup Utility”, select HP LaserJet 1020, driver should come up, click ADD Then you should be able to print.. glad we finally got around this one.. and one big FU to HP.

descarga driver 1020