[mythtv-users] Problem upgrading from 0.25fixes to 0.26

[Jay Ashworth]

----- Original Message -----
> From: "Michael T. Dean" <mtdean at thirdcontact.com>

> GNU/Linux doesn't /have/ to be rebooted for most changes--as long as
> you're willing to spend the time figuring out what's wrong, then
> learning how to fix it--but sometimes 30s to reboot is the easiest way
> to fix things.

> "Microsoft's greatest trick was convincing the world to reboot first."
> 
> (And, FWIW, Android is running a Linux kernel and I have to reboot my
> Android phone all the time--often every day, but at least once every
> other day--and my provider actually has messages pop up if you don't
> reboot your phone once per week.)
> 
> Mike (who believes that uptime is meaningless, except when trying to
> figure out if your server went down when it wasn't supposed to)

And a quick side note to Mike's excellent observation here (Mike's 
observations are, of course, always excellent; that wasn't my point):

As a professional systems administrator, I can tell you this: the last
thing you schedule as part of the maintenance window when you make
changes to an OS is "reboot the machine, and make sure that it comes
back up in one piece *while you remember what you just changed*".

Granted, if your change control documentation is good enough, the
delay shouldn't matter, but it's still better to know that you haven't
broken the boot *while you're working on a changeset*.

This is why functional separation is a good architectural design, BTW.

Even if they're VMs.

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA               #natog                      +1 727 647 1274