Most clusters run the vendor Unix. IBMs runs AIX or Linux, SGIs run IRIX or Linux, Alphas run Tru64, x86 clusters run Linux. The ultra-high-end custom machines run obscure custom Unix ports. Microsoft is trying to break into the HPC market, but so far only Cornell and Rice are buying.
The Extremely Expensive Edition CPUs aren't targeted at PHBs -- they're targeted at gamers. The PHBs are still buying 915 chipsets like Intel told them.
Remember folks, KDE is not a whole OS, it's just a frontend. Apples and oranges, and all that.
With an attitude like that, I think KDE is doomed (compared to vertically integrated OSes like OS X, Windows, and JDS). The user just wants to install SUSE (for example) and have it work; users don't care that Linux and KDE are separate fiefdoms.
Apple has the privilege of only having one VFS layer. There is no such single layer that KDE could rely upon, since it runs on quite a few distinct operating systems.
In my mind there are two ways to look at it. You've presented one way: KDE must have this feature, and if the OSes won't provide it, then KDE must provide it in some suboptimal way.
The alternate approach is to say that mounting a fish or whatever is a feature that belongs in the OS, and if a particular OS supports it, then KDE will get that for free. If an OS doesn't support it, then KDE won't have that feature when running on that OS.
Apple is doing this stuff (e.g. you can mount WebDAV servers), but Apple is doing it right by integrating network resources into the real VFS layer so that all applications can access them. KDE's I/O slaves are not real filesystems and are not accessible by all applications.
Tarantula isn't a separate core since it doesn't have a separate program counter. It's more like a coprocessor or a big frickin' extra functional unit.
It's probably the 802nd group created within IEEE. "The IEEE 802 LAN/MAN Standards Committee develops Local Area Network standards and Metropolitan Area Network standards."
802.11 Wireless LAN Working Group 802.12 Demand Priority Working Group 802.14 Cable Modem Working Group 802.15 Wireless Personal Area Network (WPAN) Working Group 802.16 Broadband Wireless Access Working Group 802.17 Resilient Packet Ring Working Group 802.18 Radio Regulatory TAG 802.19 Coexistence TAG 802.20 Mobile Broadband Wireless Access (MBWA) Working Group 802.21 Media Independent Handoff Working Group
Modern radio links use FEC to eliminate bit errors or convert them to packet loss. That way TCP never sees corrupted packets and doesn't have to worry about them.
Slashdot Mirror
That won't help at all, since the **AA can just ask the tracker for the IPs of all the peers.
"Oh yeah? Then we'll double bankrupt him!"
Most clusters run the vendor Unix. IBMs runs AIX or Linux, SGIs run IRIX or Linux, Alphas run Tru64, x86 clusters run Linux. The ultra-high-end custom machines run obscure custom Unix ports. Microsoft is trying to break into the HPC market, but so far only Cornell and Rice are buying.
No, last week NASA bought 10240 Itanium processors.
Of course it's actually a Quantum drive, but Quantum is now owned by Maxtor.
Extreme Edition is Gallatin, not Prescott. So the most expensive Pentium 4 isn't even 64-bit.
The Extremely Expensive Edition CPUs aren't targeted at PHBs -- they're targeted at gamers. The PHBs are still buying 915 chipsets like Intel told them.
Remember folks, KDE is not a whole OS, it's just a frontend. Apples and oranges, and all that.
With an attitude like that, I think KDE is doomed (compared to vertically integrated OSes like OS X, Windows, and JDS). The user just wants to install SUSE (for example) and have it work; users don't care that Linux and KDE are separate fiefdoms.
Apple has the privilege of only having one VFS layer. There is no such single layer that KDE could rely upon, since it runs on quite a few distinct operating systems.
In my mind there are two ways to look at it. You've presented one way: KDE must have this feature, and if the OSes won't provide it, then KDE must provide it in some suboptimal way.
The alternate approach is to say that mounting a fish or whatever is a feature that belongs in the OS, and if a particular OS supports it, then KDE will get that for free. If an OS doesn't support it, then KDE won't have that feature when running on that OS.
Apple is doing this stuff (e.g. you can mount WebDAV servers), but Apple is doing it right by integrating network resources into the real VFS layer so that all applications can access them. KDE's I/O slaves are not real filesystems and are not accessible by all applications.
Exactly. Every guarantee has an equal and opposite refusal. In this case they have only 40 lambdas, so they can only support 40 users at a time.
Ethernet PONs have symmetric bandwidth -- 1 Gbps down, 1 Gbps up. Only the slower, more expensive BPON/GPON stuff is asymmetric.
PONs are encrypted, just like cable.
Download it here.
Why restrict downloads to just one?
Apple pays for that bandwidth.
Neither the XT3 nor BlueGene/L have shared memory. The XT3 supports Cray's "SHMEM" API, but that's not really shared memory as we know it.
What architectures use 64-bit instruction words? Not PowerPC, MIPS, or SPARC. Certainly not x86-64.
Tarantula isn't a separate core since it doesn't have a separate program counter. It's more like a coprocessor or a big frickin' extra functional unit.
You're the exception. At $2.50 per DVD player, digital cable box, or digital satellite box, some companies are paying MPEG-LA a lot of money.
WMV9 isn't "completely closed" any more; MS submitted the bitstream specification to SMPTE.
However, since both WMV9 and AVC (h.264) are included into specs, does that mean that each hardware DVD player will have to have both decoders?
Yes. They also have to include MPEG-2.
And would each movie have to be encoded in either of the two?
Yes.
It's probably the 802nd group created within IEEE. "The IEEE 802 LAN/MAN Standards Committee develops Local Area Network standards and Metropolitan Area Network standards."
They didn't skip any numbers (except for the unlucky 802.13).
802.11 Wireless LAN Working Group
802.12 Demand Priority Working Group
802.14 Cable Modem Working Group
802.15 Wireless Personal Area Network (WPAN) Working Group
802.16 Broadband Wireless Access Working Group
802.17 Resilient Packet Ring Working Group
802.18 Radio Regulatory TAG
802.19 Coexistence TAG
802.20 Mobile Broadband Wireless Access (MBWA) Working Group
802.21 Media Independent Handoff Working Group
The bandwidth is shared; 268Mbps for 1,000 customers sounds about right.
Modern radio links use FEC to eliminate bit errors or convert them to packet loss. That way TCP never sees corrupted packets and doesn't have to worry about them.