Yeah, I know, we're trying to suck-up to the moderators by poking fun at Microsoft.
But it's tasteless to do so in the context of a story that may lead to the ecological destruction and death or illness for thousands of people. Not to mention the diplomatic turmoil.
Well you probably would've had a better chance of getting that story through if you had mentioned one of the magic words. Namely, "Linux", since no there are no representatives for Linux, GNU, FSF, OSS, or anything of that ilk at that "Digital Dividends" conference. (They did send an invitation to RedHat who declined.)
But then, Linux Weekly News has been covering it pretty well. Maybe the boys here figure that putting it on/. would be redundant. And I'm apt to agree with them.
Oh, and when I said "conference" previously, I meant "bending-over-and-kissing-our-own-asses".
I don't think journaling, phase-trees, soft-updates, whatever are quite the panacea the hype seems to making them out to be. Not that they aren't useful or shouldn't be pursued -- they are and should. But the ultimate problem we're dealing with is that disks are slow. So writes are cached, and that's what causes problems when there's an unexpected poweroff. And caching occurs at many levels: the disk drive, possibly the disk controller, the device driver, and the file system driver. So the thing to remember is even the writes made as part of journaling/phase-tree/soft-update/whatever are, at some point, cached. So the potential for data loss is still very much present, and I fear (well, not really, since I don't give a damn if your computer crashes while downloading porn) that this hype over FS technologies might be presenting a false sense of security.
So in short, the problem with file system inconsistencies won't go away until we have storage devices fast enough to allow for immediate committal of writes. (But will we then have such incredibly faster RAM and bus speeds that even <1ms will be considered "slow"?)
Okay, so you use discrete pulses of signal to transmit the information. At first, there's not that much traffic so you can send pulses once every second. Then your traffic doubles so you start sending packets once ever half second. Then you send ever 0.25 seconds. Then 0.125 seconds, 0.0625, 0.03125, 0.015625, etc. etc. etc.
At what point do you begin sending pulses so frequently that you are effectively transmitting continuously?
Exactly. I can't understand why the W3C has drafted this as a seperate "standard" and not incorporated it as part of CSS. And for all intents and purposes, this could be just another set of implementation guidelines for CSS2, except:
Sec. 4.7, The MP-UA is not required to satisfy the CSS2 conformance statement pertaining to the handheld media type
You'll excuse me if I don't feel like digging up the relavent portion of the CSS2 spec (Sec. 7.3.1). But the point is, CSS2 and HTML4 were designed to be generic, implementation-neutral descriptors of content able to be applied to any type of display device. That's why there's a media attribute; so the standard doesn't have to be rewritten for some new media type, just outline the specifics for that implementation and wrap it with media="handheld" And if they thought that the current CSS2 implementation for handheld media was outdated, then update it. Not this divergent crap.
With analog phone taps (circuit switching) there is a physical pair of wires that you can determine with certainty only carry the audio conversations to or from a particular location. It's the electronic equivalent of a stake-out in front of a suspect's house.
Carnivore, however, is tapping a packet switched network. It has to sit there listening to all traffic with all different sources and destinations. Then they try to apply some automated software voodoo to only record the data within the bounds of the warrant. And in that sense, it's like having a stake-out in the food court of a mall that you know the suspect occassionally visits.
Consider these scenarios: [1]The suspect is able to send information in a way that bypasses the tap or is illegible (encrypted); the tap is ineffective. [2]The tap picks up information not belonging to the suspect but turns suspicion to another person who isn't a suspect; the warrant has been violated. [3]The tap picks up information not belonging to the suspect, but is seen as if it had; the suspect is wrongfully incriminated. [4]The tap picks up incriminating evidence relating to the suspect; the tap is effective.
So we end up with a 50% chance of getting information relating to the suspect, and only 25% that it's actually useful. But it's that other 50% that worries me, because there should be a 0% chance of that ever happening.
Oh, and about Mr. Perrit. He made a big point about saying that many of the reviewers are Republicans (opposed to the current Democratic administration). Oh yeah, Republicans have *never* done anything to compromise the privacy of citizens. That makes me feel a whole lot better. Fnord.
Just guessing here, but it looks to me like it'll crap out at "f[b++]=a/5;" since you don't assign a value to b.
Obfuscated C is either a)redundant b)C++ or c)MS Visual C
Re:What ever happened to ... (off topic)
on
Does P = NP?
·
· Score: 1
The supposed NBT before the web was multimedia. Remember all computers were being advertised as "MPC2"?
High temperature superconductors were and are real. The problem is the mass-medias ignorance of what was meant by "high temperature." That is, you merely need liquid nitrogen to get ceramics to superconduct, as opposed to the colder liquid oxygen for metallic materials.
trek has got to be one of the most ported program. (The first is obviously "Hello World"). Certainly it's shown up on a lot of computers an a lot of different forms.
When internet technologies were first debuted to the public at some convention in '79 or '80, there were two programs that were enormously popular. One was a simple chat program, the other was Trek.
At least, version 4.1 can. In the transport section of the QT cpanel you can tell it to use TCP port 80 (HTTP),instead of the usual UDP 5970-5999 (RTSP). If you need QT 4.1, go to http://www.apple.com/quicktime/download/support/ to get the stand-alone installer instead of the annoying internet-based installer. (It's about 8M)
For other means of getting through, you could ask around for a shell account that you can connect to via port 80. (Preferably with SSH.)
Boy, I would sure love to be hired to play Yahoo games and trade MP3s all day. Wait, you mean that's not what you've been hired to do?;-)
I think one of the factors was safety. Almost any type of refueling accident, even a "minor" leak could damage both the shuttle, the ISS, and of course endanger the lives of anyone in orbit. NASA has never lost an astronaut in space, and I'm sure they want to keep it that way. The cost of hauling the modules back and forth is probably a lot cheaper than an accident that takes someone's life will cost them.
Well whaddya know, there already is one. It's called Basilisk II. http://www.uni-mainz.de/~bauec002/B2Main.html
Works in Linux, Windows, BeOS, and AmigaOS.
Also, VMWare is x86 only and WINE is not an emulator.
Slashdot Mirror
Yeah, I know, we're trying to suck-up to the moderators by poking fun at Microsoft.
But it's tasteless to do so in the context of a story that may lead to the ecological destruction and death or illness for thousands of people. Not to mention the diplomatic turmoil.
... and then they exploit your image for marketing purposes.
(Bonus points for the first person to come up with an image of Tux sitting at a loom.)
God: "First Light!"
(And on the fifth day God created Natalie Portman, and he saw that it was good.)
Well you probably would've had a better chance of getting that story through if you had mentioned one of the magic words. Namely, "Linux", since no there are no representatives for Linux, GNU, FSF, OSS, or anything of that ilk at that "Digital Dividends" conference. (They did send an invitation to RedHat who declined.)
/. would be redundant. And I'm apt to agree with them.
But then, Linux Weekly News has been covering it pretty well. Maybe the boys here figure that putting it on
Oh, and when I said "conference" previously, I meant "bending-over-and-kissing-our-own-asses".
I don't think journaling, phase-trees, soft-updates, whatever are quite the panacea the hype seems to making them out to be. Not that they aren't useful or shouldn't be pursued -- they are and should. But the ultimate problem we're dealing with is that disks are slow. So writes are cached, and that's what causes problems when there's an unexpected poweroff. And caching occurs at many levels: the disk drive, possibly the disk controller, the device driver, and the file system driver. So the thing to remember is even the writes made as part of journaling/phase-tree/soft-update/whatever are, at some point, cached. So the potential for data loss is still very much present, and I fear (well, not really, since I don't give a damn if your computer crashes while downloading porn) that this hype over FS technologies might be presenting a false sense of security.
So in short, the problem with file system inconsistencies won't go away until we have storage devices fast enough to allow for immediate committal of writes. (But will we then have such incredibly faster RAM and bus speeds that even <1ms will be considered "slow"?)
Very true, no one is about to deny that ext2 is a dinosaur.
But how does soft-updates compare to Tux2? Which, believe it or not, happens to be what this article was about.
Okay, so you use discrete pulses of signal to transmit the information. At first, there's not that much traffic so you can send pulses once every second. Then your traffic doubles so you start sending packets once ever half second. Then you send ever 0.25 seconds. Then 0.125 seconds, 0.0625, 0.03125, 0.015625, etc. etc. etc.
At what point do you begin sending pulses so frequently that you are effectively transmitting continuously?
Exactly. I can't understand why the W3C has drafted this as a seperate "standard" and not incorporated it as part of CSS. And for all intents and purposes, this could be just another set of implementation guidelines for CSS2, except:
You'll excuse me if I don't feel like digging up the relavent portion of the CSS2 spec (Sec. 7.3.1). But the point is, CSS2 and HTML4 were designed to be generic, implementation-neutral descriptors of content able to be applied to any type of display device. That's why there's a media attribute; so the standard doesn't have to be rewritten for some new media type, just outline the specifics for that implementation and wrap it with media="handheld" And if they thought that the current CSS2 implementation for handheld media was outdated, then update it. Not this divergent crap.With analog phone taps (circuit switching) there is a physical pair of wires that you can determine with certainty only carry the audio conversations to or from a particular location. It's the electronic equivalent of a stake-out in front of a suspect's house.
Carnivore, however, is tapping a packet switched network. It has to sit there listening to all traffic with all different sources and destinations. Then they try to apply some automated software voodoo to only record the data within the bounds of the warrant. And in that sense, it's like having a stake-out in the food court of a mall that you know the suspect occassionally visits.
Consider these scenarios: [1]The suspect is able to send information in a way that bypasses the tap or is illegible (encrypted); the tap is ineffective. [2]The tap picks up information not belonging to the suspect but turns suspicion to another person who isn't a suspect; the warrant has been violated. [3]The tap picks up information not belonging to the suspect, but is seen as if it had; the suspect is wrongfully incriminated. [4]The tap picks up incriminating evidence relating to the suspect; the tap is effective.
So we end up with a 50% chance of getting information relating to the suspect, and only 25% that it's actually useful. But it's that other 50% that worries me, because there should be a 0% chance of that ever happening.
Oh, and about Mr. Perrit. He made a big point about saying that many of the reviewers are Republicans (opposed to the current Democratic administration). Oh yeah, Republicans have *never* done anything to compromise the privacy of citizens. That makes me feel a whole lot better. Fnord.
Someone hurry up and get a web server on one of these so we can slashdot a dog!
Ah, but you forget MS added WSH in 4.1 (Win98)
'biteme.vbs
Do
MsgBox "BITE ME", vbInformation, "BITE ME"
Loop
Just guessing here, but it looks to me like it'll crap out at "f[b++]=a/5;" since you don't assign a value to b.
Obfuscated C is either a)redundant b)C++ or c)MS Visual C
The supposed NBT before the web was multimedia. Remember all computers were being advertised as "MPC2"?
High temperature superconductors were and are real. The problem is the mass-medias ignorance of what was meant by "high temperature." That is, you merely need liquid nitrogen to get ceramics to superconduct, as opposed to the colder liquid oxygen for metallic materials.
Boy, wouldn't that be something
Well, something to think about the next time the subject of online voting comes up.
And Windows is Altamont
I'm glad that Apple didn't pursue BeOS, because if they had gone down that road we most likely would not have Darwin.
trek has got to be one of the most ported program. (The first is obviously "Hello World"). Certainly it's shown up on a lot of computers an a lot of different forms.
When internet technologies were first debuted to the public at some convention in '79 or '80, there were two programs that were enormously popular. One was a simple chat program, the other was Trek.
Now, for a completely meaningless benchmark of how fast a computer can do nothing, there's the Fhlushstone
Okay, Lister is doing Robot Wars. Kryten is doing Scrapheap Challenge. So where's Rimmer at? How about Cat?
At least, version 4.1 can. In the transport section of the QT cpanel you can tell it to use TCP port 80 (HTTP),instead of the usual UDP 5970-5999 (RTSP). If you need QT 4.1, go to http://www.apple.com/quicktime/download/support/ to get the stand-alone installer instead of the annoying internet-based installer. (It's about 8M)
;-)
For other means of getting through, you could ask around for a shell account that you can connect to via port 80. (Preferably with SSH.)
Boy, I would sure love to be hired to play Yahoo games and trade MP3s all day. Wait, you mean that's not what you've been hired to do?
I think one of the factors was safety. Almost any type of refueling accident, even a "minor" leak could damage both the shuttle, the ISS, and of course endanger the lives of anyone in orbit. NASA has never lost an astronaut in space, and I'm sure they want to keep it that way. The cost of hauling the modules back and forth is probably a lot cheaper than an accident that takes someone's life will cost them.
Well, they could only afford the royalties for one Disney character, so....
So when can we expect an announcement from Debian that the currently unstable "woody" will eventually be released as 7.2, and not 2.4 as expected?
Well whaddya know, there already is one. It's called Basilisk II. http://www.uni-mainz.de/~bauec002/B2Main.html
Works in Linux, Windows, BeOS, and AmigaOS.
Also, VMWare is x86 only and WINE is not an emulator.