Search This Blog
Showing posts with label (Open)Solaris. Show all posts
Showing posts with label (Open)Solaris. Show all posts
22 March 2011
27 October 2010
In case anyone missed it... departures from Oracle...
I think this quote says it all:
Doug Lea resigns from the JCPThere are quite a few more as well.
“I believe that the JCP is no longer a credible specification and standards body, and there is no remaining useful role for an independent advocate for the academic and research community on the EC.”
13 August 2010
Oracle kills OpenSolaris
I just have to wonder. When Oracle is dead feasting on the dead Sun like a zombie; will there be anything left? Do we even care anymore or do we move onto Life-After-Oracle by choosing a new OS platform, a new programming language, a new filesystem etc etc etc?
14 July 2010
Slashdot: OpenSolaris Governing Board Closing Shop?
echolinux writes "Frustrated by Oracle's refusal to interact with the OpenSolaris community or speak with the OpenSolaris Governing Board, the OGB has issued an ultimatum to Oracle: designate a liaison to the OGB by August 16th or the board will 'take action at the August 23 meeting to trigger the clause in the OGB charter that will return control of the community to Oracle.'"
04 April 2010
Hudson reset on upgrade
I realized today that Hudson was about 15 versions out of date. I did the upgrade (pfexec pkg install hudson). On restart, Hudson now had a blank configuration. Don't worry - your data isn't gone. My manifest file had been modified and reimported; so now the various paths were incorrect for my system. Fixing and reimporting (pfexec svccfg import hudson.xml) was enough to get it working again.
24 March 2010
Package Renaming
I was looking at the "What's new for OpenSolaris 2010.03" and noticed the comment about "Renamed Packages"... Things like 'SUNWgtar' were renamed to 'archiver/gnu-tar'. So if you are having trouble finding your package; make sure to check out the list for the new name.
19 February 2010
cfgadm
So I woke up the other day and the server was making a LOT of noise. My first thought was that it was a fan going out [still think it is actually], so I tried 'fmadm faulty'. I was hoping to see something telling me which of the 8 fans were dying. Instead, I see that I was in the midst of a zpool failure.
Checking 'zpool status' I was able to verify that one of the disks had died. I'm running raid-z2, so it isn't like it was a hectic problem to solve... but I learned long ago it is better to fix it now than to wait until a couple more die.
Normally, you would have to go buy a replacement disk. Luckily for me, this Asus box never did recognize the last 3 drive bays. Counting across (there are 10 hot-swap SATAII drives -- want to make sure to pop the right one) I took a guess which one was failing and which ones were not currently in use. Luckily I was right.
Now, the "new" drive already had data on it because it used to be part of the root mirror before I upgraded them to larger drives. That being said, I was a little confused when the new drive wasn't being recognized.
I found this page which helped dramatically. 'cfgadm' showed that drive '6/0' was not configured. I ran 'cfgadm -c configure sata6/0'. It now showed up, but it said it was 'unavail' and 'corrupted data'. 'zpool online' didn't work because of those errors. Finally, I managed to get it to start working with 'zpool replace -f data c6t0d0'. It took quite awhile for it to finally finish. 'fmadm faulty' still showed the fault but I was able to fix that with the zpool clear that it recommended.
I'm thinking I should hook up one of my woot-off lights to flash whenever fmadm faulty shows a failure...
Checking 'zpool status' I was able to verify that one of the disks had died. I'm running raid-z2, so it isn't like it was a hectic problem to solve... but I learned long ago it is better to fix it now than to wait until a couple more die.
Normally, you would have to go buy a replacement disk. Luckily for me, this Asus box never did recognize the last 3 drive bays. Counting across (there are 10 hot-swap SATAII drives -- want to make sure to pop the right one) I took a guess which one was failing and which ones were not currently in use. Luckily I was right.
Now, the "new" drive already had data on it because it used to be part of the root mirror before I upgraded them to larger drives. That being said, I was a little confused when the new drive wasn't being recognized.
I found this page which helped dramatically. 'cfgadm' showed that drive '6/0' was not configured. I ran 'cfgadm -c configure sata6/0'. It now showed up, but it said it was 'unavail' and 'corrupted data'. 'zpool online' didn't work because of those errors. Finally, I managed to get it to start working with 'zpool replace -f data c6t0d0'. It took quite awhile for it to finally finish. 'fmadm faulty' still showed the fault but I was able to fix that with the zpool clear that it recommended.
I'm thinking I should hook up one of my woot-off lights to flash whenever fmadm faulty shows a failure...
Labels:
(Open)Solaris,
Hardware,
Troubleshooting,
UsefulCommands,
ZFS
04 January 2010
Zones getting out of sync
The other day, I started an update and walked away. I noticed today it was done, so I zfs snapshotted the zones and xvm sessions then rebooted.
Upon bootup, everything seemed OK until I tried to access the web pages on one of the zones. Checking svcs -xv, I saw that the local filesystem was down! That's not good!
While troubleshooting, it occurred to me that the global is reporting snv_130 and zlogin to a zone is reporting snv_101a. Oops. Just a little outdated.
I looked around for how to get them into sync, and ran across this article.
The solution is actually quite simple. It takes *forever* so I really wish I would have checked the time for you before I started. The basic jist of it is:
At first, I forgot the '-u' and it came back and told me it was out of sync and reminded me to try again with -u.
Oops, now what? At first I started looking online at things like Bug 13190... Then I realized I was missing the obvious...
Log File: /var/tmp/eoti.org.attach_log.voaWef
hmm, ok, so what does it say?
root@serveris:~# cat /var/tmp/eoti.org.attach_log.voaWef
This may seem odd to most of you... but I had the default opensolaris package repository AND the dev repository setup at one point; so it was getting confused. I followed the instructions (the pkg set-publisher and pkg unset-publisher) then retried the attach...
root@serveris:~# zoneadm -z eoti.org attach -u
Upon bootup, everything seemed OK until I tried to access the web pages on one of the zones. Checking svcs -xv, I saw that the local filesystem was down! That's not good!
While troubleshooting, it occurred to me that the global is reporting snv_130 and zlogin to a zone is reporting snv_101a. Oops. Just a little outdated.
I looked around for how to get them into sync, and ran across this article.
The solution is actually quite simple. It takes *forever* so I really wish I would have checked the time for you before I started. The basic jist of it is:
# pfexec zoneadm -z MYZONE halt
# pfexec zoneadm -z MYZONE detach
# pfexec zoneadm -z MYZONE attach -u
At first, I forgot the '-u' and it came back and told me it was out of sync and reminded me to try again with -u.
root@serveris:~# zoneadm -z eoti.org attach -u
Log File: /var/tmp/eoti.org.attach_log.voaWef
Attaching...
Global zone version: entire@0.5.11,5.11-0.130:20091219T044839Z
Non-Global zone version: entire@0.5.11,5.11-0.101:20081204T010954Z
Publisher Check: Zone preferred publisher does not contain
entire@0.5.11,5.11-0.130:20091219T044839Z.
Publisher Reset: Copying preferred publisher from global zone.
Updating non-global zone: (Stage 1). Output follows
Creating Plan
ERROR: Could not update attaching zone
Oops, now what? At first I started looking online at things like Bug 13190... Then I realized I was missing the obvious...
Log File: /var/tmp/eoti.org.attach_log.voaWef
hmm, ok, so what does it say?
root@serveris:~# cat /var/tmp/eoti.org.attach_log.voaWef
[Monday, January 4, 2010 8:08:03 PM PST] Log File: /var/tmp/eoti.org.attach_log.voaWef
[Monday, January 4, 2010 8:08:07 PM PST] Attaching...
[Monday, January 4, 2010 8:08:07 PM PST] existing
[Monday, January 4, 2010 8:08:07 PM PST]
[Monday, January 4, 2010 8:08:07 PM PST] Sanity Check: Passed. Looks like an OpenSolaris system.
Unable to retrieve package data for publisher 'os-dev' from one
of the following origin(s):
http://pkg.opensolaris.org/dev/
The catalog retrieved from one of the origin(s) listed above only
contains package data for: opensolaris.org.
To resolve this issue, correct the origin information provided for
publisher 'os-dev' using the pkg set-publisher subcommand, or re-add
the publisher using the correct name and remove the 'os-dev'
publisher.
To re-add this publisher with the correct name, execute the following
commands as a privileged user:
pkg set-publisher -P -g http://pkg.opensolaris.org/dev/ opensolaris.org
pkg unset-publisher os-dev
Unable to retrieve package data for publisher 'os-dev' from one
of the following origin(s):
http://pkg.opensolaris.org/dev/
The catalog retrieved from one of the origin(s) listed above only
contains package data for: opensolaris.org.
To resolve this issue, correct the origin information provided for
publisher 'os-dev' using the pkg set-publisher subcommand, or re-add
the publisher using the correct name and remove the 'os-dev'
publisher.
To re-add this publisher with the correct name, execute the following
commands as a privileged user:
pkg set-publisher -P -g http://pkg.opensolaris.org/dev/ opensolaris.org
pkg unset-publisher os-dev
pkg: The following pattern(s) did not match any packages in the current catalog.
Try relaxing the pattern, refreshing and/or examining the catalogs:
entire@0.5.11,5.11-0.130:20091219T044839Z
This may seem odd to most of you... but I had the default opensolaris package repository AND the dev repository setup at one point; so it was getting confused. I followed the instructions (the pkg set-publisher and pkg unset-publisher) then retried the attach...
root@serveris:~# zoneadm -z eoti.org attach -u
Log File: /var/tmp/eoti.org.attach_log.4kaGTgYay!
Attaching...
Global zone version: entire@0.5.11,5.11-0.130:20091219T044839Z
Non-Global zone version: entire@0.5.11,5.11-0.101:20081204T010954Z
Publisher Check: Zone preferred publisher does not contain
entire@0.5.11,5.11-0.130:20091219T044839Z.
Publisher Reset: Copying preferred publisher from global zone.
Updating non-global zone: (Stage 1). Output follows
DOWNLOAD PKGS FILES XFER (MB)
Completed 121/121 19959/19959 125.0/125.0
PHASE ACTIONS
Removal Phase 5811/5811
Install Phase 15876/15876
Update Phase 12076/12076
PHASE ITEMS
Indexing Packages 122/122
Updating non-global zone: (Stage 2). Output follows
No updates necessary for this image.
Updating non-global zone: Zone updated to entire@0.5.11,5.11-0.130:20091219T044839Z
Attach complete.
Labels:
(Open)Solaris,
Troubleshooting,
UsefulCommands,
ZFS,
Zones
23 October 2009
JForum on OpenSolaris
I decided to go ahead and setup a forum for one of the projects I am working on. I already had a zone setup that was hosting a "coming soon" page.
Looking around, I spent quite awhile trying to decide which forum software I was going to use. As a Java developer, I decided to go with a Java-based one so that it is easier for me to maintain. I ended up choosing JForum.
Installation was actually pretty easy. Getting the forums configured not so much (by default new forums were not visible until I went and reconfigured every user group -- each time I added a forum -- very annoying).
I had zlogin'd to the domain and:
Checking port 8080 on the domain I saw that tomcat was indeed running.
I downloaded jforum-2.1.8.war and placed it as: /var/tomcat6/webapps/jforum.war
Going to http://THEMACHINE:8080/jforum/install.jsp I specified to use HSQLDB, UTF-8, my URLs and a password.
Still a few things I'd like to fix, but as of now the forums are working.
Looking around, I spent quite awhile trying to decide which forum software I was going to use. As a Java developer, I decided to go with a Java-based one so that it is easier for me to maintain. I ended up choosing JForum.
Installation was actually pretty easy. Getting the forums configured not so much (by default new forums were not visible until I went and reconfigured every user group -- each time I added a forum -- very annoying).
I had zlogin'd to the domain and:
# pkg install SUNWtcat
# pkg install SUNWj6dvx
# svcadm enable tomcat6
# pkg install SUNWj6dvx
# svcadm enable tomcat6
Checking port 8080 on the domain I saw that tomcat was indeed running.
I downloaded jforum-2.1.8.war and placed it as: /var/tomcat6/webapps/jforum.war
Going to http://THEMACHINE:8080/jforum/install.jsp I specified to use HSQLDB, UTF-8, my URLs and a password.
Still a few things I'd like to fix, but as of now the forums are working.
22 October 2009
Gnome-terminal just disappears after upgrading to snv_125
After upgrading today, I was unable to launch the terminal. Let me correct that -- the window would come up, but before any text was displayed it would close. I didn't see any error messages or logs or anything that indicated what the problem was.
Then I found bug #6892167. To verify if that was my problem, I went up to "Applications | Run Application" and did 'gnome-terminal -e /bin/bash'. It launched fine.
Confirmed, I followed the instructions in the workaround to the best of my ability. The "old" copy of the libvte I had was 9.6.0, but it still appears to work. Also, I was unable to unmount the old boot environment without forcing (-f) it.
All seems to work now.
Then I found bug #6892167. To verify if that was my problem, I went up to "Applications | Run Application" and did 'gnome-terminal -e /bin/bash'. It launched fine.
Confirmed, I followed the instructions in the workaround to the best of my ability. The "old" copy of the libvte I had was 9.6.0, but it still appears to work. Also, I was unable to unmount the old boot environment without forcing (-f) it.
All seems to work now.
18 August 2009
Framework error: code: 28 reason: Operation timed out after 30000 milliseconds
When trying to install a package (in my case openjdk7-dev) you might run into this [on command line OR in the pkg ui]:
The solution to fix this was to simply set an environment variable:
Error:
Please check the network connection.
Is the repository accessible?
1: Framework error: code: 28 reason: Operation timed out after 30000 milliseconds with 18904080 out of 20853709 bytes received
URL: 'http://pkg.opensolaris.org/dev'.
2: Framework error: code: 28 reason: Operation timed out after 30000 milliseconds with 18999276 out of 20853709 bytes received
URL: 'http://pkg.opensolaris.org/dev'.
3: Framework error: code: 28 reason: Operation timed out after 30000 milliseconds with 19187200 out of 20853709 bytes received
URL: 'http://pkg.opensolaris.org/dev'.
4: Framework error: code: 28 reason: Operation timed out after 30000 milliseconds with 18991256 out of 20853709 bytes received
URL: 'http://pkg.opensolaris.org/dev'.
The solution to fix this was to simply set an environment variable:
export PKG_CLIENT_TIMEOUT=300
11 August 2009
FTPConnectionClosedException: Connection closed without indication
After installing the ftp server yesterday, I was trying to connect to it with the commons-net library. Unfortunately it kept failing:
As download worked from the browser, I thought this kinda odd. Looking a little closer, I decided to manually try the steps from the command line and see if I could figure out what was going on.
I ftp'd in and did the same commands I was doing from Java (passive, binary, etc).
When I tried to 'get' I saw:
Since I had found through my debugging that after the exception, the 150 FILE_STATUS_OK was the last reply I got; I looked up 421. It appears that there is a current bug on OpenSolaris that causes this behavior.
So here's the workaround (for the setup I did yesterday):
Everything works beautifully now :)
org.apache.commons.net.ftp.FTPConnectionClosedException: Connection closed without indication.
at org.apache.commons.net.ftp.FTP.__getReply(FTP.java:297)
at org.apache.commons.net.ftp.FTP.getReply(FTP.java:619)
at org.apache.commons.net.ftp.FTPClient.completePendingCommand(FTPClient.java:1244)
at org.apache.commons.net.ftp.FTPClient.retrieveFile(FTPClient.java:1301)
at org.apache.commons.net.ftp.FTP.__getReply(FTP.java:297)
at org.apache.commons.net.ftp.FTP.getReply(FTP.java:619)
at org.apache.commons.net.ftp.FTPClient.completePendingCommand(FTPClient.java:1244)
at org.apache.commons.net.ftp.FTPClient.retrieveFile(FTPClient.java:1301)
As download worked from the browser, I thought this kinda odd. Looking a little closer, I decided to manually try the steps from the command line and see if I could figure out what was going on.
I ftp'd in and did the same commands I was doing from Java (passive, binary, etc).
When I tried to 'get
150 Opening BINARY mode data connection for aopalliance-1.0.jar (6371 bytes).
421 Service not available, remote server has closed connection
ftp>
421 Service not available, remote server has closed connection
ftp>
Since I had found through my debugging that after the exception, the 150 FILE_STATUS_OK was the last reply I got; I looked up 421. It appears that there is a current bug on OpenSolaris that causes this behavior.
So here's the workaround (for the setup I did yesterday):
cp /lib/libsendfile.so.1 /home/ftp/lib
chown root:bin /home/ftp/lib/libsendfile.so.1
chown root:bin /home/ftp/lib/libsendfile.so.1
svcadm restart ftp
Everything works beautifully now :)
Labels:
(Open)Solaris,
Networking,
Troubleshooting,
Zones
Installing ftpd into a zone
from zone:
should work now
- pkg install SUNWftp
- svcadm enable ftp
- ftpconfig /home/ftp ((it will fail at the end))
- ftpconfig -d ((zonepath))
/root/home/ftp
should work now
07 July 2009
Hanging during boot
As a followup to the previous post (and this one before that)...
It still takes 4-5 hours to boot.... specifically, dmesg shows that this took 4 hours...
Jul 7 12:21:14 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 1
(system becomes usable here)
Jul 7 15:24:19 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 3
Any thoughts why a non-existant IDE device is polled for 4 hours during boot? Or why after finally booting, it is *still* doing it?
UPDATE: Bug submitted
It still takes 4-5 hours to boot.... specifically, dmesg shows that this took 4 hours...
Jul 7 08:15:32 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 0 irq 0xe vector 0x90 ioapic 0x4 intin 0xe is bound to cpu 2
(previous line [cdrom] was fine... rest are not)
Jul 7 08:15:32 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 3
Jul 7 08:15:32 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 0
Jul 7 08:15:40 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 3
Jul 7 08:15:57 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 0
Jul 7 08:15:57 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 1
Jul 7 08:15:57 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 2
Jul 7 08:15:57 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 3
(repeat and repeat and repeat)
Jul 7 12:21:13 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 0Jul 7 08:15:32 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 3
Jul 7 08:15:32 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 0
Jul 7 08:15:40 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 3
Jul 7 08:15:57 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 0
Jul 7 08:15:57 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 1
Jul 7 08:15:57 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 2
Jul 7 08:15:57 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 3
(repeat and repeat and repeat)
Jul 7 12:21:14 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 1
(system becomes usable here)
Jul 7 15:24:19 serveris xpv_psm: [ID 805372 kern.info] xVM_psm: ide (ata) instance 1 irq 0xf vector 0x98 ioapic 0x4 intin 0xf is bound to cpu 3
Any thoughts why a non-existant IDE device is polled for 4 hours during boot? Or why after finally booting, it is *still* doing it?
UPDATE: Bug submitted
Labels:
(Open)Solaris,
Hardware,
Troubleshooting,
Xen
27 June 2009
Update: Ardor3d and DarkMMO on OpenSolaris
As noted in the previous entry, I have Ardor3d working now in OpenSolaris (as of v 0.6-SNAPSHOT of Ardor3d).
I now have a mavenized-version of DarkMMO working as well (poms will be checked in soon).
Below is the startup script I am currently using to launch it.
I now have a mavenized-version of DarkMMO working as well (poms will be checked in soon).
Below is the startup script I am currently using to launch it.
#!/bin/bash
DS_PATH=`pwd`
DS_CP="$DS_PATH/DarkMMO-Client/target/DarkMMO-Client-1.0-SNAPSHOT.jar"
for file in $DS_PATH/DarkMMO-Client/target/dependency/*.jar; do
DS_CP="$DS_CP:$file"
done
export LD_LIBRARY_PATH=/export/home/malachi/work/Ardor3Dv1/ardor3d-lwjgl/lib/lwjgl/native/solaris
java -cp $DS_CP -Ddarkmmo.nwndatadir="$DS_PATH/nwn" com.worldwizards.darkmmo.client.DarkMMOClient
Labels:
(Open)Solaris,
Ardor3d,
Compiling,
DarkMMO,
Darkstar
24 June 2009
Maxine on OpenSolaris
Maxine is a VM designed for and written in the Java(TM) Programming Language with an emphasis on leveraging meta-circularity, componentized design, and code reuse to achieve flexibility, configurability, and productivity for academic and industrial virtual machine researchers.So I thought I'd give it a shot.
I extracted the zip file into into /opt. Originally permissions were as root:root (due to pfexec usage for opt) but I had to change it since maxine didn't like not having write access to the directory. I also created a symlink to /opt/maxine [which will be how I refer to it from now on].
I copied junit-4.4.jar into /opt/maxine/bin and added a line at the top of /opt/maxine/bin/max:
JUNIT4_CP=/opt/maxine/bin/junit-4.4.jarI modified my .zshrc to set /opt/maxine as MAXINE_HOME and added $MAXINE_HOME/bin to the beginning of my path.
Following these instructions, I took it for a little spin.
# max build
This actually failed (cc: language M1 not recognized) as long as gcc was in the PATH before the SunStudioExpress/bin; swapping those around it began working.
# max helloworld
Hello World# max vm -cp VM/bin test.output.GCTest2
Could not load main class: java.lang.ClassNotFoundException: test.output.GCTest2
KK, let's troubleshoot that...
# max -v helloworld
/opt/maxine/Native/generated/solaris/maxvm -classpath /opt/maxine/VM/bin util.HelloWorld
Hello World!
# max -v vm -cp VM/bin util.HelloWorld
/opt/maxine/Native/generated/solaris/maxvm -cp VM/bin util.HelloWorld
Could not load main class: java.lang.ClassNotFoundException: util.HelloWorld
# max -v vm -cp /opt/maxine/VM/bin util.HelloWorld
/opt/maxine/Native/generated/solaris/maxvm -cp /opt/maxine/VM/bin util.HelloWorld
Hello World!
Ok, I think I have it...
# max -v vm -cp /opt/maxine/VM/bin test.output.GCTest2
/opt/maxine/Native/generated/solaris/maxvm -cp /opt/maxine/VM/bin test.output.GCTest2
Garbage Collector Test
...
/opt/maxine/Native/generated/solaris/maxvm -cp /opt/maxine/VM/bin test.output.GCTest2
Garbage Collector Test
...
GCTest2 done.
I don't have 'max gate' working yet and 'max inspect' core dumped while trying to fork... but hey, it's a start.
Labels:
(Open)Solaris,
Compiling,
Maxine,
TheOtherMachine,
Troubleshooting
22 June 2009
Ardor3D on OpenSolaris
I noticed earlier today that Sun finally changed the licensing on Darkstar, as per my request. Before going and working on my design, I decided to see what the status of DarkMMO was. Jeff has picked it back up, and has started porting it to Ardor3d.
Ardor3d? I hadn't heard of that...
Apparently, Joshua Slack has moved the development from jMonkeyEngine to Ardor3d. The little bit of research I did seems to indicate that there is a bit of a rift with that -- but that Ardor3d is more current.
Ok, well, can I get Ardor3d working on OpenSolaris?
I go and check out their 'getting started' and was very disappointed to see references to Eclipse. Yes, I know many of you out there like Eclipse; but I am a purist and so have been against it since day 1. Besides, I really didn't like IBM's deceptive practices regarding its launch.
Oh well, let's see if this project is worth using after all. I download the source (subversion, yay!) and go to compile it (maven, yay!)... First failure is obvious... I needed to add a mirror to their nexus repository inside mine.
Try again...
Ok, well now the ardor3d-swt is failing. As much as I hate to, I decide to troubleshoot why it isn't building. As could be expected from a non-java library, the problem was caused by their repo not having the native libraries (yes, native - that's the main reason I despise SWT -- whoever heard of requiring native libraries for a java app intentionally?).
Ok, screw it. I commented out the ardor3d-swt module and then added an exclusion for **/*Swt*.java to the compiler in the top level pom. Ok, now everything else builds.
Now to run the example... hmmm... well that's annoying, I don't really want to have to find all the jars to test it... So I copied the dependency plugin configuration from ambrosia's pom into the top level pom and rebuilt.
Good. Now I have all the runtime dependencies for the examples in one place. I added all of them (why is the Java6 -classpath directory not working?) to the classpath, as well as the auto-generated ardor3d-examples-0.6-SNAPSHOT.jar.
Try again. Close.
export LD_LIBRARY_PATH=/export/home/malachi/work/Ardor3Dv1/ardor3d-lwjgl/lib/lwjgl/native/solaris:$LD_LIBRARY_PATH
Try again. Ok this time it runs. Can't use JOGL in the popup because there isn't a native library for it. Can't use 8 samples, because then it complains about GLX13 configuration. Can't use fullscreen -- well, that's a bit harsh. I *can* use fullscreen but it looks like crap because it changes to 320x240 and has severe artifacts. However, 4 samples, LWJGL, 1152x864 looks pretty good. Colors look a LOT better on 1024x768 though.
So not sure how much time I will spend on it. Definitely appears that it will be a bit of work to make it usable on OpenSolaris. Then again, maybe I should retry on Windows since my Emotiv Epoc won't run on anything else right now anyways.
BTW: To run the example after setting up the classpath and LD_LIBRARY_PATH...
java com.ardor3d.example.basic.BoxExample
Ardor3d? I hadn't heard of that...
Apparently, Joshua Slack has moved the development from jMonkeyEngine to Ardor3d. The little bit of research I did seems to indicate that there is a bit of a rift with that -- but that Ardor3d is more current.
Ok, well, can I get Ardor3d working on OpenSolaris?
I go and check out their 'getting started' and was very disappointed to see references to Eclipse. Yes, I know many of you out there like Eclipse; but I am a purist and so have been against it since day 1. Besides, I really didn't like IBM's deceptive practices regarding its launch.
Oh well, let's see if this project is worth using after all. I download the source (subversion, yay!) and go to compile it (maven, yay!)... First failure is obvious... I needed to add a mirror to their nexus repository inside mine.
Try again...
Ok, well now the ardor3d-swt is failing. As much as I hate to, I decide to troubleshoot why it isn't building. As could be expected from a non-java library, the problem was caused by their repo not having the native libraries (yes, native - that's the main reason I despise SWT -- whoever heard of requiring native libraries for a java app intentionally?).
Ok, screw it. I commented out the ardor3d-swt module and then added an exclusion for **/*Swt*.java to the compiler in the top level pom. Ok, now everything else builds.
Now to run the example... hmmm... well that's annoying, I don't really want to have to find all the jars to test it... So I copied the dependency plugin configuration from ambrosia's pom into the top level pom and rebuilt.
Good. Now I have all the runtime dependencies for the examples in one place. I added all of them (why is the Java6 -classpath directory not working?) to the classpath, as well as the auto-generated ardor3d-examples-0.6-SNAPSHOT.jar.
Try again. Close.
export LD_LIBRARY_PATH=/export/home/malachi/work/Ardor3Dv1/ardor3d-lwjgl/lib/lwjgl/native/solaris:$LD_LIBRARY_PATH
Try again. Ok this time it runs. Can't use JOGL in the popup because there isn't a native library for it. Can't use 8 samples, because then it complains about GLX13 configuration. Can't use fullscreen -- well, that's a bit harsh. I *can* use fullscreen but it looks like crap because it changes to 320x240 and has severe artifacts. However, 4 samples, LWJGL, 1152x864 looks pretty good. Colors look a LOT better on 1024x768 though.
So not sure how much time I will spend on it. Definitely appears that it will be a bit of work to make it usable on OpenSolaris. Then again, maybe I should retry on Windows since my Emotiv Epoc won't run on anything else right now anyways.
BTW: To run the example after setting up the classpath and LD_LIBRARY_PATH...
java com.ardor3d.example.basic.BoxExample
Labels:
(Open)Solaris,
Ardor3d,
Compiling,
Troubleshooting
10 June 2009
Firefox 3.5 and Java is not enabled
So I download the 3.5 Preview of Firefox (luckily the tarball rather than overwriting my working Firefox) and when I try to do just about anything:
The current version of Java on this system (0 - Java Not Enabled)So haven't figured out yet how to fix this. Edit|Preferences says that it is enabled. The other version of Firefox (3.1) can run at the same time and Java is working on it... Hope they iron that out soon. Especially since that little attempt completely wiped out all my personal data in the 3.1 version (bookmarks, passwords, history, everything -- which by the way, REALLY sucks).
03 June 2009
Installing JavaFX
download javafx_sdk-1_2-solaris-i586.sh
malachi@serveris[1]:/opt % pfexec chmod +x javafx_sdk-1_2-solaris-i586.sh
malachi@serveris[0]:/opt % pfexec ./javafx_sdk-1_2-solaris-i586.sh
malachi@serveris[0]:/opt % pfexec rm javafx_sdk-1_2-solaris-i586.sh
malachi@serveris[0]:/opt % pfexec ln -s javafx-sdk1.2 javafx
add /opt/javafx/bin to your PATH
per http://java.sun.com/javafx/1/tutorials/core/getStarted/
malachi@serveris[0]:~/work/javafx/Calculator/tmp % javafxc Calculator.fx
malachi@serveris[0]:~/work/javafx/Calculator/tmp % javafx Calculator
malachi@serveris[1]:/opt % pfexec chmod +x javafx_sdk-1_2-solaris-i586.sh
malachi@serveris[0]:/opt % pfexec ./javafx_sdk-1_2-solaris-i586.sh
malachi@serveris[0]:/opt % pfexec rm javafx_sdk-1_2-solaris-i586.sh
malachi@serveris[0]:/opt % pfexec ln -s javafx-sdk1.2 javafx
add /opt/javafx/bin to your PATH
per http://java.sun.com/javafx/1/tutorials/core/getStarted/
malachi@serveris[0]:~/work/javafx/Calculator/tmp % javafxc Calculator.fx
malachi@serveris[0]:~/work/javafx/Calculator/tmp % javafx Calculator
20 May 2009
OpenSolaris Bible: First Impressions
I got home from work last night and had my new OpenSolaris Bible [Amazon $32] sitting at my doorstep. Browsing through it, I was fairly impressed with the range of tidbits they covered. ZFS, iPKG, SMF, FMD, xVM, Zones, Java and C++ development, etc.
First thing I decided to play with was getting those remote CIFS shares mounted (they had been accessible via file explorer, but not via command-line). Unfortunately, it required I reboot the machine after enabling the smb/server... and well, for some unknown reason that currently takes 4 hours... so I didn't get to play with it much. I did however manage to get one of the shares to mount... Still trying to get the automount to work, but it's a start.
Taking the book to work today, I decided to play with FMD... Here's some comparison results between the work machine and the home machine... [Note: 'eris' is the work machine. 'serveris' is the home machine]
[eris:malachi(0)] ~% pfexec /usr/lib/fm/fmd/fmtopo
TIME UUID
May 20 09:40:20 23d4dce1-d973-c98a-ee18-ee2a16dd8ee8
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0/core=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0/core=0/strand=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0/core=1
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0/core=1/strand=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=0/pciexrc=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=0/pciexrc=0/pciexbus=1
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=0/pciexrc=0/pciexbus=1/pciexdev=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=0/pciexrc=0/pciexbus=1/pciexdev=0/pciexfn=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=1
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=1/pciexrc=1
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=2
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/chassis=0
malachi@serveris[0]:~ % pfexec /usr/lib/fm/fmd/fmtopo
TIME UUID
May 20 09:42:42 0524f912-299c-6280-d892-c36f53c00103
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/core=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/core=0/strand=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/core=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/core=1/strand=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/memory-controller=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/memory-controller=0/dram-channel=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/memory-controller=0/dram-channel=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/core=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/core=0/strand=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/core=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/core=1/strand=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/memory-controller=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/memory-controller=0/dram-channel=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/memory-controller=0/dram-channel=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0/pcibus=5
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0/pcibus=5/pcidev=11
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0/pcibus=5/pcidev=11/pcifn=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0/pcibus=5/pcidev=32
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0/pcibus=5/pcidev=32/pcifn=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=1/pciexrc=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=2
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=2/pciexrc=2
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=3
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=3/pciexrc=3
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=3/pciexrc=3/pciexbus=2
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=3/pciexrc=3/pciexbus=2/pciexdev=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=3/pciexrc=3/pciexbus=2/pciexdev=0/pciexfn=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=4
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=4/pciexrc=4
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=4/pciexrc=4/pciexbus=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=4/pciexrc=4/pciexbus=1/pciexdev=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=4/pciexrc=4/pciexbus=1/pciexdev=0/pciexfn=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=5
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=5/pciexrc=5
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=6
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=6/pciexrc=6
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/chassis=0
first cpu:
[eris:malachi(0)] ~% pfexec /usr/lib/fm/fmd/fmtopo -P all hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0
TIME UUID
May 20 09:44:10 2d75b8fe-0c11-4e89-d8a5-ed2569e7b58e
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0
group: protocol version: 1 stability: Private/Private
resource fmri hc://:product-id=OptiPlex-755:chassis-id=72VY...
group: authority version: 1 stability: Private/Private
product-id string OptiPlex-755
chassis-id string 72VYGH1
server-id string eris
group: chip-properties version: 1 stability: Private/Private
vendor_id string GenuineIntel
family int32 6
model int32 23
stepping int32 6
malachi@serveris[0]:~ % pfexec /usr/lib/fm/fmd/fmtopo -P all hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0
TIME UUID
May 20 09:45:56 a0c248a0-75ae-65c3-e8b3-be99702ad460
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0
group: protocol version: 1 stability: Private/Private
resource fmri hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-...
group: authority version: 1 stability: Private/Private
product-id string L1N64-SLI-WS
chassis-id string SYS-1234567890
server-id string serveris
group: chip-properties version: 1 stability: Private/Private
vendor_id string AuthenticAMD
family int32 15
model int32 193
stepping int32 3
NodeId uint32 0x0
CoherentNodes uint32 0x2
SbNode uint32 0x0
LkNode uint32 0x0
SystemCoreCount uint32 0x4
C0Unit uint32 0x0
C1Unit uint32 0x1
McUnit uint32 0x2
HbUnit uint32 0x3
SbLink uint32 0x1
BroadcastRoutes uint32[] [ 9 1 ]
ResponseRoutes uint32[] [ 1 8 ]
RequestRoutes uint32[] [ 1 8 ]
shorthand for the CPU names....
[eris:malachi(0)] ~% pfexec /usr/lib/fm/fmd/fmtopo -s cpu
TIME UUID
May 20 09:45:57 08533a3a-65de-e73d-e8f1-e89fba223ed0
cpu:///cpuid=0
cpu:///cpuid=1
malachi@serveris[0]:~ % pfexec /usr/lib/fm/fmd/fmtopo -s cpu
TIME UUID
May 20 09:47:22 d2a17d23-222d-412d-c691-cf1273371317
cpu:///cpuid=0
cpu:///cpuid=1
cpu:///cpuid=2
cpu:///cpuid=3
Now, what else can I play with?
First thing I decided to play with was getting those remote CIFS shares mounted (they had been accessible via file explorer, but not via command-line). Unfortunately, it required I reboot the machine after enabling the smb/server... and well, for some unknown reason that currently takes 4 hours... so I didn't get to play with it much. I did however manage to get one of the shares to mount... Still trying to get the automount to work, but it's a start.
Taking the book to work today, I decided to play with FMD... Here's some comparison results between the work machine and the home machine... [Note: 'eris' is the work machine. 'serveris' is the home machine]
[eris:malachi(0)] ~% pfexec /usr/lib/fm/fmd/fmtopo
TIME UUID
May 20 09:40:20 23d4dce1-d973-c98a-ee18-ee2a16dd8ee8
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0/core=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0/core=0/strand=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0/core=1
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0/core=1/strand=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=0/pciexrc=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=0/pciexrc=0/pciexbus=1
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=0/pciexrc=0/pciexbus=1/pciexdev=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=0/pciexrc=0/pciexbus=1/pciexdev=0/pciexfn=0
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=1
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=1/pciexrc=1
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/hostbridge=2
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/chassis=0
malachi@serveris[0]:~ % pfexec /usr/lib/fm/fmd/fmtopo
TIME UUID
May 20 09:42:42 0524f912-299c-6280-d892-c36f53c00103
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/core=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/core=0/strand=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/core=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/core=1/strand=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/memory-controller=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/memory-controller=0/dram-channel=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0/memory-controller=0/dram-channel=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/core=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/core=0/strand=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/core=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/core=1/strand=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/memory-controller=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/memory-controller=0/dram-channel=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=1/memory-controller=0/dram-channel=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0/pcibus=5
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0/pcibus=5/pcidev=11
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0/pcibus=5/pcidev=11/pcifn=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0/pcibus=5/pcidev=32
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=0/pcibus=5/pcidev=32/pcifn=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=1/pciexrc=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=2
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=2/pciexrc=2
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=3
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=3/pciexrc=3
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=3/pciexrc=3/pciexbus=2
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=3/pciexrc=3/pciexbus=2/pciexdev=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=3/pciexrc=3/pciexbus=2/pciexdev=0/pciexfn=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=4
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=4/pciexrc=4
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=4/pciexrc=4/pciexbus=1
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=4/pciexrc=4/pciexbus=1/pciexdev=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=4/pciexrc=4/pciexbus=1/pciexdev=0/pciexfn=0
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=5
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=5/pciexrc=5
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=6
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/hostbridge=6/pciexrc=6
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/chassis=0
first cpu:
[eris:malachi(0)] ~% pfexec /usr/lib/fm/fmd/fmtopo -P all hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0
TIME UUID
May 20 09:44:10 2d75b8fe-0c11-4e89-d8a5-ed2569e7b58e
hc://:product-id=OptiPlex-755:chassis-id=72VYGH1:server-id=eris/motherboard=0/chip=0
group: protocol version: 1 stability: Private/Private
resource fmri hc://:product-id=OptiPlex-755:chassis-id=72VY...
group: authority version: 1 stability: Private/Private
product-id string OptiPlex-755
chassis-id string 72VYGH1
server-id string eris
group: chip-properties version: 1 stability: Private/Private
vendor_id string GenuineIntel
family int32 6
model int32 23
stepping int32 6
malachi@serveris[0]:~ % pfexec /usr/lib/fm/fmd/fmtopo -P all hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0
TIME UUID
May 20 09:45:56 a0c248a0-75ae-65c3-e8b3-be99702ad460
hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-1234567890:server-id=serveris/motherboard=0/chip=0
group: protocol version: 1 stability: Private/Private
resource fmri hc://:product-id=L1N64-SLI-WS:chassis-id=SYS-...
group: authority version: 1 stability: Private/Private
product-id string L1N64-SLI-WS
chassis-id string SYS-1234567890
server-id string serveris
group: chip-properties version: 1 stability: Private/Private
vendor_id string AuthenticAMD
family int32 15
model int32 193
stepping int32 3
NodeId uint32 0x0
CoherentNodes uint32 0x2
SbNode uint32 0x0
LkNode uint32 0x0
SystemCoreCount uint32 0x4
C0Unit uint32 0x0
C1Unit uint32 0x1
McUnit uint32 0x2
HbUnit uint32 0x3
SbLink uint32 0x1
BroadcastRoutes uint32[] [ 9 1 ]
ResponseRoutes uint32[] [ 1 8 ]
RequestRoutes uint32[] [ 1 8 ]
shorthand for the CPU names....
[eris:malachi(0)] ~% pfexec /usr/lib/fm/fmd/fmtopo -s cpu
TIME UUID
May 20 09:45:57 08533a3a-65de-e73d-e8f1-e89fba223ed0
cpu:///cpuid=0
cpu:///cpuid=1
malachi@serveris[0]:~ % pfexec /usr/lib/fm/fmd/fmtopo -s cpu
TIME UUID
May 20 09:47:22 d2a17d23-222d-412d-c691-cf1273371317
cpu:///cpuid=0
cpu:///cpuid=1
cpu:///cpuid=2
cpu:///cpuid=3
Now, what else can I play with?
Subscribe to:
Posts (Atom)
