I've been considering the upgrade from Snow Leopard to Lion, but will probably wait just a little while longer. I have a (Sept 2010) MacBook Pro, it has been an excellent machine - I also have a 21" iMac and a standard MacBook all of which perform.
The issue that I have is that on the MacBook Pro I run Virtual Box and Solaris 11 among others, as does one of the guys that I work with. He has recently come across an interesting feature - which we have not been able to resolve so far.
Once he upgraded to Lion and when running the Solaris Virtual Machine, if he left the Macbook and it went into hibernate the following happened.
1 The MacBook got very hot.
2 If the power cube was plugged in it became too hot to touch.
3 When you eventually got onto the Virtual machine typing was near impossible due to repeating keys.
4 When you could have a look around - the 15 min Load Average on the Solaris Virtual M/C could be well up into the 2000's.
I'm guessing that this is actually a Virtual Box problem, just high lighted by Lion. We are going to go to Mountain Lion on his machine, to see if that resolves the problem.
I have been in touch with Oracle as the latest version of VBox was used as was a downloaded virtual machine from them. I'll keep people posted if there are any changes.
I do like the look of Mountain Lion, really getting towards what Sun's Project Looking Glass was all about - just you don't need an enterprise class server to run it!
I am thinking to purchase a new MacBook Air, 13 inch.
Anyone have a MacBook Air? What do you think about it? Seems expensive, a bit. Is it worth it? (9 Replies)
Jifty::Upgrade(3pm) User Contributed Perl Documentation Jifty::Upgrade(3pm)NAME
Jifty::Upgrade - Superclass for schema/data upgrades to Jifty applications
SYNOPSIS
package MyApp::Upgrade;
use base qw/ Jifty::Upgrade /;
use Jifty::Upgrade qw/ since rename /;
since '0.7.4' => sub {
# Rename a column
rename table => 'cthulus', name => 'description',
to => 'mind_numbingly_horrible_word_picture';
};
since '0.6.1' => sub {
my @sizes = ('Huge', 'Gigantic', 'Monstrous', 'Really Big');
my @appearances = ('Horrible', 'Disgusting', 'Frightening', 'Evil');
# populate new columns with some random stuff
my $cthulus = MyApp::Model::CthuluCollection->new;
while (my $cthulu = $cthulus->next) {
$cthulu->set_size($sizes[ int(rand(@sizes)) ]);
$cthulu->set_appearance($appearances[ int(rand(@appearances)) ]);
}
};
DESCRIPTION
"Jifty::Upgrade" is an abstract base class to use to customize schema and data upgrades that happen.
since VERSION SUB
"since" is meant to be called by subclasses of "Jifty::Upgrade". Calling it signifies that SUB should be run when upgrading to version
VERSION, after tables and columns are added, but before tables and columns are removed. If multiple subroutines are given for the same
version, they are run in order that they were set up.
versions
Returns the list of versions that have been registered; this is called by the Jifty::Script::Schema tool to determine what to do while
upgrading.
upgrade_to VERSION
Runs the subroutine that has been registered for the given version; if no subroutine was registered, returns a no-op subroutine.
rename table => CLASS, [column => COLUMN,] to => NAME
Used in upgrade subroutines, this executes the necessary SQL to rename the table, or column in the table, to a new name.
SEE ALSO
Jifty::Manual::Upgrading
perl v5.14.2 2010-12-08 Jifty::Upgrade(3pm)
