One challenge is knowing how many VA your servers draw, which varies depending on how much RAM they have, how many disk drives, and even how busy the servers are. There is no boilerplate information that can help you with this. To spec your UPS's properly, you need to connect a power meter to each group of servers and monitor the power consumption under typical load.
Once you have an accurate idea of the load, you can look at UPS manufacturer's data to determine how much runtime to expect. For example, if a 2KVA UPS is rated for 10 minutes with a particular battery, you should get 20 minutes if your load is 1KVA.
The first time I came up against a TDSS infection it was incredibly hard to deal with. Then I learned a little trick to disable the thing:
Start Device Manager
Click View, Show Hidden Devices
Scroll down to Non-Plug and Play Drivers
Click + at left
Right-click on TDSSserv.sys or TDSSxyz.sys where xyz are random characters,
clbdriver.sys, gaopdxserv.sys, seneka or seneka.sys
This information is from about 1 year ago, however. I haven't looked at any current variants, so they might be quite different. Nevertheless, the technique of installing as a device driver was novel to me at the time, and may still be used. Just as with autorun entries, check your Non-Plug and Play devices. If you see something with a name that looks randomly generated or otherwise suspicious, you might want to disable it.
From a privacy perspective, how is this worse than the dozens of common applications that already "phone home" all the time to check for updates, etc?
Since I'm running a legitimate copy of Windows, unless it gets flagged incorrectly as non-genuine, I'll neither notice or care that it runs this little check every three months.
If you have an OEM version of Windows, then replacing the motherboard requires a new licence. This is explained in the OEM
System Builder Licencing FAQ, which I quote below:
Generally, an end user can upgrade or replace all of the hardware components on a computer—except the motherboard—and still retain the license for the original Microsoft OEM operating system software. If the motherboard is upgraded or replaced for reasons other than a defect, then a new computer has been created. Microsoft OEM operating system software cannot be transferred to the new computer, and the license of new operating system software is required.
If the motherboard is replaced because it is defective, you do not need to acquire a new operating system license for the PC as long as the replacement motherboard is the same make/model or the same manufacturer's replacement/equivalent, as defined by the manufacturer's warranty.
Any scanner that returned over 9,000 false positives is clearly a joke. So you ignore it and run a better scanner.
I've dealt with scans for credit card purposes and for the most part I thought they were pretty good. Yes, there was the occasional false positive. So you provide some explanatory information and then you get passed. False positives are preferable to false negatives.
It's simply unrealistic to expect these scans to yield perfect results. Despite that, I believe they're useful.
No vulnerability scanner will ever detect 100% of the vulnerabilities possible. They're still very useful, however, because no website is going to have 100% of all the vulnerabilities possible.
Think of it another way. If your website has only 1 vulnerability and the scanner detects it, then it's 100% effective.
If your website has only 1 vulnerability and no scanner detects, score 1 for the bad guys. The cat and mouse game continues.
CPU hogging programs can be a real pain, especially on a multi-user system. I know of businesses that run keyboard polling applications on a Terminal Server, for example. Each instance easily pin a core at 100%.
If you ever run into a problem like this (on Windows), check out ThreadMaster
I was merely pointing out a redundancy. I can see your 4-digit number as well, so it's understandable that you'd like to think everyone is jealous. Sorry to disappoint you.
A low number carries status, but the fact that someone got in early is no guarantee of their sagacity. I judge comments on their content, not on the pedigree of the commenter.
To put in another way, one doesn't need a low number to post a good comment, one only needs a brain.
A correct algorithm is not enough to ensure a correct result.
The fact is that binary digits in RAM can (and do) spontaneously change from 0 to 1 and vice-versa. A few possible causes are listed here. The likelihood of such errors increases with the number of digits involved.
There is no mention of whether Bellard used ECC
RAM.
Reading OMNI always felt a bit like an exercise in wishful thinking. It was like reading car magazines that feature incredible prototypes. Yes they're awesome, but you're never going to see one in your lifetime. OMNI was about what was possible, not what was actually happening.
To read about real advances, I preferred Scientific American, especially back when Martin Gardner wrote for them. Prior to that, I never used the terms "recreational" and "mathematics" in the same sentence.
On a side note, there was a fantastic 3D illusion created as a tribute to Gardner. It's still available for download here.
For cripes sake. Does every comment here have to trigger an anti-MS response? He's not "defending" anything, and made no mention of XP in his post. The example was that manufacturers may choose not to implement a new technology when the old one is still available and working. IPV6 is a perfect example of this.
I have yet to see a single OEM windows install boot up with dozens of error messages because it is just trying to load drivers for every piece of hardware in the windows driver database for instance.
I've restored factory images on Lenovo laptops and found devices with no driver installed.
As for the issue about erroneous error messages, the coders are either lazy or incompetent. Period. Every bit of information displayed should be both useful and correct. There used to be a paradigm in Unix that no information should be displayed unless necessary. For example, when I type 'rm foo', no feedback is returned unless the operation fails. It would be unnecessary to report success, and completely f*cked to report an error if none occurred. For an example of things done right, try OpenBSD.
The outages refer to e-mail. Users can still make an old-fashioned phone call.
Using any e-mail system for time-sensitive communication demonstrates a lack of understanding about how e-mail works. Most of the time it's fast and dependable, but problems can always occur along the way that will cause messages to be delayed. Most MTA's in default configuration will retry for days to deliver a message if the receiving server is not responding.
If you need to contact someone urgently, e-mail is a poor choice.
I used to have a friend who could spot the two little circles in the top right of a movie in the theater telling the projectionist to change the reel. Once he saw them the movies were never the same again.
Yep. Years ago I started noticing those two flashes in the top right corner of the movie screen. I've never stopped noticing them. The people sitting with me are oblivious.
You started this thread by asserting that DNS caching on your router lessens the privacy issues associated with DNS. I disagreed with that assertion.
I'm not saying anything about paranoia, slippery slopes, root servers, or who already has access to private information. I'm saying that DNS caching does practically nothing to enhance privacy. Period. This is a technical fact, not an opinion.
I was actually wondering if they obtained those IP addresses (8.8.8.8 and 8.8.4.4) specifically to appeal to Chinese people.
The number 8 is considered very lucky in Chinese culture. The appeal of the number 8 is noticeable here in Vancouver, where we have a large Chinese community. It appears on many personalized licence plates, for example, and I've heard Realtors claim that houses with 8's in the address generate more interest from Chinese buyers.
Having your own DNS cache simply means that Google will only see unique queries from you. Even if your cache never expired any entries, they would still have a record of every single site you visit. They simply wouldn't know how many times you visited.
Do you remember back in the days of 386 computers, when they had a "Turbo" button on the case? I can remember having to turn off Turbo mode to play some games that otherwise ran impossibly fast.
Many cases also had a two display that changed from "16" to "8" (or something similar) when the Turbo button was toggled. This was supposed to represent a change in the clock speed, but what really happened was that cache memory was disabled to make the system run slow.
My kids think it's hilarious that we used to have a button to make the computer run slow.
Slashdot Mirror
One challenge is knowing how many VA your servers draw, which varies depending on how much RAM they have, how many disk drives, and even how busy the servers are. There is no boilerplate information that can help you with this. To spec your UPS's properly, you need to connect a power meter to each group of servers and monitor the power consumption under typical load.
Once you have an accurate idea of the load, you can look at UPS manufacturer's data to determine how much runtime to expect. For example, if a 2KVA UPS is rated for 10 minutes with a particular battery, you should get 20 minutes if your load is 1KVA.
Oops, I didn't paste the final steps:
The first time I came up against a TDSS infection it was incredibly hard to deal with. Then I learned a little trick to disable the thing:
This information is from about 1 year ago, however. I haven't looked at any current variants, so they might be quite different. Nevertheless, the technique of installing as a device driver was novel to me at the time, and may still be used. Just as with autorun entries, check your Non-Plug and Play devices. If you see something with a name that looks randomly generated or otherwise suspicious, you might want to disable it.
From a privacy perspective, how is this worse than the dozens of common applications that already "phone home" all the time to check for updates, etc?
Since I'm running a legitimate copy of Windows, unless it gets flagged incorrectly as non-genuine, I'll neither notice or care that it runs this little check every three months.
If you have an OEM version of Windows, then replacing the motherboard requires a new licence. This is explained in the OEM System Builder Licencing FAQ, which I quote below:
Generally, an end user can upgrade or replace all of the hardware components on a computer—except the motherboard—and still retain the license for the original Microsoft OEM operating system software. If the motherboard is upgraded or replaced for reasons other than a defect, then a new computer has been created. Microsoft OEM operating system software cannot be transferred to the new computer, and the license of new operating system software is required.
If the motherboard is replaced because it is defective, you do not need to acquire a new operating system license for the PC as long as the replacement motherboard is the same make/model or the same manufacturer's replacement/equivalent, as defined by the manufacturer's warranty.
Any scanner that returned over 9,000 false positives is clearly a joke. So you ignore it and run a better scanner.
I've dealt with scans for credit card purposes and for the most part I thought they were pretty good. Yes, there was the occasional false positive. So you provide some explanatory information and then you get passed. False positives are preferable to false negatives.
It's simply unrealistic to expect these scans to yield perfect results. Despite that, I believe they're useful.
No vulnerability scanner will ever detect 100% of the vulnerabilities possible. They're still very useful, however, because no website is going to have 100% of all the vulnerabilities possible.
Think of it another way. If your website has only 1 vulnerability and the scanner detects it, then it's 100% effective.
If your website has only 1 vulnerability and no scanner detects, score 1 for the bad guys. The cat and mouse game continues.
CPU hogging programs can be a real pain, especially on a multi-user system. I know of businesses that run keyboard polling applications on a Terminal Server, for example. Each instance easily pin a core at 100%.
If you ever run into a problem like this (on Windows), check out ThreadMaster
// You sound jealous...
I was merely pointing out a redundancy. I can see your 4-digit number as well, so it's understandable that you'd like to think everyone is jealous. Sorry to disappoint you.
A low number carries status, but the fact that someone got in early is no guarantee of their sagacity. I judge comments on their content, not on the pedigree of the commenter.
To put in another way, one doesn't need a low number to post a good comment, one only needs a brain.
You know, you don't need a sig that announces "Slashdot reader since 1997". We can all see the number beside you nickname.
"Bandwidth" is a measure of throughput - the rate at which you can push data through your pipe. Nobody has unlimited bandwidth.
FTA, the fraction of women who find him attractive is 1 in 20.
A correct algorithm is not enough to ensure a correct result.
The fact is that binary digits in RAM can (and do) spontaneously change from 0 to 1 and vice-versa. A few possible causes are listed here. The likelihood of such errors increases with the number of digits involved.
There is no mention of whether Bellard used ECC RAM.
Reading OMNI always felt a bit like an exercise in wishful thinking. It was like reading car magazines that feature incredible prototypes. Yes they're awesome, but you're never going to see one in your lifetime. OMNI was about what was possible, not what was actually happening.
To read about real advances, I preferred Scientific American, especially back when Martin Gardner wrote for them. Prior to that, I never used the terms "recreational" and "mathematics" in the same sentence.
On a side note, there was a fantastic 3D illusion created as a tribute to Gardner. It's still available for download here.
Thanks for the comparison.
for the inevitable comparisons to Linux. And yes, we've heard of embedded Linux.
For cripes sake. Does every comment here have to trigger an anti-MS response? He's not "defending" anything, and made no mention of XP in his post. The example was that manufacturers may choose not to implement a new technology when the old one is still available and working. IPV6 is a perfect example of this.
I have yet to see a single OEM windows install boot up with dozens of error messages because it is just trying to load drivers for every piece of hardware in the windows driver database for instance.
I've restored factory images on Lenovo laptops and found devices with no driver installed.
As for the issue about erroneous error messages, the coders are either lazy or incompetent. Period. Every bit of information displayed should be both useful and correct. There used to be a paradigm in Unix that no information should be displayed unless necessary. For example, when I type 'rm foo', no feedback is returned unless the operation fails. It would be unnecessary to report success, and completely f*cked to report an error if none occurred. For an example of things done right, try OpenBSD.
The outages refer to e-mail. Users can still make an old-fashioned phone call.
Using any e-mail system for time-sensitive communication demonstrates a lack of understanding about how e-mail works. Most of the time it's fast and dependable, but problems can always occur along the way that will cause messages to be delayed. Most MTA's in default configuration will retry for days to deliver a message if the receiving server is not responding.
If you need to contact someone urgently, e-mail is a poor choice.
I used to have a friend who could spot the two little circles in the top right of a movie in the theater telling the projectionist to change the reel. Once he saw them the movies were never the same again.
Yep. Years ago I started noticing those two flashes in the top right corner of the movie screen. I've never stopped noticing them. The people sitting with me are oblivious.
You seem to be incapable of getting the point.
You started this thread by asserting that DNS caching on your router lessens the privacy issues associated with DNS. I disagreed with that assertion.
I'm not saying anything about paranoia, slippery slopes, root servers, or who already has access to private information. I'm saying that DNS caching does practically nothing to enhance privacy. Period. This is a technical fact, not an opinion.
My point is, with exception of some limited type in traffic, Google already has a lot of this info.
This has nothing to do with your original assertion that DNS caching limits privacy problems.
So, if you are really concerned about privacy and Google (I do believe this is an issue), you have to stop using Google altogether.
That would not be sufficient. You would also have to avoid using Google Public DNS, with or without caching.
I was actually wondering if they obtained those IP addresses (8.8.8.8 and 8.8.4.4) specifically to appeal to Chinese people.
The number 8 is considered very lucky in Chinese culture. The appeal of the number 8 is noticeable here in Vancouver, where we have a large Chinese community. It appears on many personalized licence plates, for example, and I've heard Realtors claim that houses with 8's in the address generate more interest from Chinese buyers.
I do not see the privacy issues
Having your own DNS cache simply means that Google will only see unique queries from you. Even if your cache never expired any entries, they would still have a record of every single site you visit. They simply wouldn't know how many times you visited.
Do you see the privacy issues now?
Do you remember back in the days of 386 computers, when they had a "Turbo" button on the case? I can remember having to turn off Turbo mode to play some games that otherwise ran impossibly fast.
Many cases also had a two display that changed from "16" to "8" (or something similar) when the Turbo button was toggled. This was supposed to represent a change in the clock speed, but what really happened was that cache memory was disabled to make the system run slow.
My kids think it's hilarious that we used to have a button to make the computer run slow.