And no, they're not using an instantaneous tau to approximate a decay distribution. Anyone who has ever cooked popcorn knows better than that.
I don't know what you're talking about. I'm precise enough that my decay distribution is zero. When I cook popcorn all of the kernels pop at exactly the same moment. It scares the heck out of the dog. You must be doing it wrong.
We reused an old piece of junk machine as a print server in our development lab, which was connected to the enterprise network. We gave it an appropriately descriptive name, Dungpile.
Little did we know that in its prior life Dungpile had been configured as a DHCP server. (We didn't look at it too closely... our bad.)
One day we hear a frazzled guy from the IT department going door to door crying, "I'm looking for Dungpile! Does anyone know where Dungpile is?"
It turns out the enterprise DHCP server had a hiccup, and in the subsequent negotiation for which backup would take over, Dungpile won out. Our little print server started handing out 10.10.*.* IP addresses (it was evidently set up for a private network) to the enterprise workstations. That worked very poorly.
The IT folks could tell the bogus addresses were coming from a machine called Dungpile, but didn't know where it was located. (I don't know why they didn't just boot Dungpile and force their primary server to resume duties. The weren't a great team.)
Anyway, it made my day hearing someone wandering the hall yelling about finding dungpile.
Yes, but do it with style. Buy a small refrigerator, spray paint it gray, add rails, and rack mount the sucker. Just make sure you put the servers in the top of the fridge and the beer in the bottom so you don't risk server damage from leaks.
Slashdot Mirror
And no, they're not using an instantaneous tau to approximate a decay distribution. Anyone who has ever cooked popcorn knows better than that.
I don't know what you're talking about. I'm precise enough that my decay distribution is zero. When I cook popcorn all of the kernels pop at exactly the same moment. It scares the heck out of the dog. You must be doing it wrong.
We reused an old piece of junk machine as a print server in our development lab, which was connected to the enterprise network. We gave it an appropriately descriptive name, Dungpile. Little did we know that in its prior life Dungpile had been configured as a DHCP server. (We didn't look at it too closely... our bad.) One day we hear a frazzled guy from the IT department going door to door crying, "I'm looking for Dungpile! Does anyone know where Dungpile is?" It turns out the enterprise DHCP server had a hiccup, and in the subsequent negotiation for which backup would take over, Dungpile won out. Our little print server started handing out 10.10.*.* IP addresses (it was evidently set up for a private network) to the enterprise workstations. That worked very poorly. The IT folks could tell the bogus addresses were coming from a machine called Dungpile, but didn't know where it was located. (I don't know why they didn't just boot Dungpile and force their primary server to resume duties. The weren't a great team.) Anyway, it made my day hearing someone wandering the hall yelling about finding dungpile.
Yes, but do it with style. Buy a small refrigerator, spray paint it gray, add rails, and rack mount the sucker. Just make sure you put the servers in the top of the fridge and the beer in the bottom so you don't risk server damage from leaks.