Tuesday, December 21, 2010
Friday, December 17, 2010
Monday, November 01, 2010
Friday, October 22, 2010
Heretic, author unknown.
I was walking across a bridge one day, and I saw a man standing on the edge, about to jump off. So I ran over and said,
"Stop! Don't do it!".
"Why shouldn't I?" he said.
I said, "Well, there's so much to live for!"
He said, "Like what?"
I said, "Well, are you religious or atheist?"
He said, "religious."
I said, "Me too! Are your Christian or Buddhist?"
He said, "Christian."
I said, "Me too! Are you Catholic or Protestant?"
He said, "Protestant."
I said, "Me too! Are your Episcopalian or Baptist?"
He said, "Baptist!"
I said, "Wow! Me too! Are your Baptist church of God or Baptist church of the Lord?"
He said, "Baptist church of God!"
I said, "Me too! Are you original Baptist church of God or are you reformed Baptist church of God?"
He said, "Reformed Baptist church of God!"
I said, "Me too! Are you reformed Baptist church of God, reformation of 1879, or reformed Baptist church of God, reformation of 1915?"
He said, "Reformed Baptist church of God, reformation of 1915!"
I said, "Die, Heretic scum!" and pushed him off.
"Stop! Don't do it!".
"Why shouldn't I?" he said.
I said, "Well, there's so much to live for!"
He said, "Like what?"
I said, "Well, are you religious or atheist?"
He said, "religious."
I said, "Me too! Are your Christian or Buddhist?"
He said, "Christian."
I said, "Me too! Are you Catholic or Protestant?"
He said, "Protestant."
I said, "Me too! Are your Episcopalian or Baptist?"
He said, "Baptist!"
I said, "Wow! Me too! Are your Baptist church of God or Baptist church of the Lord?"
He said, "Baptist church of God!"
I said, "Me too! Are you original Baptist church of God or are you reformed Baptist church of God?"
He said, "Reformed Baptist church of God!"
I said, "Me too! Are you reformed Baptist church of God, reformation of 1879, or reformed Baptist church of God, reformation of 1915?"
He said, "Reformed Baptist church of God, reformation of 1915!"
I said, "Die, Heretic scum!" and pushed him off.
Thursday, October 21, 2010
Monday, September 20, 2010
Thursday, August 19, 2010
Tuesday, July 06, 2010
Monday, June 28, 2010
Friday, May 14, 2010
Tuesday, April 20, 2010
Friday, April 02, 2010
YouTube - Phil Hare doesn't care.MP4
YouTube - Phil Hare doesn't care.MP4
Congressional Representative Phil Hare (IL - D) says he "doesn't worry about the Constitution" and fails to answer any of the questions his constituents posed to him.
Congressional Representative Phil Hare (IL - D) says he "doesn't worry about the Constitution" and fails to answer any of the questions his constituents posed to him.
Sunday, March 28, 2010
Using the bootadm Command to Manage the Boot Archives (System Administration Guide: Basic Administration) - Sun Microsystems
Do not attempt these instructions by yourself without first opening a case with Sun. Every problem is different, and just because these commands worked for me, does NOT mean they will work for your problem. You could make things worse by not seeking help from Sun. Don't make me tell you I told you so!
Sunday night I attempted to reboot one of my servers, and got output similar to the following (the names have been changed):
SunOS Release 5.10 Version Generic_141414-07 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Unexpected EOF on line 14 of /kernel/drv/md.conf
Hostname: xyzzy
WARNING: The following files in / differ from the boot archive:
changed /kernel/drv/did.conf
The recommended action is to reboot to the failsafe archive to correct
the above inconsistency. To accomplish this, on a GRUB-based platform,
reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe". Then
follow the prompts to update the boot archive. Alternately, to continue
booting at your own risk, you may clear the service by running:
"svcadm clear system/boot-archive"
Sep 18 15:22:06 svc.startd[7]: svc:/system/boot-archive:default:
Method "/lib/svc/method/boot-archive" failed with exit status 95.
Sep 18 15:22:06 svc.startd[7]: system/boot-archive:default
failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):
With help from Sun, and documentation similar to "Using the bootadm Command to Manage the Boot Archives (System Administration Guide: Basic Administration) - Sun Microsystems", I was able to get my system back up and running.
Thank you Sun!
Sunday night I attempted to reboot one of my servers, and got output similar to the following (the names have been changed):
SunOS Release 5.10 Version Generic_141414-07 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Unexpected EOF on line 14 of /kernel/drv/md.conf
Hostname: xyzzy
WARNING: The following files in / differ from the boot archive:
changed /kernel/drv/did.conf
The recommended action is to reboot to the failsafe archive to correct
the above inconsistency. To accomplish this, on a GRUB-based platform,
reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe". Then
follow the prompts to update the boot archive. Alternately, to continue
booting at your own risk, you may clear the service by running:
"svcadm clear system/boot-archive"
Sep 18 15:22:06 svc.startd[7]: svc:/system/boot-archive:default:
Method "/lib/svc/method/boot-archive" failed with exit status 95.
Sep 18 15:22:06 svc.startd[7]: system/boot-archive:default
failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):
With help from Sun, and documentation similar to "Using the bootadm Command to Manage the Boot Archives (System Administration Guide: Basic Administration) - Sun Microsystems", I was able to get my system back up and running.
Thank you Sun!
Wednesday, March 24, 2010
Monday, March 22, 2010
Friday, March 12, 2010
Wednesday, March 03, 2010
#271519: Solaris 10 Kernel Patches 141444-09 and 141445-09 May Cause Interface Failure in IP Multipathing (IPMP)
#271519: Solaris 10 Kernel Patches 141444-09 and 141445-09 May Cause Interface Failure in IP Multipathing (IPMP)
Category : Availability
Release Phase : Resolved
Bug Id : 6888928
Product : Solaris 10 Operating System
Date of Workaround Release : 03-Nov-2009
Date of Resolved Release : 10-Dec-2009
Solaris 10 Kernel Patches 141444-09 and 141445-09 cause interface failure in IP Multipathing:
1. Impact
The IP Multipathing (IPMP) facility allows systems with multiple network interfaces in the same subnet to failover in the event that one of the interfaces fails, and then failback when the interface is ok.
Solaris 10 Kernel Patches 141444-09 (SPARC) and 141445-09 (x86) cause interface failure in IPMP when configured for probe based failure detection. This issue does not occur with a IPMP link based failure detection configuration.
2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform:
* Solaris 10 with patch 141444-09 and without patch 142900-02
x86 Platform:
* Solaris 10 with patch 141445-09 and without patch 142901-02
Note 1: Solaris 8 and 9 and OpenSolaris are not impacted by this issue.
Note 2: This issue only occurs on systems with IPMP configured for probe based failure detection. This issue does not occur with a IPMP link based failure detection configuration.
Category : Availability
Release Phase : Resolved
Bug Id : 6888928
Product : Solaris 10 Operating System
Date of Workaround Release : 03-Nov-2009
Date of Resolved Release : 10-Dec-2009
Solaris 10 Kernel Patches 141444-09 and 141445-09 cause interface failure in IP Multipathing:
1. Impact
The IP Multipathing (IPMP) facility allows systems with multiple network interfaces in the same subnet to failover in the event that one of the interfaces fails, and then failback when the interface is ok.
Solaris 10 Kernel Patches 141444-09 (SPARC) and 141445-09 (x86) cause interface failure in IPMP when configured for probe based failure detection. This issue does not occur with a IPMP link based failure detection configuration.
2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform:
* Solaris 10 with patch 141444-09 and without patch 142900-02
x86 Platform:
* Solaris 10 with patch 141445-09 and without patch 142901-02
Note 1: Solaris 8 and 9 and OpenSolaris are not impacted by this issue.
Note 2: This issue only occurs on systems with IPMP configured for probe based failure detection. This issue does not occur with a IPMP link based failure detection configuration.
Friday, February 26, 2010
Bug ID: 6898395 when applying latest KU 141444-09 clusters hangs on reboot as it exhausts autopush structures.
From http://bugs.opensolaris.org
Bug ID: 6898395 when applying latest KU 141444-09 clusters hangs on reboot as it exhausts autopush structures.
Bug ID: 6898395 when applying latest KU 141444-09 clusters hangs on reboot as it exhausts autopush structures.
Bug ID 6898395
Synopsis when applying latest KU 141444-09 clusters hangs on reboot as it exhausts autopush structures.
State 6-Fix Understood (Fix is known)
Category:Subcategory suncluster:networking
Keywords BOP | rtiq_regression | sc32u3-dmt
Responsible Engineer Thomas Atkins
Reported Against
Duplicate Of
Introduced In
Commit to Fix
Fixed In
Release Fixed
Related Bugs 6879232
Submit Date 5-November-2009
Last Update Date 11-December-2009
Description
please see evaluation in 6879232, essentially after adding 141444-09 to my cluster nodes, reboot hangs, as my cluster nodes has exhausted the default number of autopush structures.
When the clhbsndr module is loaded, it causes a lot more autopushes to occur than would otherwise happen on a non-clustered system.
So cluster needs to update /etc/system with
set nautopush=64
this has also been seen by one external customer so far, University of Queensland.
Enda
Work Around
edit /etc/system and add the line:
set nautopush=64
Thursday, February 18, 2010
Wednesday, February 17, 2010
Friday, February 12, 2010
Subscribe to:
Posts (Atom)