What about this one?
http://arstechnica.com/information-technology/2013/03/epic-uptime-achievement-can-you-beat-16-years/
- Opprinnelig melding -
Hi, all!
I saw this on the Illumos developer list. I thought some of you might
get a kick out of it.
A Sun Solaris machine was shut
On 9 April 2013 15:06, Roy Sigurd Karlsbakk r...@karlsbakk.net wrote:
What about this one?
http://arstechnica.com/information-technology/2013/03/epic-uptime-achievement-can-you-beat-16-years/
we had a box that I installed in 1999 that was turned off when we moved
out of the building in 2010
On 2013-04-09 16:26, Jonathan Adams wrote:
we found it hiding behind a fitted cupboard
that had been installed after it
Well, there was a trend in 90's Russia to mount storage boxes into
a wall, bricked forever, preferably with a wireless network. Whenever
there were masked shows (tax police
Edward Ned Harvey (openindiana) wrote:
Patching is extremely safe. But let's look at the flip side. Suppose you
encounter the rare situation where patching *does* cause a problem. It's been
known to happen; heck, it's been known to happen *by* *me*. You have to ask
yourself, which is the
On 4/8/2013 4:16 AM, Ian Collins wrote:
Edward Ned Harvey (openindiana) wrote:
Patching is extremely safe. But let's look at the flip side.
Suppose you encounter the rare situation where patching *does* cause
a problem. It's been known to happen; heck, it's been known to
happen *by* *me*.
On Mon, Apr 8, 2013 at 1:16 AM, Ian Collins i...@ianshome.com wrote:
Hands up all those who've bricked a Linux system or had a Solaris 10
system that wouldn't play with live upgrade.
I've had a couple instances where Linux systems wouldn't boot after kernel
updates. Generally these have been
On Mon, Apr 8, 2013 at 12:02 PM, David Brodbeck bro...@uw.edu wrote:
On Mon, Apr 8, 2013 at 1:16 AM, Ian Collins i...@ianshome.com wrote:
Hands up all those who've bricked a Linux system or had a Solaris 10
system that wouldn't play with live upgrade.
I've had a couple instances where
On 2013-04-08 21:04, David Brodbeck wrote:
Oh yeah -- another reason is I've run into many situations where
OpenSolaris/OpenIndiana requires a full power cycle to reboot -- at least
one of my machines hangs if I try to do a soft reboot in OI.
Did you test if reboot -p (via PROM == via BIOS on
Also, given the boot environments and live upgrade methods of OI and
other Solaris derivatives, applying a patch is NOT dangerous.
Apply, reboot into new environment (overnite??), and if things seem to
have problems, go back to the old environment.
The only caution that seems reasonable is to
Edward Ned Harvey (openindiana) wrote:
From: Ben Taylor [mailto:bentaylor.sol...@gmail.com]
Patching is a bit of arcane art. Some environments don't have
test/acceptance/pre-prod with similar hardware and configurations, so
minimizing impact is understandable, which means patching only what is
Andrew Gabriel said the following, on 07-04-13 10:34 AM:
Edward Ned Harvey (openindiana) wrote:
From: Ben Taylor [mailto:bentaylor.sol...@gmail.com]
Patching is a bit of arcane art. Some environments don't have
test/acceptance/pre-prod with similar hardware and configurations, so
minimizing
On 2013-04-07 16:34, Andrew Gabriel wrote:
OTOH, I have worked in environments where everything is going to be
locked down for 6-10 years. You get as current and stable as you can for
the final testing, and then that's it - absolutely nothing is allowed to
change. As someone else already hinted
Patching is a bit of arcane art. Some environments don't have
test/acceptance/pre-prod with similar hardware and configurations, so
minimizing impact is understandable, which means patching only what is
necessary.
I prefer to patch everything when I build, or in environments where I have
On Wed, Mar 20, 2013 at 4:32 AM, Edward Ned Harvey (openindiana)
openindi...@nedharvey.com wrote:
It would only bring a tear to my eye, because of how foolishly
irresponsible that is. 3737 days of uptime means 10 years of never
applying security patches and bugfixes. Whenever people are
I was watching this discussion thread with interest so I checked
system uptimes. My AMD64 Solaris 10 system was just about to reach
exactly one year of uptime. When it reached one year of uptime, then
BOOM, system panic for unknown (to me) reason. I recall that the same
thing happened to my
Edward Ned Harvey (openindiana) said the following, on 20-03-13 7:32 AM:
From: dormitionsk...@hotmail.com [mailto:dormitionsk...@hotmail.com]
Sent: Tuesday, March 19, 2013 11:42 PM
A Sun Solaris machine was shut down last week in Hungary, I think, after 3737
days of uptime. Below are links to
From: dormitionsk...@hotmail.com [mailto:dormitionsk...@hotmail.com]
Sent: Tuesday, March 19, 2013 11:42 PM
A Sun Solaris machine was shut down last week in Hungary, I think, after 3737
days of uptime. Below are links to the article and video.
Warning: It might bring a tear to your
On 03/20/2013 12:32 PM, Edward Ned Harvey (openindiana) wrote:
It would only bring a tear to my eye, because of how foolishly
irresponsible that is. 3737 days of uptime means 10 years of
never applying security patches and bugfixes. Whenever people
are proud of a really long uptime, it's a
long uptimes are not hard to achieve. i bet if i got my old sparc ipx out from
college days and booted it the system would report about thirteen years if
uptime. i think i last used it in the summer of 2000.
i shut it down last time by putting it to sleep. when it boots, assuming
battery is
I had to reboot after about 200 days of uptime the other day because I
updated netatalk, which created a new BE. I don't really understand why a
non-kernel package, for a non-essential service, would need a new BE.
Is there a way to avoid this kind of thing so in the future I can brag
about
I worked for QNX back in the early 2000's. At that time QNX had a fairly
complete design for performing kernel upgrades on a live system. Because
QNX is a microkernel, this was doable. I can't get too deep into the
details, but essentially it required a set of permanently reserved memory
pages
I'm waiting for 7337 days before mine go down ;)
On 20 March 2013 14:41, dormitionsk...@hotmail.com
dormitionsk...@hotmail.com wrote:
Hi, all!
I saw this on the Illumos developer list. I thought some of you might get
a kick out of it.
A Sun Solaris machine was shut down last week in
22 matches
Mail list logo
