Something funny about those Pentiums.. There were shady dealers who would relabel them. I worked at a rather shady computer store around then. We'd get "Pentium 133Mhz", but about 20% of the time, they wouldn't boot at 133. If we lowered the speed to 120, they were fine. People who wanted to overclock their new P133 were SOL, since they were already overclocked.
That was a long time ago, and I am happy to report that the store is long since gone. The owner ran up a huge bill with his suppliers, pocketed the profits, and shut the doors one day. He got busted for tax evasion a few years later, and had free room and board for a while in a state prison.
I suspect the buzzing on your phone isn't coming from your phone. It's coming from the implant in your head. Have you checked for signs of alien abduction? I suspect that you may fit nicely in another demographic.
Noob.:) The first PC I completely built by hand was a 386. I'm pretty sure it was an Intel, only because AMD was still tied up in court about theirs. As I recall, around that era the other options at the time were Cyrix/TI, Chips, and IBM.
I really don't miss those good old days. All the dip switches and jumpers required for 286/386/486. Things are so much easier now. If it fits, it's probably compatible. Plug it in, turn it on. If it boots, you have a winner.:)
Only for you people using a GUI. Real men read Slashdot from a text console with lynx. Insane people read it with telnet and a script to parse the HTML for text mode viewing. I hear even RMS has started using graphical web browsers on occasion, so I guess that trick may work on him now.:)
The spec may say that there should be at least 64K available, but that doesn't mean that it is. That is available for something to write into, so if the UEFI already writes something there, 36K or less could fill it.
It actually seems to be a forewarning of future problems. 28K have already been used up by something, it's already 44% through its life. If it's a fairly new machine, that doesn't look so good for it's longevity. Since I don't have a problem machine in front of me (and I'm glad I don't), I can't really even hope to look in there and see what's wasting the space.
I've been fine with my phones for years. Recently I've been playing Ingress on my HTC EVO Design 4g. That can suck up a battery pretty quick. Even on a 2.1A charger it doesn't keep up all that well. After an hour or two, it starts complaining. I found replacement batteries for about $5/ea on Amazon. It's much easier to swap batteries, than to sit at a portal for 1/2 hour waiting for the battery to charged enough to run the game for a while. The car charger isn't all that useful when walking around to resonators, or in a high density area.
Wasn't there a practice run done? Really, if you're responsible for a multi-billion dollar event, it might be a good idea to fire everything up a few times and make sure it behaves as intended.
I just introduced an Intel fan to the wonders of AMD. He just knew that he'd always been told "Use Intel". I told him about my home machine. An air cooled AMD FX-8320 @4.01Ghz w/ 16GB RAM an a AMD 7770 w/ 1GB GDDR5. Every game I play, I crank all the settings all the way up, and the frame rate and quality is great.
I gave him some spare parts for his kids. Phenom II x6 1110T, motherboard, and a stack of RAM that he got 8GB to work together with, and a couple ATI 55xx video cards. He got the standard used parts disclaimer, "It all worked when I took it out, no guarantees that they do now." Not bad for a total of $0.
We spent some time comparing the Intel and AMD current pricing, and he didn't see any reason to use Intel any more.
Someone will reply, saying some benchmark says a comparable Intel is faster. Someone else will show a different benchmark says AMD is faster. For the price, I don't care, they just work, work well, and with the savings I don't mind upgrading again in 6 months. With the numbers we found that day, he can upgrade about 4 times and still come out under the Intel pricing.
Anyone can sue anyone else, at any time, for anything.
Here, one of the morning radio show hosts spent two weeks in court because another morning radio show host was offended that there were jokes made about him.
Two weeks, and a metric fucktonne of money spent by both sides, so the jury could decide in just a few minutes that the accuser was a whiny bitch.
I paraphrase that decision, of course. It was something like 47 items of the lawsuit, each decided as "as you kidding, we're only getting paid $15/day for this."
I've seen that too. Mostly with fairly open hosting machines. Like, letting anyone sign up for free or low cost hosting. I saw a lot of them that were built for one platform (usually Redhat), where the libraries didn't quite line up with the running system.
At one place, I was collecting them. The script kiddie would put their SSH server on a high port. It worked great, except they couldn't get root with it, and they couldn't get to the daemon through the firewalls. It was rather entertaining.
I hated the free hosting servers. They were constantly trying to do bad things. They never succeeded, but I had to go prune those accounts on a regular basis. The worst were people trying to host anime porn on our servers, and link it from message boards in east Asia. I was tempted to block all access from east Asia, except we did have a lot of paying customers over there.
I was asked to clean some exploited servers in the wild that had compromised SSH binaries in them. This was about 10 years or so ago, so this is really a not current news story.
Thankfully most script kiddies are exactly that, and their script left the source on the machine for me to review. Why? I guess to compile on the machine to make sure it used the local libraries. They generally didn't have passwords hard coded though, they used SSH keys. The passwords they stole were usually stored locally in a file, and sent to somewhere in eastern Europe or Asia. I have no idea if that was by the script kiddie design or the person who rolled it up. It's a pretty slick trick though. You get the script kiddies to gather intel from compromised machines, and feed it back to you. Now you have access to every machine the script kiddies compromised.
The funny part about most of the cleanups was, the version of SSH they put on was newer than the remotely exploitable version they got in with.
Yup. There are actually several reasonably priced hosting services in Iceland. I was shopping for international homes for some of my data, until I thought about it and none of my data is worth spending money to hide.:) Iceland was pretty high on the list though.
Well, if we didn't say it, they'd all make their passwords "password", their own first name, or some other amazingly simple word.
They always glaze over when you try to explain strong passwords. No matter what you tell them, you can always sit down at their desk and say "what's your password?", just to find out it's "Password1" or "1234567A"
But you do realize that there are plenty of resume fluffed "coders" who would fail it.
There are languages that I was proficient in, that I haven't touched in years. I'm honest on my resume, things that I've forgotten, I take off before I start sending the resumes out. Even things I haven't touched in more than a couple years get dropped.
A lot of people keep everything they've ever known on their resume. For some, that's still a pretty short list. I've asked candidates about some of their experience, to find out that they barely touched it years before, and wouldn't know how to begin. Some just list skills to match the position advertisement, and assume they can get the company to pay for training later.
Oh my god, you can't delete code! It worked for us in 1998, and it's still working on our circa 1998 machines. What the hell are you thinking?!
Kidding aside, I comment and date old code, and add new code. It's not only there for restoration purposes (ya, ya, version control and stuff are there too), but if someone gets a new great idea on adding new code, they may find exactly that has already been removed with good reason.
When it's my own code that I maintain with no one else, I ditch the old commented code after about a year. Sometimes it sits there for longer, because it was actually good code that didn't suit that particular purpose.
I have one chunk of code in particular that won't get ditched for a longtime. It's a HTML filter, that takes all kinds of Microsoft specific characters and converts them into HTML friendly characters. I did it up better with a much smaller chunk of code, that can do a lot more, but occasionally I reference those old bits.
Slashdot Mirror
Something funny about those Pentiums.. There were shady dealers who would relabel them. I worked at a rather shady computer store around then. We'd get "Pentium 133Mhz", but about 20% of the time, they wouldn't boot at 133. If we lowered the speed to 120, they were fine. People who wanted to overclock their new P133 were SOL, since they were already overclocked.
That was a long time ago, and I am happy to report that the store is long since gone. The owner ran up a huge bill with his suppliers, pocketed the profits, and shut the doors one day. He got busted for tax evasion a few years later, and had free room and board for a while in a state prison.
Who hasn't? I even submitted pictures. All I got was just got an email asking me for more.
I suspect the buzzing on your phone isn't coming from your phone. It's coming from the implant in your head. Have you checked for signs of alien abduction? I suspect that you may fit nicely in another demographic.
Noob. :) The first PC I completely built by hand was a 386. I'm pretty sure it was an Intel, only because AMD was still tied up in court about theirs. As I recall, around that era the other options at the time were Cyrix/TI, Chips, and IBM.
I really don't miss those good old days. All the dip switches and jumpers required for 286/386/486. Things are so much easier now. If it fits, it's probably compatible. Plug it in, turn it on. If it boots, you have a winner. :)
Only for you people using a GUI. Real men read Slashdot from a text console with lynx. Insane people read it with telnet and a script to parse the HTML for text mode viewing. I hear even RMS has started using graphical web browsers on occasion, so I guess that trick may work on him now. :)
The spec may say that there should be at least 64K available, but that doesn't mean that it is. That is available for something to write into, so if the UEFI already writes something there, 36K or less could fill it.
It actually seems to be a forewarning of future problems. 28K have already been used up by something, it's already 44% through its life. If it's a fairly new machine, that doesn't look so good for it's longevity. Since I don't have a problem machine in front of me (and I'm glad I don't), I can't really even hope to look in there and see what's wasting the space.
I've been fine with my phones for years. Recently I've been playing Ingress on my HTC EVO Design 4g. That can suck up a battery pretty quick. Even on a 2.1A charger it doesn't keep up all that well. After an hour or two, it starts complaining. I found replacement batteries for about $5/ea on Amazon. It's much easier to swap batteries, than to sit at a portal for 1/2 hour waiting for the battery to charged enough to run the game for a while. The car charger isn't all that useful when walking around to resonators, or in a high density area.
Wasn't there a practice run done? Really, if you're responsible for a multi-billion dollar event, it might be a good idea to fire everything up a few times and make sure it behaves as intended.
My only thought was, "The power went out during the Superbowl? I'm surprised I haven't heard more bitching".
That was about it. Although there are apparently millions of Americans who care, there are also millions of Americans would don't.
I just introduced an Intel fan to the wonders of AMD. He just knew that he'd always been told "Use Intel". I told him about my home machine. An air cooled AMD FX-8320 @4.01Ghz w/ 16GB RAM an a AMD 7770 w/ 1GB GDDR5. Every game I play, I crank all the settings all the way up, and the frame rate and quality is great.
I gave him some spare parts for his kids. Phenom II x6 1110T, motherboard, and a stack of RAM that he got 8GB to work together with, and a couple ATI 55xx video cards. He got the standard used parts disclaimer, "It all worked when I took it out, no guarantees that they do now." Not bad for a total of $0.
We spent some time comparing the Intel and AMD current pricing, and he didn't see any reason to use Intel any more.
Someone will reply, saying some benchmark says a comparable Intel is faster. Someone else will show a different benchmark says AMD is faster. For the price, I don't care, they just work, work well, and with the savings I don't mind upgrading again in 6 months. With the numbers we found that day, he can upgrade about 4 times and still come out under the Intel pricing.
I was confused by it having both an 8-track player *AND* CD changer. I guess they were basing their design to compete with this.
It's nice that they included 4 screens for the pilot to watch DVDs on. That's almost better than my flight sim setup at home.
Is it just me, or are all the buttons and switches on the right side of the seat just a big sticker?
I think you missed the part of...
Anyone can sue anyone else, at any time, for anything.
Here, one of the morning radio show hosts spent two weeks in court because another morning radio show host was offended that there were jokes made about him.
Two weeks, and a metric fucktonne of money spent by both sides, so the jury could decide in just a few minutes that the accuser was a whiny bitch.
I paraphrase that decision, of course. It was something like 47 items of the lawsuit, each decided as "as you kidding, we're only getting paid $15/day for this."
Not to nitpick but...
The US population is roughly 314,000,000.
Mexico's population is roughly 112,000,000
And if it were 3% to 6%, it would only be 25,560,000, or less than the population of California.
According to Wikipedia, the US interest in bioweapons started around 1918. They've been used on and off throughout history
Being prepared for such a threat isn't such a bad idea. We've gone far beyond that.
Interesting idea, but ... what?
Why would I mess with something so slow? I have 32Ghz (4Ghz * 8 cores).
As for the bunnies, we don't have quite that many here. We've been burning them to keep the steam engines running.
No, but it's "about midnight" somewhere. :)
I've seen that too. Mostly with fairly open hosting machines. Like, letting anyone sign up for free or low cost hosting. I saw a lot of them that were built for one platform (usually Redhat), where the libraries didn't quite line up with the running system.
At one place, I was collecting them. The script kiddie would put their SSH server on a high port. It worked great, except they couldn't get root with it, and they couldn't get to the daemon through the firewalls. It was rather entertaining.
I hated the free hosting servers. They were constantly trying to do bad things. They never succeeded, but I had to go prune those accounts on a regular basis. The worst were people trying to host anime porn on our servers, and link it from message boards in east Asia. I was tempted to block all access from east Asia, except we did have a lot of paying customers over there.
Aw, I don't know why you were modded troll. That's funny. :)
And only ultra secure because it would work for a few days, and then hang, refusing all access. :)
I was asked to clean some exploited servers in the wild that had compromised SSH binaries in them. This was about 10 years or so ago, so this is really a not current news story.
Thankfully most script kiddies are exactly that, and their script left the source on the machine for me to review. Why? I guess to compile on the machine to make sure it used the local libraries. They generally didn't have passwords hard coded though, they used SSH keys. The passwords they stole were usually stored locally in a file, and sent to somewhere in eastern Europe or Asia. I have no idea if that was by the script kiddie design or the person who rolled it up. It's a pretty slick trick though. You get the script kiddies to gather intel from compromised machines, and feed it back to you. Now you have access to every machine the script kiddies compromised.
The funny part about most of the cleanups was, the version of SSH they put on was newer than the remotely exploitable version they got in with.
Yup. There are actually several reasonably priced hosting services in Iceland. I was shopping for international homes for some of my data, until I thought about it and none of my data is worth spending money to hide. :) Iceland was pretty high on the list though.
Well, if we didn't say it, they'd all make their passwords "password", their own first name, or some other amazingly simple word.
They always glaze over when you try to explain strong passwords. No matter what you tell them, you can always sit down at their desk and say "what's your password?", just to find out it's "Password1" or "1234567A"
But you do realize that there are plenty of resume fluffed "coders" who would fail it.
There are languages that I was proficient in, that I haven't touched in years. I'm honest on my resume, things that I've forgotten, I take off before I start sending the resumes out. Even things I haven't touched in more than a couple years get dropped.
A lot of people keep everything they've ever known on their resume. For some, that's still a pretty short list. I've asked candidates about some of their experience, to find out that they barely touched it years before, and wouldn't know how to begin. Some just list skills to match the position advertisement, and assume they can get the company to pay for training later.
I guess it would prune out those who would take 2 hours to print "Hello World".
Oh my god, you can't delete code! It worked for us in 1998, and it's still working on our circa 1998 machines. What the hell are you thinking?!
Kidding aside, I comment and date old code, and add new code. It's not only there for restoration purposes (ya, ya, version control and stuff are there too), but if someone gets a new great idea on adding new code, they may find exactly that has already been removed with good reason.
When it's my own code that I maintain with no one else, I ditch the old commented code after about a year. Sometimes it sits there for longer, because it was actually good code that didn't suit that particular purpose.
I have one chunk of code in particular that won't get ditched for a longtime. It's a HTML filter, that takes all kinds of Microsoft specific characters and converts them into HTML friendly characters. I did it up better with a much smaller chunk of code, that can do a lot more, but occasionally I reference those old bits.