Howto

First, I have to credit Paul for clearly documenting the process for setting up Java 1.5 support for Opera 9 in this post on the Yellow Dog Community Board. The process for setting up Java 1.6 support is only slightly different.

To get Opera 9 installed, just browse to the Opera download page and select Yellow Dog under Select distribution and vendor. At the time I’m writing this it displays a version for Yellow Dog Linux 5.0 - 5.0.1, 5.0.2 (Sony Playstation 3 and Apple G4 - G5), but this works on Yellow Dog 6 as well. When the download starts you can just select Open with Software Installer. When installation is complete, Opera should show up in your menu under Applications -> Internet, or you can start it from the command line simply by entering opera.

If you have bookmarks from Firefox that you wish to import, start Opera and go to the menu item File -> Import and Export -> Import Netscape/Firefox bookmarks … This brings up a window labeled Select Netscape bookmarks to import. In the box next to Look in, you’ll need to enter ~/.mozilla to bring up the hidden folder in your home directory where the Firefox bookmarks are stored. Then double-click on the firefox folder, double-click the next folder that comes up (a random name ending in .default), and finally select bookmarks.html. Click on Open and a window should pop up letting you know how many were imported. These will be located under Bookmarks -> Opera -> Netscape bookmarks, but you can reorganize them later with Bookmarks -> Manage bookmarks.

If you’re unfamiliar with Opera, you can read about the various features by selecting Help -> Opera Help, or simply press the F1 key.

And now for the Java 1.6 support — first you need to have IBM Java 1.6 installed as described in this Howto (skipping the Mozilla plugin part if you want). Once you have IBM Java 1.6 installed you need to open a terminal window and create a symbolic link with this command (as root using su, or use sudo):

su

[root password]

ln -s /opt/ibm/java-ppc-60/jre/lib /opt/ibm/java-ppc-60/jre/lib

exit

I realize this is creating a symbolic link to the /opt/ibm/java-ppc-60/jre/lib folder within the /opt/ibm/java-ppc-60/jre/lib folder, but that is what works. Otherwise Opera won’t recognize it as a valid path in the next step.

Back in Opera, go to the Tools -> Preferences menu and select the Advanced tab. Select Content from the list on the left side. and click the Java options… button. This will open a small window labeled Java. The box for Java path should be empty at this point. Click on Choose… and browse to the /opt/ibm/java-ppc-60/jre/lib/ppc/ folder, then click OK.

Note: If you copy/paste /opt/ibm/java-ppc-60/jre/lib/ppc/ into the Java path box instead, you still need to click on Choose… and OK or it doesn’t work properly in my experience with it.

Now click the Validate Java path button and it should say: The Java path seems to specify a valid directory. Your screen should look something like this:

Click OK to close the Validate Java path window, and OK again to close the Java window. Back on the Preferences window on the Advanced tab, check Enable Java and click OK.

Now close Opera and restart Opera. At this point you should have Java 1.6 support in Opera 9.

To confirm that it works properly I have tested this on the following sites:

http://www.time.gov — select a time zone and a clock applet should appear at the top
http://www.flyordie.com — various online multiplayer games including Reversi and 3D Pool
http://www.logmein.com — Java based remote access client for accessing Windows and Mac OSX desktops

The blurb straight from www.logmein.com:

“LogMeIn lets you access your Windows PC from anywhere in the world. All you need is a computer connected to the Internet. You see your Target PC’s full desktop and control everything on it—applications, network files, email, printing—without the hassle of further downloads or installations. You can even share files that are too large for email. There’s no need to lug around a laptop, because LogMeIn lets you access your PC from an internet cafe, an airport, or a hotel business center. You can even print documents you’ve accessed remotely.”

Some of the features listed are only included in the “Pro” version (see their product comparison page), but using only their free service you can easily access your computers running Windows or Mac OS X. To get this running on Yellow Dog Linux for the PS3, all you need to do is install the Java plugin for Firefox. There’s no messing with firewalls, port forwarding, or other security concerns — just create an account over at www.logmein.com, install the host software on your PC or Mac, and head to the login page from your PS3 (after installing the Java plugin). The initial startup process takes a few moments while the Java plugin loads., but that’s all there is to setting up the connection.

Once you’re in you can click on the Advanced option on the menu bar and select a resolution to match what you’re running on your PS3, then click on the Full Screen option. For example, I’m able to access my Windows XP machine full screen on my PS3 at 1280×720. This is how it looks when I’m running my CAD software on Windows and accessing it from my PS3 using my LogMeIn Free account (click on the thumbnail for full size image):

After formatting my “new” USB 2.0 hard drive I wanted to be able to plug it in any USB port while still being able to mount it automatically /etc/fstab. I was concerned that the device name might change if I moved it to a different USB port or booted with other memory cards or drives connected.

I’m using a FAT32 file system on this drive so it can be accessed from both Linux and the PS3’s XMB. I didn’t create a label when I originally formatted it.

To create a label for the existing FAT32 file system on my USB hard drive and have it automatically
mounted in the same location every time I boot, I followed this process (learned from this thread on fedoraforum.org):

0. Become the root user:

su -l root
[root password]

1. Confirm which device name to use with:

fdisk -l

This is how my drive shows up in the list:

Disk /dev/sdd: 60.0 GB, 60011642880 bytes
255 heads, 63 sectors/track, 7296 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes  

Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1        7296    58605088+   c  W95 FAT32 (LBA)

2. Use dosfslabel to assign a label (assuming drive is FAT32 formatted and there isn’t one already):

dosfslabel /dev/sdd1 apricorn

Where /dev/sdd1 is the current device name confirmed in Step 1, and apricorn is the label (this could be anything you want, but needs to match the LABEL used in Step 5).

3. Add the mount point:

mkdir /media/apricorn

It doesn’t necessarily have to match the label or be located in /media, but it does need to match the mount point you put in /etc/fstab in Step 5, below.

4. Check your username’s uid & gid:

id yourusername

(replace yourusername with your regular username)

5. Add this entry to /etc/fstab:

LABEL=apricorn /media/apricorn vfat sync,rw,uid=500,gid=500 0 0

Replace apricorn with the label you created in Step 2.
Replace /media/apricorn with the mount point you created in Step 3.
Replace uid=500,gid=500 with your uid & gid from Step 4 (probably the same).

The sync option causes data to be written to the drive immediately in case it is accidently removed without unmounting it first. The uid / gid option gives the user full access to the files on the drive.

6. Reboot.

Immediately after rebooting the drive should show up on your Desktop (if you’re using
Gnome) and be accessible from the mount point you created (/media/apricorn in my case).

I also used the same process for a FAT32-formatted Sandisk Extreme III 4 GB Compact Flash card on my PS3, adding more storage space that’s accessible immediately when I start up in Linux or the Game OS.

For further reference:
http://wiki.archlinux.org/index.php/Persistent_block_device_naming

UPDATE:  I’m not sure yet, but I think the Game OS doesn’t like my FAT32 (LBA) partition — the USB drive isn’t showing up as it should on the XMB.  I need to try another device formatted as FAT32 (LBA) instead of just FAT32 to see if it makes any difference.

As you can see here, here, over here, here, right here, and also here, losing track of the menu bar in e17 is a first step for many new users of YDL. And if it isn’t that, they’re wondering why their desktop is “out of alignment” after changing resolutions as can be seen here. I had the same problems myself when I first started using YDL. Another current issue with the desktop running on e17 is that it doesn’t layout icons properly and places them all in a single column. Eventually they go off the screen if you have more than a few of them.

The menu bar issue is an easy fix and is listed on the Terrasoft’s HOWTOs for Yellow Dog Linux v 5.x page under How to locate your lost E17 Shelf. The desktop alignment problem occurs after changing resolutions on the PS3, and is also an easy fix with the e17 menu item Windows > Cleanup Windows. For a new user, either of these things can happen easily and can be very frustrating if you don’t know where to look. I don’t know of any fix for the icon issue.

On my system I prefer to run e17 with the “desktop” turned off. A downside to this is you need to load the file manager any time you want to manipulate files with the GUI — the desktop is actually a Nautilus window, which explains why it covers up your e17 animated background and menu bar on virtual desktop 0,0. Fortunately it is very easy to turn the desktop off and back on again if you want.

To turn off the Nautilus desktop on e17, run this command:

gconftool-2 -s -t bool /apps/nautilus/preferences/show_desktop false

This gets rid of it instantly and it stays off until you turn it back on with this command:

gconftool-2 -s -t bool /apps/nautilus/preferences/show_desktop true

It takes a moment for it to come back up again, but that’s all there is to it.

A disadvantage of running with the desktop turned off is that it makes it more difficult to “empty the trash” — you need to show the hidden .trash folder in the Nautilus file browser and empty the contents manually. If someone knows an easy way around this, it would be a great time to use the comment function on this blog…

On the positive side, you don’t have any of the associated problems with the desktop and you can better experience the “beauty of e17.”

Reference link:
http://web.mit.edu/answers/9.4_release/9.4_skip_nautilus.html

4/6/08:  Updated ppc rpm file(s) are now hosted at the Hammer of Thyrion SourceForge site.

Here’s a youtube video showing Hexen 2 running on Yellow Dog 6 for PS3. This is made possible by the awesome Hammer of Thyrion project on Sourceforge. Like Quake 2, it has a software rendering mode that the Playstation 3 handles very well.

While there are no PPC RPM packages listed, there’s a source package file on the project’s download page which makes installing this one much easier than building from the source alone. I downloaded the hexen2-1.4.2-1.src.rpm file, then copied it to my /usr/src/yellowdog/SRPMS folder. Then from the command line, I said:

cd /usr/src/yellowdog/SRPMS
sudo setarch ppc rpmbuild --rebuild --ppc hexen2-1.4.2-1.src.rpm

I was pleasantly surprised to see it go through the entire process without a hitch! If you’ve played with many open source projects you’ll know this isn’t always the case. Moving to my /usr/src/yellowdog/RPMS folder I found the hexen2-1.4.2-1.ppc.rpm, hexen2-debuginfo-1.4.2-1.ppc.rpm, and hexenworld-1.4.2-1.ppc.rpm it had generated. So I just browsed to it with the file manager and double-clicked on the hexen2-1.4.2-1.ppc.rpm file to start the install. Again, no problems at all. If you run into trouble here, see my list of Third party repos for Yellow Dog 6. Rebuilding the package will require SDL-devel, at least.

After installing from the new hexen2-1.4.2-1.ppc.rpm I saw I had a Hexen 2 menu item under Applications -> Games. Of course now I needed the data files for Hexen 2. If you want to use the demo files you need version 1.11 of the Hexen 2 demo. Just search Google for hexen 2 demo 1.11 and you should find it available from several sources.

The Hexen 2 demo comes in the form of an .EXE file, but that’s OK — you can still use the unzip command to extract the file. For example, assuming you have downloaded the file to your Desktop, open a terminal window and:

unzip -j ~/Desktop/h2demo.exe Install/Hexen2/data1/*.pak

That will extract the pak0.pak file to your current directory (the -j switch tells unzip you just want to extract the file not create directories). Then you need to move the pak0.pak file to the necessary location: /usr/games/hexen2/data1

sudo mv pak0.pak /usr/games/hexen2/data1

After that, you should be ready to run Hexen 2. If you want to use the full version of Hexen 2, see the readme on the Hammer of Thyrion project page for details.

Start Hexen 2 from the menu item Applications -> Games -> Hexen 2. This should bring up a Hexen II Launcher window. Uncheck the box next to OpenGL, optionally leave Full Screen checked, and select SDL for sound, sample rate 48000 (optional). Without OpenGL checked it will allow you to select a max resolution of 640×480 — don’t worry, you can change it later in the game menu. Finally, click on Play Hexen II. If everything went well you should be up and running!

On my system I’m running at 1280×720, but the game starts at 640×480 at first. If I bring up the game menu I can select Options -> Video Modes and change it to 1280×720 (you can see me doing that in the video).

Maybe they’ll host PPC rpm files on the Hammer of Thyrion page so you won’t have to go through the process of rebuilding the source package… If not, I created a Yellow Dog Linux group on Yahoo! Groups that has some limited file storage. You have to register (free) with Yahoo Groups to access it. In the files area you’ll find a ready-made hexen2-1.4.2-1.ppc.rpm file, along with one I created for Quake 2: quake2-r0.16.1-ydl6.ppc.rpm.

Hopefully all of this is OK with everyone involved …

I’m relatively new to Linux, so when I’m not mucking around and hosing things up on my own I read a lot of guides. In Mauriat Miranda’s excellent Fedora 6 Install Guide I found a quick and easy way to setup sudo so you don’t have to use the su command and your root password all the time.

su

[root password]

echo 'loginname ALL=(ALL) ALL'>> /etc/sudoers

exit

Where ‘loginname’ is your user account. This only needs to be done once. When using sudo and you’re asked for a password, it is the password for your user account, not root.

For example, when you need to edit your /etc/yaboot.conf file, you can say:

sudo gedit /etc/yaboot.conf

Enter your regular user account password. You’ll be able to edit and save the file as if you were logged in as root. In practice I’m finding this to be much more convenient than using su all the time.

Here’s a way to quickly get up and running with Amiga OS 3.X on your PS3 running Yellow Dog, complete with internet access running through the E-UAE emulator and virtual hard disks.

1. First, install E-UAE, an Amiga emulator based on WinUAE. I use the version from the Dribble repository, installed via Add/Remove Software or simply yum install e-uae. Setup instructions for Dribble and other repos can be found here. Alternatively, you can manually install the linux-ppc binary located here.

2. As noted on the E-UAE site, “you will need access to an image of some version of the Amiga Kickstart ROM (although UAE does include a ROM emulation which may work with some old games). The Amiga Kickstart ROMs are copyrighted material and may not be freely distributed (so don’t ask me for a copy). If you don’t have an Amiga from which you can legally make a ROM image, a selection of ROM images are available for purchase online from Cloanto - publishers of the Amiga Forever distribution.”

I got the Premium Edition of Amiga Forever by Cloanto, but I think the Plus and Online Editions include the same files I’m using below.

With the Premium Edition I downloaded an installer file called “afplus.exe” that I had to run on a Windows machine to extract the files. I think the Plus Edition downloads as an ISO file (in a ZIP file) so you can avoid installing on Windows. See here for more info.

The installer extracted a folder called “Amiga Files” in My Documents folder on my Windows machine. In that folder was a “System” folder. Quoting the readme file, The “System” directory contains all Amiga system files, including ROM and OS files, workbench ADF files (floppy disk images), and the ‘System” and “Work” partitions of the Amiga OS 3.X environment (which are mapped to directories on the host file system).

To transfer the contents to my PS3 I just shared the folder and copied it over my network. Alternatively you could burn the files to a CD, copy to a memory card, etc. The entire Amiga OS and applications only take up around 30 MB.

The actual folders I needed were: “Amiga Files/System/dir” (both the “System” and “Work” folders) and the “Amiga Files/System/rom” folder.

Note: It took a couple of weeks but eventually I received the CD + 2 DVDs for Amiga Forever Premium Edition from Cloanto. On the Amiga Forever 2006 CD, the System and Work folders are located on the CD under: /Emulation/System/dir. The roms are in the /Emulation/System/rom folder on the CD.

The “Amiga Files/System/dir/System” and “Amiga Files/System/dir/Work” folders will be set up as virtual hard drive partitions in E-UAE.

The “Amiga Files/System/rom” folder includes the Amiga ROM files needed by E-UAE (and also a key file required to use Cloanto’s ROMs).

So, on the PS3 I now have the following folders:
~/UAE/System
~/UAE/Work
~/UAE/rom

3. Then E-UAE needs to be configured to emulate the right Amiga hardware, use the system ROM file, and use the System and Work folders as virtual hard drives. E-UAE uses a config file in your home folder called .uaerc

To make things easier, you can copy/paste/modify this one (save it in your home folder as .uaerc ):

unix.rom_path=/home/bill/UAE/rom/
unix.floppy_path=/mnt/shared/emulators/amiga
cpu_type=68040
chipset=aga
kickstart_rom_file=/home/bill/UAE/rom/amiga-os-310.rom
kickstart_key_file=/home/bill/UAE/rom/rom.key
chipmem_size=4
fastmem_size=8
z3mem_size=64
gfxcard_size=32
cpu_speed=max
filesystem2=rw,DH0:System:/home/bill/UAE/System,1
filesystem2=rw,DH1:Work:/home/bill/UAE/Work,0
gfx_width_fullscreen=960
gfx_height_fullscreen=720
gfx_fullscreen_amiga=false
use_gui=false
gfx_linemode=double
gfx_center_vertical=true
gfx_center_vertical=smart
show_leds=true
joyport0=mouse
joyport1=joy0
bsdsocket_emu=true

Note that you’ll have to modify these file/folder locations to match your own in the above config file:

unix.rom_path=/home/bill/UAE/rom/ (the rom folder path)
unix.floppy_path=/mnt/shared/emulators/amiga (this is where I keep my .ADF floppy disk images, not necessary)
kickstart_rom_file=/home/bill/UAE/rom/amiga-os-310.rom (the ROM version required to use Amiga OS3.X or Workbench 3.1)
kickstart_key_file=/home/bill/UAE/rom/rom.key (the key file required to use Cloanto’s ROM file)
filesystem2=rw,DH0:System:/home/bill/UAE/System,1 (path to the System folder copied from Amiga Forever, works like a hard drive on the Amiga, DH0:)
filesystem2=rw,DH1:Work:/home/bill/UAE/Work,0 (path to the Work folder copied from Amiga Forever, works like a hard drive on the Amiga, DH1:)

Note that you have to use the actual path names and not ~ or $HOME …

Also, you may need to adjust the fullscreen resolution — I have mine set this way since I’m running my PS3 at 720p:
gfx_width_fullscreen=960
gfx_height_fullscreen=720

4. Finally, you can start E-UAE from a terminal window (uae) or the Applications -> Games menu in e17. With the above settings in the config file, it should load straight into the Amiga OS3.X Workbench. Pressing F12-s toggles between windowed and full screen.

You can actually run Amiga OS3.X at 1280×720, full screen, on the PS3. On the Amiga Workbench, open the System drive, then Prefs, then ScreenMode, and select uaegfx: 1280×720 32bit under Display Mode. (assuming you’re running YDL at 720p)

To install additional software besides what is already included with Yellow Dog 6, I’m using three additional repositories. These are set up by saving them as text files in the /etc/yum.repos.d folder (root privilege required). The file names are: fedora-extras.repo, livna-stable.repo, and dribble.repo

NOTE: These are clearly NOT supported by Terrasoft and could potentially create stability issues on your system. That said, I haven’t had any problems with using them other than some of the applications not working properly. In some cases an RPM will call for a dependency not included in these or the yellowdog repos since they’re included in Fedora Core 6 base. In this case you can install the dependency directly from the Fedore Core 6 download server.

fedora-extras.repo

[fedora-extras]

name=Fedora Extras

baseurl=http://download.fedora.redhat.com/pub/fedora/linux/extras/6/ppc

enabled=1

gpgcheck=0

livna-stable.repo

[livna-stable]

name=Livna.org Fedora Compatible Packages (stable)

baseurl=http://rpm.livna.org/fedora/6/ppc

enabled=1

gpgcheck=0

dribble.repo

[dribble]

name=Dribble for Fedora 7 - ppc

baseurl=http://dribble.org.uk/repo/7/ppc

enabled=1

gpgcheck=0

After installing those it appears to be a good idea to install ProtectBase to prevent files from the yellowdog-base repository from being overwritten by files from these or other third party repositories. Here’s how to install and configure ProtectBase to protect your yellowdog-base.repo:

su
[root password]

yum install yum-protectbase

echo 'protect=1' >> /etc/yum.repos.d/yellowdog-base.repo

echo 'protect=1' >> /etc/yum.repos.d/yellowdog-updates.repo

exit

If you need to disable protection in the future, just edit /etc/yum.repos.d/yellowdog-base.repo and change protect=1 to protect=0.

UPDATED 5/10/08: Using Fedora 7 packages from Dribble now, and protecting both yellowdog-base and yellowdog-updates (so updates will install properly)

See it in action on youtube!

UPDATE:  I have added rpm package built for Yellow Dog 6 in the files area of the Yahoo! Groups site, so it is no longer necessary to build from the source as described below.  The demo or full version files are still required.  The full version is available on Steam.

Even without any hardware accelerated OpenGL, Quake 2 runs great on the Playstation 3 with Yellow Dog 6. I normally play at 960×720 and it runs around 3o FPS (according to timerefresh). The gameplay is smooth at this speed and very entertaining. Following these instructions should have you dodging, ducking, and spreading giblets all over the place in no time!

This will require either the Quake 2 demo files or the full retail version of Quake 2. If you already have the Quake 4 Special DVD Edition, it includes a second disc with Quake 2 + Expansion packs. This makes it very easy to copy the data files over to your PS3.

Just copy the entire contents of /path/to/your/DVD/setup/data to where you want it on your PS3 (like in your home folder under quake2, for example: ~/quake2). Instructions for using the demo files are included in the README with the source.

Building and Installing the game:

I’m running it using the source port found on icculus.org.Compiling from the quake2-r0.16.1.tar.gz source required editing the make file — the portion I changed looks like this:

BUILD_SDLQUAKE2=YES # sdlquake2 executable (uses SDL for cdrom and sound)
BUILD_SVGA=NO # SVGAlib driver. Seems to work fine.
BUILD_X11=NO # X11 software driver. Works somewhat ok.
BUILD_GLX=NO # X11 GLX driver. Works somewhat ok.
BUILD_FXGL=NO # FXMesa driver. Not tested. (used only for V1 and V2).
BUILD_SDL=YES # SDL software driver. Works fine for some people.
BUILD_SDLGL=NO # SDL OpenGL driver. Works fine for some people.
BUILD_CTFDLL=YES # game$(ARCH).so for ctf
BUILD_XATRIX=NO # game$(ARCH).so for xatrix (see README.r for details)
BUILD_ROGUE=NO # game$(ARCH).so for rogue (see README.r for details)
BUILD_JOYSTICK=YES # build in joystick support
BUILD_ARTS=NO # build in support for libaRts sound.
BUILD_ALSA=NO # build in support for ALSA (default sound on 2.6)
BUILD_DEDICATED=NO # build a dedicated quake2 server
BUILD_AA=NO # build the ascii soft renderer.
BUILD_QMAX=NO # build the fancier GL graphics
BUILD_RETEXTURE=NO # build a version supporting retextured graphics
BUILD_REDBLUE=NO # build a red-blue 3d glasses renderer...
STATICSDL=NO
SDLDIR=/usr/local/lib

Then compile and install like so:

[installdir] is wherever you want to install the original quake2 game files — I used ~/quake2
The releaseppc folder will be found in your source dir after you compile.

0. edit Makefile as described above, then ‘make ARCH=ppc‘ When compiling is done you’ll have a new folder called releaseppc. If you get errors when trying to compile you may be missing some dependencies.
1. copy releaseppc/gameppc.so to [installdir]/baseq2/
2. copy releaseppc/ref_*.so to [installdir]
3. copy releaseppc/sdlquake2 to [installdir]
4. copy releaseppc/ctf/gameppc.so to [installdir]/ctf/ (optional)
5. copy releaseppc/sdlquake2 to your /usr/local/bin folder (you need root privilege to do this)

Once you have all that set up you start quake2 like this:

sdlquake2 +set vid_ref=softsdl +set basedir ~/quake2
(where ~/quake2 is the [installdir] you copied the original Quake 2 files and the new binaries)

Note:
If the default resolution is higher than your screen resolution you can start in windowed mode and change it in the game menu. To start in windowed mode instead:

sdlquake2 +set vid_fullscreen 0 +set vid_ref=softsdl +set basedir ~/quake2

Try running from the command line first to see if you get any errors, then you can set it up as a launcher on the desktop, or as a new menu item using alacarte.

Sun offers Java for x86 and x64 Linux that can’t be used on the PS3 (which runs PPC Linux). However, IBM produces an implementation of Java that does work on PPC Linux. Here’s how to install the IBM Java plugin for Firefox on Yellow Dog 6:

Install IBM Java

Go here:
http://www-128.ibm.com/developerworks/java/jdk/linux/download.html

Click on the link for Java SE Version 6 for 32-bit iSeries/pSeries

You’ll need to register with IBM, sign in, accept license agreement, yada
yada yada…

Click on the link to Download using http

Click on this one:
rpm format
ibm-java-ppc-jre-6.0-0.0.ppc.rpm

Open with system-install-packages, Click OK

Install the Mozilla plugin

Once IBM Java install is finished, open a terminal window.
Applications -> Accessories -> Terminal

Create a symbolic link to /opt/ibm/java-ppc-60/jre/plugin/ppc/ns7/libjavaplugin_oji.so in the /usr/lib/mozilla/plugins folder:

su
[enter root password]

cd /usr/lib/mozilla/plugins

ln -s /opt/ibm/java-ppc-60/jre/plugin/ppc/ns7/libjavaplugin_oji.so

exit

Confirm Installation

Restart Firefox if it’s already running.

In Firefox, where you normally would enter an http: address, enter:

about:plugins

You should see this show up in the list:

Java(TM) Plug-in 1.6.0-internal-root_16_nov_2007_18_41-b00

After this, you should be able to run Java applets in Firefox 2, complete
with sound.

Of course then you’ll want to make sure it’s working:

http://www.time.gov
Try selecting a time zone … ZZZzz…

http://www.flyordie.com/
A very active mutliplayer Java game site featuring pool, chess, Reversi,
etc. Expect to see lots of banner ads.

http://www.runescape.com
A Java-based MMORPG (Massively Multiplayer Online Role-Playing Game)

NOTE:
If you need to use Java 5 instead, select J2SE 5.0 for 32-bit iSeries/pSeries. Download/install this one: ibm-java2-ppc-jre-5.0-6.0.ppc.rpm, and to create the symbolic link, use this:

ln -s /opt/ibm/java2-ppc-50/jre/bin/libjavaplugin_ojigtk2.so

All other steps remain the same.