with network built in, and a cheap OEM celeron. Mix in bootable USB key, RAM, power supply, shake. Serve cold.
In fact, none of the PS2, Gamecube, or XBox have NEARLY enough RAM to even fathom running a database, let alone much else (since you can't even cache very much from fixed media, for example).
Duh.
It might make a good kerberos or DNS server or something that needs to be "hardened" and always up, with a small in-memory image. But that's probably only going to fly in a college dorm at a Tech University.
and the Opteron can hold it one register. Just prefix the instruction with the OTHER size prefix byte. (for those who don't already know, most intel instructions if operating on a 16-bit short require a prefix byte. On the Opteron, you use a different prefix to get 64-bit ints and the extended regs)
There are plenty of places where it makes sense to use 64-bit regs, especially in the kernel when involving counters, timers, GIDs, and such.
I was suggesting that the implementation of IM in SIP in RFC 3428 was not universally accepted as the way things are going to be. Note that it has not yet become an approved standard. Some people believe that piggybacking IM into SIP was not really a good idea. I have barely glanced at the arguments so I can't comment, I'm just parroting.
Since I've never used jabber, and only looked at SIP (but not for IM), I wouldn't pretend to be knowledgable about the availability of tools.
But I did want stress the differences between the two groups/protocol and their backers conflicting opinions.
The width of the bus between a 686-era processor and RAM was at least 64-bits wide. The FPU ops completed in trivial numbers of cycles (3, sometimes less). So I don't really see how it being 64-bit helps (hint, it doesn't as far as that's concerned). Not to mention you still had to align doubles on 8-byte boundaries, so that should have told you something.
It's ONLY important for flat addressing and having the extra register set in the case of AMD64. They hardly changed the FPU/MMX layer (they did add more regs and added a 3rd FPU core, which helps to parallelize instructions, but that has nothing to do with the jump from 32 to 64 bit capability)
Keep in mind that 1) 64-bit instructions take an extra byte to encode 2) it's NOT the default, even in 64-bit mode 3) 32-bit instructions are used primarily and are intermixed with 64-bit ones when you don't need them 4) the 32-bit instructions execute even faster on here than on all previous archs. clock per clock. Your FPU code will not use the 64-bit extension byte except when using more than 8 operands in the reg stack (or extended XMM/SSE regs)
For pure FP math, the Opteron succeeds not because it is 64-bit, but because it has another FPU core, and twice as many FPU registers. Also, it's got better branch prediction and is generally faster per clock.
And with your faster number crunching, you use the 64-bit addressing to process data sets >4GB. Capache?
SIP is something completely different, it grew out of VoIP-related technologies... it's the same type of thing, but it's not at all compatible, and it's not standardized (yet).
XMPP has attracted some companies attention, while SIP has attracted other companies mindshare. There will be a split in enterprise messaging systems in the next few years.
I should form a company that sells gateways between the two...:evil grin:
I imagine this process is well underway, and nearing completions for the Solaris 10 release.
Meanwhile a port of HP-UX is imminent if the Itanium tanks. Take the x86 port effort + 64-bit clean IA64 version and mix together and you get the Opteron optimized version (well, it's a wee bit more complicated than that...)
So we'll have Darwin, *BSD, Linux, HP-UX (probably), Solaris, Windows NT 5.2, zow! All that's left is for Apple to port the GUI, and we'll have a cool platform for the future.
They could have chosen Ctrl+Alt+PrnScr/SysRq, but since people were used to the three finger salute causing a system trap, they kept the legacy convention (they wouldn't expect any application to want to bind to it)
it can't be handled by any input APIs (Win32/DirectInput)... it gets handled directly by the keyboard driver.
This kind of keystroke is called SAK (Secure Attention Key), as it's not specific to Windows NT. SAK is an keystroke (or other event, for example sending "break" on a Sun serial port) that the OS guarantees only the Operating System can ever handle.
They released it a looooong time ago in a Service Pack.
You can create "bounce" scripts that su to a cripple user (still in the admin group) which runs the application.
So you'd create a warcraft user in the Administrators group, deny interactive/network logon, then create the bounce script reference by a shortcut on your desktop.
For full protection, you make the bounce script invisible to everyone except for "interactive users". (The bounce script contains the password for the special admin user, so you don't want people browsing your network share to see it if you can avoid it)
put each "urlopen" in it's own thread, but don't reap them. Set a reasonable timeout (2, 3 seconds) in each thread that sets the called function to "kill myself".
Spawn as many per second as you feel comfortable with in an outer loop. Maybe you keep a count of outstanding threads (this variable is decreased on "kill myself" and increased per spawn) and adjust spawn interval accordingly. You'll make the site unavailable with many fewer upstream machines.
Is there anything in particular that you're doing right now that I can't do? I mean, name it. Be honest.
And the Apples are far-and-away ahead in the "usability" game. Guess which archiver they don't have support for... hmmm. Guess which ones are bundled with the OS and integrate right in. I'll leave that to your imagination. It's a good excercise.
Add a new directory called %USERPROFILE%/quickstart to your PATH, then make a directory called "quickstart" underneath your profile (i.e. C:\documents and settings\administrator\quickstart). Create a shortcut to that in your QuickLanch menu as well.
You can drag whatever shortcuts you want in there... make batch scripts in there too. Then you can call them from anywhere with the Windows Key + R combo, or you can open it inside quicklaunch and run stuff that way (even use drag+drop)
WinRAR doesn't work on my various flavors of *nix. So it doesn't get used. EVER. End of story. Especially on my server where I care about upload (I've got 192k up myself, quite dreadful). I think bz2 works quite nicely, thank you. And I can actually write the encoder and decoder for that one. (You should have read the Dr. Dobbs article on the algorithm, it was quite interesting)
I'm not lazy nor a bastard. Elitist, bitchy, maybe. I think you need to rethink your adjectives.
Slashdot Mirror
with network built in, and a cheap OEM celeron. Mix in bootable USB key, RAM, power supply, shake. Serve cold.
In fact, none of the PS2, Gamecube, or XBox have NEARLY enough RAM to even fathom running a database, let alone much else (since you can't even cache very much from fixed media, for example).
Duh.
It might make a good kerberos or DNS server or something that needs to be "hardened" and always up, with a small in-memory image. But that's probably only going to fly in a college dorm at a Tech University.
and the Opteron can hold it one register. Just prefix the instruction with the OTHER size prefix byte. (for those who don't already know, most intel instructions if operating on a 16-bit short require a prefix byte. On the Opteron, you use a different prefix to get 64-bit ints and the extended regs)
There are plenty of places where it makes sense to use 64-bit regs, especially in the kernel when involving counters, timers, GIDs, and such.
you're only back where you need to be at 3.0x2 = 6.0 GHz. Nope, it looks like they've screwed up that part. L1 latency is a killer.
I was suggesting that the implementation of IM in SIP in RFC 3428 was not universally accepted as the way things are going to be. Note that it has not yet become an approved standard. Some people believe that piggybacking IM into SIP was not really a good idea. I have barely glanced at the arguments so I can't comment, I'm just parroting.
Since I've never used jabber, and only looked at SIP (but not for IM), I wouldn't pretend to be knowledgable about the availability of tools.
But I did want stress the differences between the two groups/protocol and their backers conflicting opinions.
I didn't even know what the hell it was until right now! Wouldn't be worth much anykinda-cred.
That's probably why no one used it. Hmm.
I've been waiting for the *nix version. Where is my *nix version? :-)
The width of the bus between a 686-era processor and RAM was at least 64-bits wide. The FPU ops completed in trivial numbers of cycles (3, sometimes less). So I don't really see how it being 64-bit helps (hint, it doesn't as far as that's concerned). Not to mention you still had to align doubles on 8-byte boundaries, so that should have told you something.
It's ONLY important for flat addressing and having the extra register set in the case of AMD64. They hardly changed the FPU/MMX layer (they did add more regs and added a 3rd FPU core, which helps to parallelize instructions, but that has nothing to do with the jump from 32 to 64 bit capability)
Keep in mind that 1) 64-bit instructions take an extra byte to encode 2) it's NOT the default, even in 64-bit mode 3) 32-bit instructions are used primarily and are intermixed with 64-bit ones when you don't need them 4) the 32-bit instructions execute even faster on here than on all previous archs. clock per clock. Your FPU code will not use the 64-bit extension byte except when using more than 8 operands in the reg stack (or extended XMM/SSE regs)
For pure FP math, the Opteron succeeds not because it is 64-bit, but because it has another FPU core, and twice as many FPU registers. Also, it's got better branch prediction and is generally faster per clock.
And with your faster number crunching, you use the 64-bit addressing to process data sets >4GB. Capache?
SIP is something completely different, it grew out of VoIP-related technologies... it's the same type of thing, but it's not at all compatible, and it's not standardized (yet).
:evil grin:
XMPP has attracted some companies attention, while SIP has attracted other companies mindshare. There will be a split in enterprise messaging systems in the next few years.
I should form a company that sells gateways between the two...
operate on 8-byte aligned IEEE floats and (at least) 80-bit wide FP registers?
And it's been that way since the 386?
I imagine this process is well underway, and nearing completions for the Solaris 10 release.
Meanwhile a port of HP-UX is imminent if the Itanium tanks. Take the x86 port effort + 64-bit clean IA64 version and mix together and you get the Opteron optimized version (well, it's a wee bit more complicated than that...)
So we'll have Darwin, *BSD, Linux, HP-UX (probably), Solaris, Windows NT 5.2, zow! All that's left is for Apple to port the GUI, and we'll have a cool platform for the future.
They could have chosen Ctrl+Alt+PrnScr/SysRq, but since people were used to the three finger salute causing a system trap, they kept the legacy convention (they wouldn't expect any application to want to bind to it)
it can't be handled by any input APIs (Win32/DirectInput)... it gets handled directly by the keyboard driver.
This kind of keystroke is called SAK (Secure Attention Key), as it's not specific to Windows NT.
SAK is an keystroke (or other event, for example sending "break" on a Sun serial port) that the OS guarantees only the Operating System can ever handle.
I think it beats out the Milton Bradley bullshit item.
At some point you can't hide the problem, and it consumes you, so you take the pity angle to make yourself feel better w.r.t. society.
that is used in mission and life critical situations.
They released it a looooong time ago in a Service Pack.
You can create "bounce" scripts that su to a cripple user (still in the admin group) which runs the application.
So you'd create a warcraft user in the Administrators group, deny interactive/network logon, then create the bounce script reference by a shortcut on your desktop.
For full protection, you make the bounce script invisible to everyone except for "interactive users". (The bounce script contains the password for the special admin user, so you don't want people browsing your network share to see it if you can avoid it)
put each "urlopen" in it's own thread, but don't reap them. Set a reasonable timeout (2, 3 seconds) in each thread that sets the called function to "kill myself".
Spawn as many per second as you feel comfortable with in an outer loop. Maybe you keep a count of outstanding threads (this variable is decreased on "kill myself" and increased per spawn) and adjust spawn interval accordingly.
You'll make the site unavailable with many fewer upstream machines.
A little knowledge is a dangerous thing.
Is there anything in particular that you're doing right now that I can't do? I mean, name it. Be honest.
And the Apples are far-and-away ahead in the "usability" game. Guess which archiver they don't have support for... hmmm. Guess which ones are bundled with the OS and integrate right in. I'll leave that to your imagination. It's a good excercise.
Add a new directory called %USERPROFILE%/quickstart to your PATH, then make a directory called "quickstart" underneath your profile (i.e. C:\documents and settings\administrator\quickstart). Create a shortcut to that in your QuickLanch menu as well.
You can drag whatever shortcuts you want in there... make batch scripts in there too. Then you can call them from anywhere with the Windows Key + R combo, or you can open it inside quicklaunch and run stuff that way (even use drag+drop)
Hah... Everyone pirates PC games! And those games don't have to get Nintendo's seal of quality or Sony's blessing to make it to market.
WinRAR doesn't work on my various flavors of *nix. So it doesn't get used.
EVER.
End of story.
Especially on my server where I care about upload (I've got 192k up myself, quite dreadful). I think bz2 works quite nicely, thank you. And I can actually write the encoder and decoder for that one. (You should have read the Dr. Dobbs article on the algorithm, it was quite interesting)
I'm not lazy nor a bastard. Elitist, bitchy, maybe. I think you need to rethink your adjectives.
Oh wait, why am I not modded up? I guess your inclinations are incorrect.
You can play sim-sex-conquest all you want in some European countries and Asia (esp. Japan).
but so do all those built-in bells and whistles on the motherboard.