My old parts still serve me well (usually better than their younger siblings, in fact!). My network router is an old Emachine PIII 600 MHz with a (you'll love this) 20Gig 5.25 Quantum BigFoot drive running PfSense. It sports 180MB of old PC100 RAM that was lying around. All three PCI slots hold a NIC (2 gigabit and 1 100mbit), and except for the lights dimming when the BigFoot spins up, it sips juice from a ~200 watt PSU. Not that I ever get to see the lights dim: current uptime 312 days.
My other old box, serving on its fifth or sixth tour of duty is a 900 MHz Duron (Socket A, 'cause I was able to put three CPUs through that socket duing upgrades) is my main server. It runs Subversion, Samba, JBoss, and anything else that I need to stay up reliably. Aptly named 'Slacker', it runs Slackware Linux and is of modest, but acceptable, speed for serving files, web pages and NTP. Ironically, this box's CMOS is shot and it loses time whenever it doesn't have power... therefore, it controls the UPS for itself and the router. Current uptime 291 days.
Both boxes are reliable enough that they've been sitting in a home made rack headless for over a year now without incident. The storage server that sits at the bottom of the rack is a much newer 64 bit Opteron. It has been nothing but trouble. Regardless of which OS runs on the hardware, and I've tried many over the last three years, (Slackware, Fedora, Sabayon, OpenSolaris) it will simply fall over. From chipset issues, overheating, blowing power supplies (currently on number 3, I keep an extra on the shelf these days), to dropping perfectly good drives from RAID because it suddenly can't see them, the box has been nothing but misery with a very expensive price tag.
Keep your old boxes, they'll outlast your new gear and enjoy the new rig they inherit when that new gear fails and you've got another empty chassis and another new motherboard that won't fit in it. The last days of one technology are always better than the first days of a new technology.
This joke took a nasty turn for the worst and I'd rather like to back out while I still have my dignity... and my pants. Here's a well earned $20 and I bid you a good day, sir!
Won't a high drag suit also help him stabilize himself to avoid going in to a spin? He'll need the surface area (provided by a high drag suit) where the air is thinner, I think.
No doubt, I _STILL_ don't know exactly what a 'homegroup' is and why I can be part of a domain (or workgroup) at the same time as a homegroup. I don't know why Windows Media Player daemon sometimes pegs both my cores or what it's doing since I have the sharing service off, either. That being said, the new firewall is money compared to the old one. I just wish they wouldn't rearrange the control panels and rename all the settings every version of windows. Imagine my surprise when I had at least five separate places to configure my network and none of them sounded like what I was looking for!
Uh, prof, we're still in class; we know that isn't a glass of water you've been nursing at the podium for the last half hour... and stop referring to me as 'Senior Buzzkill' in your tweets.
Case in point, Microsoft's original TCP/IP stack was based on BSD licensed Spider (spyder? Too lazy to check). It shipped with Windows under a proprietary license and IIRC the BSD attribution could be found if you grepped the libraries binaries. That was way before my time, though (I'm 25), so I might not have it exactly correct.
I assume that you also apply this logic to household with pets. If cigarette smoke residue (more accurately, nicotine which sticks to copper) is enough to put your Mac out of warranty, then pet hair clogging the fans should, too. While we're at it, just having a dusty house applies by the same logic.
BTW, I've had several computers that I smoked right next to and I never had any problems with overheating... because I clean my computers and I know the difference between a hard drive and an ashtray. A little maintenance and common sense goes a long way.
Indeed. With the right (or more accurately, wrong) file system, IO scheduler, RAID layout, and workload, you can push your disk latency to well over 50 ms before it has a chance to get to the wire's buffer. The objective is to avoid hours of latency, not milliseconds. TCP/IP will take care of the road bumps if you make sure that the road doesn't stop at the edge of a cliff.
Let us not forget Windows Bob. It even became a joke at MS. Check out Bill Gates Last Day Video @~5:40 Ray Ozzie and Craig Mundie crack on BillG saying that they have to give credit where credit is due; Microsoft Bob was all Bill's idea.
Retired, eh? So I take it you write ADA-95;)
Seriously, though, what do you primarily write code in these days? Do you find that you have less of a desire to learn new languages and more of a desire to just Get Things Done?
I'm only 25 and I've found recently that I have a growing disdain for "shiny-language-of-the-month" and really I'd just like to use whatever works. I'm not sure if this is just a preference at this moment or something that will continue with time.
We should be happy that they even were aware that their numbers were poor. That means that someone is, at the least, paying attention if not objectively analyzing the data. The fact that it is a government agency makes it that much more astounding (IE. it's not going to make a difference in their paycheck or pension most likely).
Doesn't scheduling (process vs. thread) depend on the OS? IIRC Linux schedules threads the same as processes. IE. quantum slice size/interactivity credits and dynamic priorities are calculated per thread and penalties are assigned to their parent process. Windows, OTOH, does all of the accounting at the process level. We'll pretend for the moment that Windows fork is POSIX compliant.
Also, I'm not sure if it only applied to Green Threads (which have mostly fallen out of favor - at least in the JIT world. I think some interpreted language runtimes may still use them.), but I have heard of threads being broken down in to fibers.
That being said; you're right. The concept of a 'processor' has been abstracted so much that many EULAs have to define the term verbosely when the license limits the number of processors that the app can run on. I think the default definition, currently, is that a processor is a single socket and all of its cores. It will be interesting to see what happens as socket packages become essentially multiple NUMA style processors (with their own L[123] caches/dedicated RAM and memory controllers) that share only a high speed internal and external bus.
Will these tests apply for open, closed, or both so far as strings are concerned? IIRC, open and closed string models are mutually exclusive and should each have a different 'signature' that could be tested for.
Slashdot Mirror
He didn't say the first N prime or odd numbers greater than zero. If you're going to be clever, don't be stupid.
My old parts still serve me well (usually better than their younger siblings, in fact!). My network router is an old Emachine PIII 600 MHz with a (you'll love this) 20Gig 5.25 Quantum BigFoot drive running PfSense. It sports 180MB of old PC100 RAM that was lying around. All three PCI slots hold a NIC (2 gigabit and 1 100mbit), and except for the lights dimming when the BigFoot spins up, it sips juice from a ~200 watt PSU. Not that I ever get to see the lights dim: current uptime 312 days.
My other old box, serving on its fifth or sixth tour of duty is a 900 MHz Duron (Socket A, 'cause I was able to put three CPUs through that socket duing upgrades) is my main server. It runs Subversion, Samba, JBoss, and anything else that I need to stay up reliably. Aptly named 'Slacker', it runs Slackware Linux and is of modest, but acceptable, speed for serving files, web pages and NTP. Ironically, this box's CMOS is shot and it loses time whenever it doesn't have power... therefore, it controls the UPS for itself and the router. Current uptime 291 days.
Both boxes are reliable enough that they've been sitting in a home made rack headless for over a year now without incident. The storage server that sits at the bottom of the rack is a much newer 64 bit Opteron. It has been nothing but trouble. Regardless of which OS runs on the hardware, and I've tried many over the last three years, (Slackware, Fedora, Sabayon, OpenSolaris) it will simply fall over. From chipset issues, overheating, blowing power supplies (currently on number 3, I keep an extra on the shelf these days), to dropping perfectly good drives from RAID because it suddenly can't see them, the box has been nothing but misery with a very expensive price tag.
Keep your old boxes, they'll outlast your new gear and enjoy the new rig they inherit when that new gear fails and you've got another empty chassis and another new motherboard that won't fit in it. The last days of one technology are always better than the first days of a new technology.
This joke took a nasty turn for the worst and I'd rather like to back out while I still have my dignity... and my pants.
Here's a well earned $20 and I bid you a good day, sir!
Well played, good sir! Smashing well played. In fact, two can play that game...
"Knock, Knock!"
But... that's exactly what we're all afraid of!
You jerk. I was about to have a productive day... but there's time for a quick game or three.
It's cool. You'll enjoy it. Plus, it'll only take an hour of your time to prove me right or wrong.
Won't a high drag suit also help him stabilize himself to avoid going in to a spin? He'll need the surface area (provided by a high drag suit) where the air is thinner, I think.
... And another bites the dust...
You're lucky that you didn't get it to play; mine played to six minutes and then just stopped and won't play or let me skip past that.
No doubt, I _STILL_ don't know exactly what a 'homegroup' is and why I can be part of a domain (or workgroup) at the same time as a homegroup. I don't know why Windows Media Player daemon sometimes pegs both my cores or what it's doing since I have the sharing service off, either. That being said, the new firewall is money compared to the old one. I just wish they wouldn't rearrange the control panels and rename all the settings every version of windows. Imagine my surprise when I had at least five separate places to configure my network and none of them sounded like what I was looking for!
Uh, prof, we're still in class; we know that isn't a glass of water you've been nursing at the podium for the last half hour... and stop referring to me as 'Senior Buzzkill' in your tweets.
Case in point, Microsoft's original TCP/IP stack was based on BSD licensed Spider (spyder? Too lazy to check). It shipped with Windows under a proprietary license and IIRC the BSD attribution could be found if you grepped the libraries binaries. That was way before my time, though (I'm 25), so I might not have it exactly correct.
I assume that you also apply this logic to household with pets. If cigarette smoke residue (more accurately, nicotine which sticks to copper) is enough to put your Mac out of warranty, then pet hair clogging the fans should, too. While we're at it, just having a dusty house applies by the same logic.
BTW, I've had several computers that I smoked right next to and I never had any problems with overheating... because I clean my computers and I know the difference between a hard drive and an ashtray. A little maintenance and common sense goes a long way.
Indeed. With the right (or more accurately, wrong) file system, IO scheduler, RAID layout, and workload, you can push your disk latency to well over 50 ms before it has a chance to get to the wire's buffer. The objective is to avoid hours of latency, not milliseconds. TCP/IP will take care of the road bumps if you make sure that the road doesn't stop at the edge of a cliff.
Jerry Seinfeld.
*Microsoft Bob
Let us not forget Windows Bob.
It even became a joke at MS. Check out Bill Gates Last Day Video @~5:40 Ray Ozzie and Craig Mundie crack on BillG saying that they have to give credit where credit is due; Microsoft Bob was all Bill's idea.
Nope. This is a business trip of sorts. It's just coming back to deliver the death blow; after that it's out quicker than a fat kid in dodge ball.
Retired, eh? So I take it you write ADA-95 ;)
Seriously, though, what do you primarily write code in these days? Do you find that you have less of a desire to learn new languages and more of a desire to just Get Things Done?
I'm only 25 and I've found recently that I have a growing disdain for "shiny-language-of-the-month" and really I'd just like to use whatever works. I'm not sure if this is just a preference at this moment or something that will continue with time.
I'll get off your lawn now.
... and probably well armed...
We should be happy that they even were aware that their numbers were poor. That means that someone is, at the least, paying attention if not objectively analyzing the data. The fact that it is a government agency makes it that much more astounding (IE. it's not going to make a difference in their paycheck or pension most likely).
Doesn't scheduling (process vs. thread) depend on the OS? IIRC Linux schedules threads the same as processes. IE. quantum slice size/interactivity credits and dynamic priorities are calculated per thread and penalties are assigned to their parent process. Windows, OTOH, does all of the accounting at the process level. We'll pretend for the moment that Windows fork is POSIX compliant.
Also, I'm not sure if it only applied to Green Threads (which have mostly fallen out of favor - at least in the JIT world. I think some interpreted language runtimes may still use them.), but I have heard of threads being broken down in to fibers.
That being said; you're right. The concept of a 'processor' has been abstracted so much that many EULAs have to define the term verbosely when the license limits the number of processors that the app can run on. I think the default definition, currently, is that a processor is a single socket and all of its cores. It will be interesting to see what happens as socket packages become essentially multiple NUMA style processors (with their own L[123] caches/dedicated RAM and memory controllers) that share only a high speed internal and external bus.
Sorry for rambling, it's quite late here.
What is the reference?
Will these tests apply for open, closed, or both so far as strings are concerned? IIRC, open and closed string models are mutually exclusive and should each have a different 'signature' that could be tested for.