Current versions of Linux have several different waysto schedule IO activity; one writeup of this is here .The developers of the iSCSI target software that we use have for some time recommended that peopleswitch away from CFQ (the default one) to either the 'deadline' or the'noop' scheduler to get better performance. Recently I got around totesting this to see if it made a difference in our environment, and itturns out that it does.

(Whether the difference is significant is an open question.

It's long since past the time when anti-spam content scanning systemsshould decode and scan all the encoded attachments of email messages,especially encoded plaintext ones. Most content scanning systems alwaysbeen willing to decode base-64 encoded inline text and HTML (it's sortof a basic requirement), but I don't think very many of them scanattachments. The predictable result is that spammers have caught onthat attaching their spam in a base-64 encoded attachment works, and itshouldn

One corollary of the danger of over-powerful introspection is that you should not use HTTP requestparameters directly as filenames for any reason, not just to avoidhard-coding allowed commands in your web application. Any time that youuse a request parameter as a filename, you create an opportunity for anattacker to escape from whatever directory your application is supposedto get its files from and thus to rummage all over your system.

(In fact, you should not directly use the URL for a filename either,because someday