VirtualBox 3.0 and Macs and stuff…


I read today that VirtualBox 3.0 has been released. In the past this wouldn’t have been a big thing for me because I mostly use VMware Server on my Linux box, but now I’m a MacBook owner it has more interest. I refuse to pay money for the crippled VMware Fusion on Mac, so VirtualBox is the obvious solution.

The Mac is starting to get under my skin. I’m currently writing this post on my Linux box and struggling. Why? I’m getting used to the Mac keyboard and the keys are in the “wrong” place on this keyboard. Also, having to change from cmd+c/cmd+v to ctrl+c/ctrl+v for copy/paste is hard work. I just stare at the keyboard for a second to try and figure it out. Funny how quickly a lifetime of automatically doing something can change in 2 weeks. 🙂

So it looks like my next PC will actually be a Mac, then at home I will be consistent. Oh no! It’s happening. I’m becoming an Apple fanboy. Aaarrrggghhh!!! 🙂

I’m still of the opinion that, looks aside, OS X is not better than Windows/Linux, it’s just different. It’s a nice kinda different, but not streets ahead as people would lead you to believe.

Anyway, enough musings of a Mac newbie… 🙂



Author: Tim...

DBA, Developer, Author, Trainer.

6 thoughts on “VirtualBox 3.0 and Macs and stuff…”

  1. VirtualBox on Windows 2003 can mess up Oracle 10g performance seriously. The funny thing is that it’s only PL/SQL (not SQL) execution that went up 100x on some of our packages.

    Sadly, we got rid of VirtualBox

  2. I still can’t get used to switching meaning of ctrl-c between winblows and unix/vms/rsts.

    But worse is my vi habit of hitting escape a lot, that just messes up in many browser windows.

  3. Hi Tim,
    may i ask you an oracle question?

    how can i limit a size of uploaded image im my clob field with out coding in application?
    you already said in trigger but unfortunately ‘:new.lob’ type is not accessible in before insert trigger.

    thank you.

  4. Hi.

    I don’t think you can without coding it in your application.

    Makes sense to do it there also. No point wasting network bandwidth transferring an item you can;t use.



  5. hi Tim,
    a simple example on my problem is:
    1- create table test(pic blob);
    2- create trigger:
    create or replace trigger test_ai
    after insert
    on test
    for each row
    raise_application_error(-20000,’len=’ || dbms_lob.getlength(:new.pic));

    now i insert a record in test table, always return 0.
    actually i want to limit a user to upload more than 64K in to my table.

    would you please help me to solve my problem.

Comments are closed.