sudo vi /etc/paths

When copying files from one location to another, I have always found it an annoying process to drag the files to one location and then go back and delete them from the original location.

The default drag and drop process in OS X is to COPY files.

We want to be able to MOVE files.

To MOVE a file is to actually copy files to a new location and to delete them from the original location.

OS X will move the file if you hold the CMD key while you drag and drop.

One caveat:

Something that confuses people is what happens if duplicate files are found during the move drag and drop. If you release the CMD key to answer the dialog box that appears, the file will be copied but not moved. If you continue to hold the CMD key as you click the Replace button, the move action will be completed.

source http://www.tech-recipes.com/rx/2581/os_x_move_files_instead_copying/

To work with mobile application, one can follow the helpful Netbeans + Mobility + Mpowerplayer Guide. However, the guide did not cover how to add optional java package such as jsr75, which I would cover below.

The complete steps to set up a mobile development environment with Netbeans + J2ME Mobility Pack + Visual Designer + Mpowerplayer emulator + optional java package:

1. Download Netbeans for Mac OS X.
2. Install either the Java SE or Web & Java EE version of the IDE.
3. After installation, start the IDE and go to Tools > Plugins.
4. Click the Available Plugins tab. Under Category go to Mobility.
5. Check the boxes for Visual Mobility Designer, and Mobility and click Install.
6. Download the Mpowerplayer SDK and install it.
7. In the NetBeans IDE main menu, choose Tools > Java Platform Manager.
8. Click Add Platform. Select the folder that contains the MPowerPlayer SDK (mpp-sdk). Click Search to locate the emulator in the folder. When the IDE finds the MPowerPlayer SDK, click Next.
9. Click Finish. The IDE registers the MIDP platform. You can now build and run a MIDP 2.0 application. But the setup still lacks optional java packages.
10. Download SUN WTK 2.5.2 (for Windows and Linux)
11. Unzip the .bin. For example, run the command:

    $ unzip sun_java_wireless_toolkit-2_5_2-linux.bin

12. Under /lib, copy the optional java package you need eg. jsr75, jsr 179 or even midpapi21.jar. Put them under /Applications/mpp-sdk/stubs/
13. In your project, edit project.properties and add to platform.bootclasspath the optional java package. eg.

    platform.bootclasspath=${platform.home}/stubs/mmapi.jar:${platform.home}/stubs/midp-2.0.jar:${platform.home}/stubs/cldc-1.0.jar:${platform.home}/stubs/jsr75.jar

14. Begin mobile development on Mac OS X!

Bootloader
- chameleon v1
x86 Patch
- DSDT
ACPI
-x86 ACPI
-DISABLE
-OHR
Kernel
- 9.7.0 kernel voodoo
Driver VGA
- NVkush
Sound
-voodoo HDA driver
-Azalia Audio Driver
PS/2 mouse/keyboard
-Apple PS/2 driver
-NTFS 3G
Network
-Marvell Yukon 88E8056

Patch

ethernet: Yukon8053

$mv AppleYukon.kext /System/Library/Extensions/
$sudo chmod -R 755 /System/Library/Extensions/AppleYukon.kext
$sudo chown -R 0:0 /System/Library/Extensions/AppleYukon.kext
$sudo kextload -v /System/Library/Extensions/AppleYukon.kext
$sudo rm /System/Library/Extensions.mkext

eVGA 250GTS

$sudo su -
$sudo mv NVinject.kext /System/Library/Extensions
$chown -R 0:0 /System/Library/Extensions/NVinject.kext
$chmod -R 755 /System/Library/Extensions/NVinject.kext
$rm -rf /System/Library/Extensions.mkext
$rm -rf /System/Library/Extensions/Caches/
$rm -rf /System/Library/Caches/

]]> http://www.jiramot.info/iatos-v7-on-my-pc/feed 0 http://www.jiramot.info/how-to-edit-the-hosts-file-in-mac-os-x-%e2%80%93-leopard http://www.jiramot.info/how-to-edit-the-hosts-file-in-mac-os-x-%e2%80%93-leopard#comments Mon, 27 Jul 2009 17:48:09 +0000 admin http://www.jiramot.info/?p=350 Introduction

The hosts file is a text file that maps hostnames to IP addresses.
Upon typing a url address on the browser, the system is checking if there is a relevant entry on the hosts file and gets the corresponding IP address, else it resolves the IP via the active connection’s DNS servers.

The hosts file can be edited to block certain hostnames (like ad-serving/malicious hosts), or used for web development purposes, i.e. to redirect domains to local addresses.

Editing the hosts file

Editing the hosts file in Mac OS X – Leopard, is a pretty easy task, especially if you are familiar with the terminal.

Step 1 – Open the Terminal.app

Either by start typing Terminal on the Spotlight, or by going into Applications -> Utilities -> Terminal.

Step 2 – Open the hosts file

Open the hosts by typing on the Terminal that you have just opened:

view plaincopy to clipboardprint?

1. $ sudo nano /private/etc/hosts

$ sudo nano /private/etc/hosts

Type your user password when prompted.

Step 3 – Edit the hosts file

The hosts file contains some comments (lines starting with the # symbol), as well as some default hostname mappings (e.g. 127.0.0.1 – localhost).
Simply append your new mappings underneath the default ones. Or edit one of the default values if you know what you are doing!
You can navigate the file using the arrow keys.

Step 4 – Save the hosts file

When done editing the hosts file, press control-o to save the file.
Press enter on the filename prompt, and control-x to exit the editor.

Step 5 – Flush the DNS cache

On Leopard you can issue a simple Terminal command to flush the DNS cache, and have your host file changes to take immediate effect:

view plaincopy to clipboardprint?

1. $ dscacheutil -flushcache

$ dscacheutil -flushcache

You can now test your new mapping on the browser!

]]> http://www.jiramot.info/how-to-edit-the-hosts-file-in-mac-os-x-%e2%80%93-leopard/feed 0 http://www.jiramot.info/os-x-change-your-path-environment-variable http://www.jiramot.info/os-x-change-your-path-environment-variable#comments Wed, 15 Jul 2009 13:11:29 +0000 admin http://www.jiramot.info/?p=327 To change your path, you must edit the .profile file in your home directory. If you are comfortable using the vi editor, you probably don’t need to read any further. If not, then you can use TextEdit to edit your .profile.

The default .profile is fairly short. The .profile is read when you open a Terminal window and each line is executed just like typing a command into the Terminal window. While this is handy because you can make any available command run whenever you drop to a shell, we’re concerned with changing an environment variable, PATH.

In your editor, find the line that starts with export PATH= and give it a look to make sure it doesn’t already contain the directory path you’re going to add. Sometimes the PATH variable can get lengthy, but chances are yours just has a few directories separated by colons, perhaps something like this:

export PATH=/opt/local/bin:/opt/local/sbin:$PATH

There are a few things to note before making changes. The format of this line is important. The use of spaces in this command, or their lack, matters. In particular, there cannot be spaces around the equals sign or between any of the directories. If there are spaces in the directory name you want to add, you’ll need to escape the space by preceeding it with a \backslash or by putting the path in quotes (export PATH=”/path/here”).

The export= keyword in front of that line has a very specific purpose. Defining a variable without exporting it makes it available only to the current shell, not to any subsequent shells. You may think to yourself that you don’t plan to make any subsequent shells, but this happens whenever you run a shell script. If the PATH variable was not exported, when you run a shell script, the PATH would no longer exist and it is possible that the script would fail.

The $PATH at the end of the example above tacks the previous value of the variable (if it exists) onto the end of the PATH. By default, this will add ‘:/bin:/sbin:/usr/bin:/usr/sbin’ to the end of the PATH for you which is useful because most everything you run from the command line lives there.

So, to add a new directory to the path, simply add it to the existing PATH line in .profile being careful to separate it from other directories there with colons and careful not to introduce unwanted spaces (everything after the space will be ignored). For example, to add the directory /mightyq/bin to the PATH shown above, the line could become any of the following examples:

export PATH=/mightyq/bin:/opt/local/bin:/opt/local/sbin:$PATH
export PATH=/opt/local/bin:/mightyq/bin:/opt/local/sbin:$PATH
export PATH=/opt/local/bin:/opt/local/sbin:$PATH:/mightyq/bin

Note that in the third example the new directory is added to the end of the PATH. You have the ability to optimize the searches your shell will do on your behalf each time you run a command by organizing your PATH logically. Putting less frequently used or really massive directories later in the path may give you a little performance boost (although these days things are pretty fast, so you have to be a little anal to really enjoy this).

If you don’t need a directory in your path, you can reverse the process by deleting the unwanted directory still taking care to preserve the no spaces, colon separation rules.

One last note, to test the change you made, you can use the echo command, but you need to make the shell reload the .profile first. Assuming you are in your home directory (if not, running ‘cd’ without any options will take you there), run these commands:

. ./.profile
echo $PATH

The first is a neat little command in that it shows three uses or interpretations of the period in a single line. The first . is a shortcut to cause the shell to ’source’ or load the contents of the subsequent file as itself, in the manner that the shell uses when you login to a system or start a Terminal window. If you simply executed these commands like a shell script (bash .profile, for example) you would start a new shell, that shell would get the variable set, and at the end of running the .profile script, that new shell would cease to exist and the newly defined variables would be relegated to the missing sock universe.

The second period means the current working directory. It’s not compulsory in any way in this command, but it’s habit from explaining the dots to folks, so I type it all the time now. In this context, you could also use ~/.profile as ~ explicitly means your home directory.

The last dot causes the .profile to be hidden from view in a normal directory listing or Finder view. It doesn’t change the file in any other way, it just make it invisible and de-clutters your directories. To see hidden files, you can use ‘ls -a’ and you might be surprised by what you find.

]]> http://www.jiramot.info/os-x-change-your-path-environment-variable/feed 0 http://www.jiramot.info/check-up-your-macbook-pro http://www.jiramot.info/check-up-your-macbook-pro#comments Tue, 30 Jun 2009 22:12:22 +0000 admin http://www.jiramot.info/?p=267 check a lcd panel

ioreg -lw0 | grep IODisplayEDID | sed “/[^<]*

]]> http://www.jiramot.info/check-up-your-macbook-pro/feed 0