RTFFAQ: They're not claiming, that they have IP rights of all those protocols and make that pretty clear:
However, just because a protocol appears on the list does not mean that Microsoft is the owner or sole owner of rights in that protocol or its documentation.
The trick here is that MS makes people buy something even though they don't know what they are buying (if anything at all).
I don't know where the 500M transistors mentioned in the submission come from. I don't find it in both linked articles. I doubt the 64MBit chip (~67E6 bit, marketing makes that 70) uses that much transistors. I think the 64MBit chip is just a demonstration/benchmark for the new process since it's pretty easy to scale a memory chip design to a smaller gate size due to its simplicity.
It's worse: It's not just the borders, even if they weren't rendered by the application and done by an window manager you wouldn't been able to move, resize etc. the window if the application hangs:
Until the application acknowledges the clip change, the old window shape has to be considered as being continuously damaged by the application.
With X11 in case you can't kill an process for whatever reasons (hung in disk-wait-state e.g. if the application accesses files on an NFS server that went down) you still can close it's windows. (Or iconify them or move them to another window... )
With this concept presented here a wild running application can ruin the whole X^Hwhatever-its-name-will-be session: All screenspace occupied by the application's windows will become unusable, i.e. you can't even move an other window over it.
Should win acadamy awards for - crappiest special effects - most unrealistic and most predictable storyline - worst acting - biggest ignorance to history in history
So you should be able to sync your local sources with a public repository at any time you want and don't havve to download huge tar files or fiddle with patches.
>... can compete in REAL (eg NOT burst mode for 512 bytes) I/O speed...
What makes you think "burst mode for 512 bytes" is not real?. Harddisc sectors are nowadays 512 bytes large and their contents are transferred in bursts. SCSI doesn't even have commands to transfer single bytes out/or into a sector (or "block" in SCSI terms), so I/O always has to be transferred in bursts of 512 bytes (or more).
> BTW, what's the count on Russian space failures? I know they've had their accidents, but I can't think > of when and where. It's not like we've got a spotless record anyhow.../insomnia
In manned space the losses of astronauts/cosmonauts in a per launch or per flight hour ratio are much better for the soviet/russian space agency (Soyuz 1 (1) and Soyuz 11 (3)) than the for NASA (14 in two shuttle accidents).
However the Soviets had two incindents with rockets exploding on launch pad while fueling them and that caused nearly 200 peoples lifes.
> I believe Arianespace will be using Russian launchers at some point. Arianespace IS already operating Soyus launches from Baikonur in some way, see here: http://www.arianespace.com/site/launcher/soyuz_sub _index.html
> However, it's hard to imagine the EU wanting a manned space program (or indeed any big showy > projects with very dubious returns) what with all the new accession countries joining next > month. Arianespace is not ESA and ESA is not EU. I.e. not every EU member is also ESA member.
It should be noted that there are plenty of joint ventures between US and Russian/Ukrainian companies as well. E.g. the Atlas V launchers are using russian RD180 engines and Sea Launch is (Or was? No launch for 2 years) using Ukrainian Zenith launch vehicles.
It's even mentioned in the article the editor cites. *sigh*
The culture of Teotihuacan predates the Aztecs by a few hundred years. It climaxed around 500, went under around 600 (my sources say 700). The so-called Aztecs arived around 1200 and gave the site its name, but that's the only Aztec connection to Teotihuacan.
No, I just said that that it's not the GPL that blocks XFree4.4 from getting into OpenBSD since OpenBSD is NOT RELEASED UNDER THE GPL.
The philosophy behind OpenBSD is based on Theo, the decisons what licences are acceptable for OpenBSD are based on its philosophy so in the end they have to be Theo compatible.
Who cares about GPL-compatibility? It has to be Theo-compatible to be part of OpenBSD.
Re:Mac68K build-from-scratch in emulation?
on
NetBSD 1.6.2 Released
·
· Score: 3, Interesting
> I'm sure this is a problem on a lot of the 40 architectures, some of them are way old and limited > to the sub-100MHz range Nowadays the release binaries for most platforms except i386 are crosscompiled.
> Cross-compiling seems like a hairy mess. Not with NetBSD (well, most platforms. There may be a few, which are not using the build.sh system).
Since the NetBSD build process bootstraps by building first a set of tools (make, binutils, compilers etc) and then uses this set to build the system.All you need is a bourne-shell compatible shell and a C/C++ compiler.That's why you can use a - say - solaris/sparc system to compile NetBSD/pmax.See the file BUILDING in the top directory of the source tree.
Military jets of the cold war aera are usally less critical than commercial jets. Think of quickly erected forward air bases and supply conditions in times of war (BTW: In Germany many straight parts of the autobahn were designed to be able to be converted to auxilary air bases quickly).
As an example, the Mig31 'Foxbat', capable of speeds exceeding Mach 2.83 is said to be able to start from unpaved runways. The F/A18 is designed to start and land on carriers, which means slow start and landing speeds and that means short starts and landings.
Slashdot Mirror
> But in Germany, you can be arrested for having historical artifacts from WWI that contain
> swastikas.
First: The NSDAP wasn't even founded in WWI.
Second: No, you can't.
Haha, this is funny. The bright glowing lightsaber is throwing a shadow on the wall ;)
Yes, whatever rights it may have.
Let's hope someone has constructed the 001 influence device till then.
Who cares? The US DOD? Haha
Well, they examined launching V2s from submarines but what I really meant was "SRBM", sorry.
A launcher based on an American ICBM (which was derived from a German SLBM) and equipped with Russian engines launches french satellites...
s es /rec197/
http://www.ilslaunch.com/newsarchives/newsrelea
I don't know where the 500M transistors mentioned in the submission come from. I don't find it in both linked articles. I doubt the 64MBit chip (~67E6 bit, marketing makes that 70) uses that much transistors. I think the 64MBit chip is just a demonstration/benchmark for the new process since it's pretty easy to scale a memory chip design to a smaller gate size due to its simplicity.
It's worse: It's not just the borders, even if they weren't rendered by the application and done by an window manager you wouldn't been able to move, resize etc. the window if the application hangs:
With X11 in case you can't kill an process for whatever reasons (hung in disk-wait-state e.g. if the application accesses files on an NFS server that went down) you still can close it's windows. (Or iconify them or move them to another window... )With this concept presented here a wild running application can ruin the whole X^Hwhatever-its-name-will-be session: All screenspace occupied by the application's windows will become unusable, i.e. you can't even move an other window over it.
Should win acadamy awards for
- crappiest special effects
- most unrealistic and most predictable storyline
- worst acting
- biggest ignorance to history in history
Isn't Linux under some source control system now?
So you should be able to sync your local sources with a public repository at any time you want and don't havve to download huge tar files or fiddle with patches.
> ... can compete in REAL (eg NOT burst mode for 512 bytes) I/O speed ...
What makes you think "burst mode for 512 bytes" is not real?. Harddisc sectors are nowadays 512 bytes large and their contents are transferred in bursts. SCSI doesn't even have commands to transfer single bytes out/or into a sector (or "block" in SCSI terms), so I/O always has to be transferred in bursts of 512 bytes (or more).
> isn't that a great paraphrased poem? afaik, it's from nazi germany.
i cs/niem oller.shtml
It sounds related to "the" (there are many versions of it) famous poem by Martin Niem"oller.
see
http://www.hoboes.com/html/FireBlade/Polit
or use your favourite search engine
Oh, yes, sorry. The cool CGI effects were in 2010 not 2001.
He landed on Japetus (Iapetus if you prefer). In the middle of the trailing (bright) side of Japetus to be precise.
;-)
I guess they changed it for Jupiter since they got those cool CGI effects of jupiter from a scientific project to simulate its athomosphere.
I bet /sparc will win. IIRC Sun itself suggest you to run a 32 bit version of solaris on the Ultra 1.
> BTW, what's the count on Russian space failures? I know they've had their accidents, but I can't think /insomnia
> of when and where. It's not like we've got a spotless record anyhow...
In manned space the losses of astronauts/cosmonauts in a per launch or per flight hour ratio are much better for the soviet/russian space agency (Soyuz 1 (1) and Soyuz 11 (3)) than the for NASA (14 in two shuttle accidents).
However the Soviets had two incindents with rockets exploding on launch pad while fueling them and that caused nearly 200 peoples lifes.
> I believe Arianespace will be using Russian launchers at some point.b _index.html
Arianespace IS already operating Soyus launches from Baikonur in some way, see here: http://www.arianespace.com/site/launcher/soyuz_su
> However, it's hard to imagine the EU wanting a manned space program (or indeed any big showy
> projects with very dubious returns) what with all the new accession countries joining next
> month.
Arianespace is not ESA and ESA is not EU. I.e. not every EU member is also ESA member.
It should be noted that there are plenty of joint ventures between US and Russian/Ukrainian companies as well. E.g. the Atlas V launchers are using russian RD180 engines and Sea Launch is (Or was? No launch for 2 years) using Ukrainian Zenith launch vehicles.
It's even mentioned in the article the editor cites. *sigh*
The culture of Teotihuacan predates the Aztecs by a few hundred years. It climaxed around 500, went under around 600 (my sources say 700). The so-called Aztecs arived around 1200 and gave the site its name, but that's the only Aztec connection to Teotihuacan.
No, I just said that that it's not the GPL that blocks XFree4.4 from getting into OpenBSD since OpenBSD is NOT RELEASED UNDER THE GPL.
The philosophy behind OpenBSD is based on Theo, the decisons what licences are acceptable for OpenBSD are based on its philosophy so in the end they have to be Theo compatible.
Who cares about GPL-compatibility? It has to be Theo-compatible to be part of OpenBSD.
> I'm sure this is a problem on a lot of the 40 architectures, some of them are way old and limited
> to the sub-100MHz range
Nowadays the release binaries for most platforms except i386 are crosscompiled.
> Cross-compiling seems like a hairy mess.
Not with NetBSD (well, most platforms. There may be a few, which are not using the build.sh system).
Since the NetBSD build process bootstraps by building first a set of tools (make, binutils, compilers etc) and then uses this set to build the system.All you need is a bourne-shell compatible shell and a C/C++ compiler.That's why you can use a - say - solaris/sparc system to compile NetBSD/pmax.See the file BUILDING in the top directory of the source tree.
Sorry, the NATO-designation is "Foxhound", not Foxbat. The Foxbat is the Mig-25.
Military jets of the cold war aera are usally less critical than commercial jets. Think of quickly erected forward air bases and supply conditions in times of war (BTW: In Germany many straight parts of the autobahn were designed to be able to be converted to auxilary air bases quickly).
As an example, the Mig31 'Foxbat', capable of speeds exceeding Mach 2.83 is said to be able to start from unpaved runways. The F/A18 is designed to start and land on carriers, which means slow start and landing speeds and that means short starts and landings.