fozbaca.org

From the register:

“Performance is let down, however, by the system bus speed which is limited to 66MHz. Desktop Macs and the PowerBook G4 have a bus speed of 100MHz, and the performance difference is evident in tests. Although fast, the iBook is slower than a similarly rated iMac, and the PowerBook G4 easily outperforms it ? but then as it costs �1000 more you would expect it to. Nevertheless, the iBook is fast enough for most tasks and applications you care to throw at it. Our only other complaint with regard to system specification is the amount of supplied RAM. Of the four iBook models available one ships with only 64MB, while the other three are stocked with 128MB. Given that Mac OS X – Apple’s next-generation operating system – which is to be preinstalled on all new Macs, needs a minimum of 128MB to run, this is very poor. ”

Amen brothers! Let us pour on the RAM! It is cheap, and cometh from the heavens to speedeth our computing needs!

OK, sports fans. I have long been an advocate of thin-client solutions. Furthermore, i think that Apple has a really good opportunity to help themselves out. Think of this: a NIC like thin client, with an LCD and the usual hookups, tied intoa MacOSX server, netbooting, and with NFS mounts over either gigabit ethernet or wireless (all of which Apple has demonstrated). Kinda like the stuff
Sun is doing, but with MacOS and Mac::Office. No company wants to switch over completely to Sun, but what about Apple? hmm…..

This could be the era of thin clients. Of NFS and netboot. Low TCO and logging in from anywhere.

I am a big advocate of this technology in the educational market and workplace. Think about it: why does a sales guy or a kindergarterner need their own computer just to do simple stuff? It is time to consolidate our computing power and use it wisely.

OK, sports fans. I have long been an advocate of thin-client solutions. Furthermore, i think that Apple has a really good opportunity to help themselves out. Think of this: a NIC like thin client, with an LCD and the usual hookups, tied intoa MacOSX server, netbooting, and with NFS mounts over either gigabit ethernet or wireless (all of which Apple has demonstrated). Kinda like the stuff
Sun is doing, but with MacOS and Mac::Office. No company wants to switch over completely to Sun, but what about Apple? hmm…..

This could be the era of thin clients. Of NFS and netboot. Low TCO and logging in from anywhere.

I am a big advocate of this technology in the educational market and workplace. Think about it: why does a sales guy or a kindergarterner need their own computer just to do simple stuff? It is time to consolidate our computing power and use it wisely.

MS Office 2004 screenshot.
[via ScriptingNews]

MS Office 2004 screenshot.
[via ScriptingNews]

Disabling Smart Tags under Apache 1.2 and later

From Red Hat Apache Guru Mark Cox, via Drew Meeks at Red Hat:

Adding

Header add MSSmartTagsPreventParsing "TRUE"

to httpd.conf should add the response header to every page served.

Mark and Drew haven’t tested this, but I pass it along. You can test the efficacy of this approach at http://209.204.184.53/, which returns both

MSSmartTagsPreventParsing: TRUE
X-Meta-MSSmartTagsPreventParsing: TRUE

as response headers, the latter since X-Meta-Foo in the response headers is interpreted by some browsers as equivalent to a <META name=”Foo”> tag. http://209.204.184.50/ returns the same content without the above headers.

Requires that mod_headers is installed on your copy of Apache: See http://httpd.apache.org/docs/mod/mod_headers.html. You can alter the scope of this by placing the “Header” directive inside a VirtualHost, Directory, Location, or Files directive.

I grabbed the whole thing incase the refered site disapears in the future.

Disabling Smart Tags under Apache 1.2 and later

From Red Hat Apache Guru Mark Cox, via Drew Meeks at Red Hat:

Adding

Header add MSSmartTagsPreventParsing "TRUE"

to httpd.conf should add the response header to every page served.

Mark and Drew haven’t tested this, but I pass it along. You can test the efficacy of this approach at http://209.204.184.53/, which returns both

MSSmartTagsPreventParsing: TRUE
X-Meta-MSSmartTagsPreventParsing: TRUE

as response headers, the latter since X-Meta-Foo in the response headers is interpreted by some browsers as equivalent to a <META name=”Foo”> tag. http://209.204.184.50/ returns the same content without the above headers.

Requires that mod_headers is installed on your copy of Apache: See http://httpd.apache.org/docs/mod/mod_headers.html. You can alter the scope of this by placing the “Header” directive inside a VirtualHost, Directory, Location, or Files directive.

I grabbed the whole thing incase the refered site disapears in the future.

Finally got stats working on fozbaca, since the move to the ufies box (thanks tiggersol), and the number 1 search string “interesting stuff”. Some more intresting ones “cummunism” and “she wet her”, don’t ask me why.

Finally got stats working on fozbaca, since the move to the ufies box (thanks tiggersol), and the number 1 search string “interesting stuff”. Some more intresting ones “cummunism” and “she wet her”, don’t ask me why.

More Overheated Porn Hysteria
this time in the Canadian Navy.

Commodore Eric Lerhe, the chief of the Canadian Pacific fleet, has been suspended from duty and faces a possible court-martial. For high treason? No, for looking at porn on the web.

Now what do ya’ll native Canadians have to comment?

A man does not sexually harass women because he reads pornography. A man sexually harasses women because he’s an asshole.

is probably the best rebuttle to the whole “porn makes men evil to women” angle.