BSD & Gaming

The April Issue Articles Include:

• Interview with Dru Lavigne

• Why You Use FreeBSD Just May Start With A ‘Z’

• OpenBSD improves upon /etc/rc.d/

• DragonFly News

• Package Management for the upcoming PC-BSD 9

• Converting a Physical Partition with FreeBSD to a vmware Image

• Build appliances with QEMU and OpenBSD

• Drupal on FreeBSD part 5

• Mutt On OS X part 2

• Realtime Weather Data EMWIN on FreeBSD

• Benchmarking Different Kind of Storage

• Content Management Made Easy The Open Source Way!

Get it fresh off the press by going to BSDMag.Org for your free copy now.

.

.

I tried, I really tried with Firefox 3 to learn to like the “Awesome Bar“. To begin with, the name bugged me, “awesome bar”… really?

Ok be good, that voice in my head told me in that sickening patronizing tone that is so prevalent in today’s politically correct culture.  The voice continued to badger me with guilt saying – just give it a try and stay open minded.

Grumbles…. fine fine whatever.

I’m a card carrying member of the “If it ain’t broke, don’t goddam fix it!” and the “Keep It Simple…ya Stupid idiot!” groups. SO, needless to say every time I hear about how someone somewhere gets what they think is a bright idea, usually in my world….it ain’t.

Well here I am many many, months later and my final conclusion? It sucks the big one. It almost never gives me anything related to what I want. Instead of saving me time it wastes it by feeding me useless crap to look at.  I end up typing the URL by hand if I know it or hitting up a search engine to find it.

Fine… it’s faster that way anyhow… so how do I get rid of it? Ahhhh the ever helpful about:config

Search for browser.urlbar.maxRichResults and change the value to “-1“, you can change it to “0” which most sites suggest, but I find it creates a slight flicker at the bottom of the URL entry field. By using a value of “-1” that flicker does not appear for me.

The newest Firefox 3.6 makes a big change in how new tabs are loaded. The old way opens a new tab to the far right. The new way opens a tab immediately to the right, this bugs the hell out of me.

If you like or want to know more about the way version 3.6 handles tabbed browsing and the changes to come, then take a look at this page – [LINK]

For those dinosaurs like myself who prefer the old way it’s a simple enough fix.

Go to about:config and filter for browser.tabs.insertRelatedAfterCurrent, then change the value to “FALSE”.

All done, PHEW! now I can go back to surfing the way I like it.