I agree, I've done both. By far the worst however are the systems where the user insists on dual booting.

Real Disadvantages: You risk data loss with any application that stores critical data using either (1) a truncate/write method or (2) a write/rename method without a asking the OS to sync it's data. I think that far fewer than 95% of applications fall under (2) and every filesystem will have issues with (1).

For (1) there is nothing the OS can do for the application, just about any file system would loose data in this case depending on how long it caches the writes in memory and if the application has a chance to finish writing all of the data. (1) is clearly bad application code at fault. Ext4 does increase the write-delay for the data but any way you use (1) is asking for problems if the system crashes/the disk fills up/etc.

For (2) the file system could implement atomic rename operations but that would be at a slight performance loss when the application didn't need this atomic operation. This is more of a do-what-I-mean-not-what-I-say workaround as I don't see too many situations where (2) would be used without expecting atomic operation. If the application didn't care about possible data loss in the file (1) works well. The real fix however is to call sync() in the application code in this situation, it makes the code more portable across posix filesystems.

If reliability was the only concern they would likely use ATM.
Speed is a major concern due to SAR bottlenecks. Also, ATM networks are expensive, difficult to implement, and inefficient at bulk data transfers.

There was a patch (not by S3) for the XFree86 driver that disabled VESA mode probing. It would make S3 chipsets "work" with VESA drivers if you got your mode lines just right in the config file. Even then there were some other bugs, you had to start the kernel in framebuffer mode and you could not go back to a console once X was started.

The stated reason from S3 for not supporting VESA probing was that it was used in the past to obtain firmware from the chipset and that Windows (9x) did not probe for VESA modes (even when using VESA drivers).

I like to think that linux support from manufactures has come a long way since then but it looks like some still don't care.

The flaw with this is that he would still be legally allowed to keep his own transcript of the performance, just not make copies. Oh, and live performances can not technically be copyrighted in the US (but you still need permission from the artist to distribute to avoid the anti-bootlegging provisions). Copyright only exists (in the US) for something placed on tangible media.

Quite frankly, yes. AFIAK most waste in the US is sold to Areva for reprocessing into usable material. Most uranium mines have been non-operational for several years due to the low price of uranium on the market, this might change in the near future however. In the US the NEC is quite strict on tracking where waste is shipped.

Full disclosure: I work in Richland, WA where Hanford is located. I do not work at Hanford myself but I know people who do.

I sent a wire 3 week ago using firefox (on windows).

On a related note, I still have not received my 100 thousand US dollars for facilitating getting the prime minister of finance in Nigeria's scheme to get money out of his country. (j/k)