Anonymous Coward.

A Linux box with a NOPASSWD 'sudo' setup would skip all of this and go right from "executes malware" to "infects system."

Your trolling: 10/10. Bravo.

/slow clap

Gordon Gekko approves.

[Parent modded "Funny" for lack of a "Sad" mod]

For mounting ISO's under WinXP, this has worked for me. It's small and simple and doesn't have any extra crap:

http://download.microsoft.com/download/7/b/6/7b6abd84-7841-4978-96f5-bd58df02efa2/winxpvirtualcdcontrolpanel_21.exe

You're addicted to internetahol?

From one of the pages the summary links to (https://cm1rr.cmich.edu/remediation/CSAstart.html):

This is the kind of quality OT comment I love slashdot for.

Not sarcasm, either. It brings to mind my example of being a member of the last generation to use a physical card catalog.

It's like they have some crazy scheme to turn a profit by selling software.

The Search Dog was one thing that whenever I installed XP and had to sit through it before being able to turn it off had me asking myself "and this is 'enterprise' software?" Why have a cartoon built into your operating system?

You're right about implementation with respect to my "human-readable" comment - in practice it wouldn't be much different if there were a standard and ls could tell me the file type as well (kind of an integration of file and ls... which wouldn't be hard to hack together just to see what it would look like, but I digress).

But I still think there are situations in which there is no way to get that info - e.g. a list of links on a page, each to a file of a different type. If it says http://example.com/file.doc, you know what to expect. Metadata sufficient to render file extensions obsolete would leave us with http://example.com/file, with no way to tell what it contains.

There may be a quick fix to this situation that I'm overlooking, but my point remains - there are some times when it's just good to know from the filename what you'll be dealing with.

Because the human using the computer wants a quick way to determine what the file most likely contains.

Primary and secondary are both on the same utility circuit, that unfortunately experiences frequent outages. So in function it is more like a secondary DNS, but strictly speaking is tertiary.

Just wanted to get something on a completely different IP block and, most importantly, utility circuit.

...and also, why not?

OT, but I have a 16-year-old P1 doing firewall, dhcp, and tertiary DNS. The thing rocks.