Canonical to Replace Google with Yahoo! in Firefox

"Ubuntu creator and distributor Canonical has inked a deal with Yahoo! to make the latter the default search provider in upcoming versions of the operating system."

Search News

Ubuntu developer and distributor Canonical has inked a deal with Yahoo! to make the latter the default search provider in upcoming versions of the operating system. This means Yahoo! will replace Google as the default search engine in the customized version of Firefox built into the company’s Ubuntu operating system. Canonical will earn a share of the advertising revenue generated by Yahoo! from this deal.

Firefox creator Mozilla Foundation already has a similar agreement with Google. The agreement gives the Foundation a part of the advertising revenue generated in return for making Google the default search engine on its internet browser. This revenue makes up a lion’s share of the total income for the Mozilla Foundation.

With Canonical signing its own deal with Yahoo! for the same browser, the Foundation will be faced with a revenue loss, as a part of the income would get diverted to Canonical. Clarifying the intentions behind their decision, Canonical’s Rick Spencer said that the revenue from this deal would “help Canonical provide developers and resources to continue the open development of Ubuntu and the Ubuntu Platform”.

While the switching of the search engines has been confirmed, Canonical has made allowances for Mozilla to continue receiving revenues. The customized Firefox will still have a choice of search engines including the same version of Google that is built into Firefox currently. With users free to select the one they want to set as their default search engine, the income for Mozilla from this channel is not likely to dry up completely.

With Google’s continued dominance of the search engine domain and most users hesitant about changing their default search provider, Canonical’s move could bear mixed results. The deal is also a strange one because Yahoo! has already signed a pact with Microsoft to sell off its business to the software giant. Now everyone in the tech world knows that Microsoft and Linux do not see eye-to-eye. So the agreement could possibly turn out to be something of a tug-of-war. Plus, it is still pending regulatory approval.

The number of users that actually stick to the new Yahoo! search in Ubuntu’s Firefox and the revenues earned by Canonical are things that only time will reveal.

«Prev 1 Next»

Most Recent Comments

18-01-2010, 05:02:01

siravarice
Oh yes very much so, just the standard voltages for ram, and the what was the perfect voltage for the overclock. I have no idea how to find out what build revision it is though lol

18-01-2010, 06:23:39

86sixsix
For the version information - run "slmgr -dlv" from an admin command prompt... 6.1.xxxx.xxxxx

I had a look through the 7 knowledge base and couldn't find a single mention of a hard lock that was down to the OS...

As I've said...if it was right at 3.2 for ages and then gone mad all of a sudden (and you haven't changed a single piece of hardware or changed anything in the BIOS) then it's down to either:

a) A background process (Run a 24hour stress test in safe-mode)
b) A new driver, either a poorly coded one or one that's made a device change its resources (Have a look at your APIC tables and see what's going on regarding IRQs and whatnot) - try removing all unnessary devices as I've said earlier
c) A couple of tracks or mosfets on your board or other bit of hardware getting a bit old and tired

Let me know your build and I'll try to replicate the problem... I've got a system that's close to yours... But with Corsair RAM...

18-01-2010, 10:29:02

biscuitboy
I seem to have a Black screen problem in 7 64bit too..... Hmmm, Stable and stress tested, still randomly if left Idle the screen goes black and Will not resume or anything....

I'm not so sure they have resolved the issue tbh.

18-01-2010, 11:54:52

86sixsix
All this points to flaky display drivers causing soft ram errors... Uninstall the 'time zone' security update... Install the latest 'windows defender' definitions... Then disable the defender service (don't just turn it off)... Disable realtime AV/malware/spyware/whatever... Disable anything remotely power-management related... Enhanced halt states, speedsteps, CoolnQuiet, Screensavers, turning off the display, adaptive suspend, Set windows to 100min and 100max as far as CPU goes in powermanagement... Don't let windows enter 'away mode'... Uninstall your display drivers, switch to the "Standard VGA" driver as provided on the windows dvd...don't let windows update pick a newer version... and stress test in safe mode.

At least that'd differentiate between a software / hardware hiccup...

Perhaps S1 and S3 states are coming into play at silly times? I must level with you... windows isn't my thing... but these are the 1st thing's i'd try.

Do the op and biscuitboy get the problems in safe mode? And what build of 7 is everyone on? I run 7600.16385 but really can't handle it's crappy performance scaling...

The op didn't mention a black screen so I doubt these issues are related...

A good test for biscuitboy's blackscreen-ness would be to do my suggestions as per my last post - then switch off, cold boot and let it sit at the login screen without even touching the keyboard... see if you've gotten the Winlogon shell registry key problem... maybe, maybe not...

...another testing step...not likely but still...

Run in safe mode, create a new Admin-rights user, cold boot...and test again in safe mode. Perhaps something's mangled in your user profiles? don't trust ccleaner and the like... they seem to be a bit over-zealous in what they delete...

18-01-2010, 12:35:07

siravarice
Just realised that all you need to do is open up command prompt and it says what build revision it is at the top line. It's build 6.1.7600. Although the full build number is 6.1.7600.16385

18-01-2010, 13:37:57

86sixsix
Indeed it does...but it's the build (end bit) that's important...

Have either of you done any testing with the Standard VGA driver in safe mode?

I trust everyone's done the basic stuff, restoring every clock you've got to stock, tapping num-lock to be sure it really has locked, making sure windows is up to date, re-ran directx setup, chkdsk'd everything, unplugged everything they don't need, not let ccleaner and whatnot remove everything it found, disabled all the twaddle services (indexing, defender, firewall (unless it's the only one you've got lol), media sharing and what have you), turned off any realtime rootkit and av stuff, tried when logged on as a *new* user, made sure nothing freaky's coming back from secedit or sfc, got rid of all device sharing, closed all their local user's processes...
I shouldn't ask about all that rubbish...I'm new here and don't want to upset anyone but again someone says 'my machine is stable but it locks up now and again' - surely it's one or the other lol...but sometimes it's easy to overlook the basic stuff...I do dumb stuff all the time lol

It's just the only time I've seen hard locks in windows machines were due to soft ram errors, cr*p code in display drivers, or having keys missing or with the wrong permissions in the registry...

I'd love you help everyone but without seeing eventlogs and minidumps or whatever windows calls them these days I'm just guessing...

18-01-2010, 13:46:58

86sixsix
That's about all I can think of windows wise...

...i trust people've got all the cke strengths, clock drives/dram drives and terminations set properly?

18-01-2010, 14:12:07

siravarice
Not to that extent, but it's not something I'm worried about really. It's running faster and smoother now that it ever has. I updated my drivers for my graphics card (they were quite out of date) and everything is up to date. I perform regular scans and what not, run CCleaner, do disk checks and so on. I'm pretty sure it's not the motherboard, it has always been very good to me and my case has always been pretty cool. Voltages are what they need to be and not over the top, I lowered them as much as possible before the overclock was unstable, then raised them a bit until i felt everything was working great. Planning some upgrades soon anyway so if the whole thing does go kaput, I will just bring the upgrade forward!

18-01-2010, 17:00:23

86sixsix
^Those are just some of the basics...

You've done the right thing by trying some new display drivers (195.81 is the most stable for me as far as my nvidia bits go)... As an example of something you may have fixed, version 182.50 didn't drop the grfx cards out out of 'performance 3d' mode and as a result they used to pull more amps than they needed and eventually took a teensy tiny bit out of my 3.3v rails on the boards...

Just don't always trust ccleaner - unless you *really* know what all the classid's and controls you're frying actually do... In which case - you need to teach me your kung-fu...

Most of the stuff I'm into is (what's the term?) 'more low-level' than windows lets you get into... but I hope I've thrown some at least quite useful hints people's way...

OFFTOPIC: And if you ever go on a mission with your 260... be sure to let me know the results... The most I get stably out of mine at stock.v is 700/1490/1275... ...I'm sure there's more to get out of the ram on these things...

Best of luck...

19-01-2010, 04:16:35

siravarice
Hmm, I could probably give it a go. My 260 does still run very cool considering the huge overclock.
Reply
x

Register for the OC3D Newsletter

Subscribing to the OC3D newsletter will keep you up-to-date on the latest technology reviews, competitions and goings-on at Overclock3D. We won't share your email address with ANYONE, and we will only email you with updates on site news, reviews, and competitions and you can unsubscribe easily at any time.

Simply enter your name and email address into the box below and be sure to click on the links in the confirmation emails that will arrive in your e-mail shortly after to complete the registration.

If you run into any problems, just drop us a message on the forums.