So what, good PCI implementations have multiple bus's, for instance my HP DL585 has two PCI-X 133 slots, each one is on a dedicated PCI bus, it also has six PCI-X slots on three more bus's. In total there are 8 PCI bus's in the system to deal with internal connections to the built in peripherals.
Which is why you need MINIMUM framerate numbers, not average. In NWNW2 I get around 40fps with fairly minimal settings, but in difficult scenes I bog down as low as 8fps and average around 11fps, to me that is unplayable.
Actually if they are using MPEG4 then it's not too bad. Typical MPEG4 movie rips from DVD are around 700MB for 90 minute movies, so they are shortchanging the bitrate a tad, but not so much as to make the film unwatchable. My guess is they are dropping the audio quality to get to that lower bitrate. This sucks for me because I just bought a nice surround sound system and this is probably low quality stereo sound, guess I'll have to wait for the next version =)
From the research I did last night they all blow. I researched units from the usual suspects (DLink, Linksys, Buffalo Tech, etc) and they all had lockup problems and most couldn't even handle the limited number of formats that they claimed to support. For the slashdot crowd I still think the answer is a HTPC in a nice case. Use a low power athlon64 x2 or core2 duo and it won't kill you on electricity usage.
The good thing about doing a parallel install is if you can use identically (or near so) speced equipment you get a twofor, you get your new IDF and you get equipment to use in your DR planning. Remember DR isn't just about offsite moves, it can also be about what do you do if your critical equipment dies.
That's not entirely true. There is a Linux module to limit max forks per second. There are also patches to the Out Of Memory task killer to make it walk the process tree and attempt to kill the oldest ancestor of the nuisance process. There are ways, even in a single user scenario, to limit the damage of things like fork bombs and other resource depleters.
The 7200.8 does appear to have issues. The Storagereview reliability database has it ranked in the 31st percentile reliability-wise, although the limited number of entries (only 220) might be skewing the results a bit. The 7200.7 on the other hand is in the 89th percentile with nearly 800 entries. The majority of Segate products listed in the database with a statistically significant number of entries are ranked in the 90+ percentile for reliability. Personally I have installed about 300 Segate HDD's in servers in the last 6 months and have only had one failure, but these are enterprise SCSI and FibreChannel drives.
They do, however if they have different ideas of what the offset should be for the timezone then things like kerberos tickets don't work. This is because the time is sent as UMT, if you manually change the clock to display the correct time then you effectively change the local idea of UMT because the computer backcalculates the UMT time from the displayed time and the offset from your timezone location. This is a big deal. In fact this is one of my biggest projects for Q1-07, and all because someone thinks they are going to save some minuscule amount of resources by changing when daylight shines relative to when people are awake which has never been shown to be the case.
Correct. The first time I thought it was a cookie or something, so I posted anonymously from my wife's pc which never goes to slashdot but which sits behind my nat'ing router, and my moderation still went poof.
A friend of mine had a similar incident. He worked in the datacenter of a large bank. When the telco came to run new fibre into the building they put the fibre in the conduit, stuck in a a plug and blew it in. Only problem was they hadn't checked the conduit as per procedure. The conduit went under the subbasement and was full of water. They had thousands of gallons of water pushed into the under floor space, to the point where tiles floated. The amazing thing is nothing major shorted out, including a large chassis based Cisco switch (think 4500 series) which was mostly under the tile floor, luckily the power supplies were on the top! Needless to say they implemented their DR strategy that day =)
Wonder if that was before Cisco offered extended range products. These days you can get gear from Cisco that will survive in the Sahara in a NEMA3(sealed) outdoor enclosure.
That's weird because UL rating and the national electric code always allow a higher class device or fixture the be substituted for a lower class one (with the obvious exception of breakers and such, I'm talking about things like plenum rated stuff can be used in normal wiring situations)
Pricey? Lowes has a two bulb enclosure (admittedly ugly, but that has nothing to do with the electronics) for only $21.48. There's really no reason NOT to use T8's where they are appropriate. Personally I used em in my garage and would have used em in the basement but the previous owner hung the ceiling too low.
Actually neither works with current Slashcode, if a post is made from the same IP (possibly in a set period of time, haven't dug into it) then the moderation is removed. Sucks if you are at a big company with a proxy server, but it prevents the anonymous abuse hole you are talking about.
FoxIt is definitely nice. In fact it's so nice I haven't even bothered to install Adobe's bloatware on my newest PC. Seriously thinking about buying a personal license to get to Firefox plugin.
Actually they thought that the solar cells would be clouded over by the Martian dust and that the cooler nights during the Martian fall would cause the batteries to be drained by the heaters. For some still unknown reason the Martian winds were more powerful than expected and so the dust was cleared from the cells at a rate much greater than expected. This allowed them to survive through the Martian winter and consequently greatly exceed even their most optimistic predictions.
I don't know, I would think on a per line cost the lines in COBOL and other old code that used a two digit year for storing dates would be freaking expensive. The Y2K stuff cost the customers of the computer industry untold billions and I bet the total number of affected lines was in the thousands.
Actually that's kind of what they did when they had a problem with a bug filling the flash memory area of Spirit during the trip to mars, they set a register and booted without mounting the flash drive then cleaned up the drive to resume normal operations. This article talks about the way they fixed that problem. Another interesting thing I found in this article is that the uplink to the rovers while they were on their ways to Mars was only 2Kbit/s! Talk about limited bandwidth, speeds here at home haven't been that slow since 1987 with the introduction of the Hayes 96 with 9600 baud.
VxWorks is an amazing family of embedded OS's. I personally saw a lot of it when I supported the guys at Cisco/Aironet wireless before they switched over to IOS for their AP's and bridges. There was never a time that I am aware of that a problem was traced to a VxWorks bug. In fact the only reboot (not lockup!) problem that I am aware of with the VxWorks based AP's was due to memory exhaustion of the MAC table in a flat class A network. That client got a custom fix that involved the changing of one variable, viva object orientation and good coding practices! The reason that it rebooted was that the AP code stopped responding and and a hardware watchdog tripped and the unit self rebooted. Good embedded systems are very cool, too bad so few are open to study.
Nope, not completely unrecoverable, just difficult. Using an SEM anything written to a modern (mid 90's or later) HDD can be recovered even after many passes with "secure" delete patterns. Peter Gutmann wrote about the problem years ago. Although he doesn't specifically mention flash ram I would imagine the problems facing DRAM and SRAM would be even more prevalent with flash due to wear leveling and other protection techniques meant to keep data safe on the flash device. When the data really needs to be secure physical destruction is the only way to go =)
While SBC might have been the purchasing party on paper I can guarantee you that internal politics meant the merger was really controlled by the AT&T side of the fence. This was bad for me at the time as our great SBC rep was essentially pushed out.
1080i MPEG4 streams only take ~9Mbit/s. I can get 6Mbit/s from my cable provider today for $65/month. I would expect 9Mbit/s for the same price in the next year or two, and that to be the base rate in another couple years as cable, WiMax and FIOS compete. The problem for those who want to lock content in is that there are so many technologies wanting to provide you with bandwidth that eventually you will have more than enough bandwidth to do whatever you need. Artificial speed limits imposed by Tier-1 ISP's was the only thing that was going to stop this inevitability, and this agreement by AT&T basically stops that idea.
Slashdot Mirror
The LPT/USB port isn't usually disabled, so just hook up a cable and print =)
So what, good PCI implementations have multiple bus's, for instance my HP DL585 has two PCI-X 133 slots, each one is on a dedicated PCI bus, it also has six PCI-X slots on three more bus's. In total there are 8 PCI bus's in the system to deal with internal connections to the built in peripherals.
Which is why you need MINIMUM framerate numbers, not average. In NWNW2 I get around 40fps with fairly minimal settings, but in difficult scenes I bog down as low as 8fps and average around 11fps, to me that is unplayable.
Actually if they are using MPEG4 then it's not too bad. Typical MPEG4 movie rips from DVD are around 700MB for 90 minute movies, so they are shortchanging the bitrate a tad, but not so much as to make the film unwatchable. My guess is they are dropping the audio quality to get to that lower bitrate. This sucks for me because I just bought a nice surround sound system and this is probably low quality stereo sound, guess I'll have to wait for the next version =)
From the research I did last night they all blow. I researched units from the usual suspects (DLink, Linksys, Buffalo Tech, etc) and they all had lockup problems and most couldn't even handle the limited number of formats that they claimed to support. For the slashdot crowd I still think the answer is a HTPC in a nice case. Use a low power athlon64 x2 or core2 duo and it won't kill you on electricity usage.
The good thing about doing a parallel install is if you can use identically (or near so) speced equipment you get a twofor, you get your new IDF and you get equipment to use in your DR planning. Remember DR isn't just about offsite moves, it can also be about what do you do if your critical equipment dies.
That's not entirely true. There is a Linux module to limit max forks per second. There are also patches to the Out Of Memory task killer to make it walk the process tree and attempt to kill the oldest ancestor of the nuisance process. There are ways, even in a single user scenario, to limit the damage of things like fork bombs and other resource depleters.
The 7200.8 does appear to have issues. The Storagereview reliability database has it ranked in the 31st percentile reliability-wise, although the limited number of entries (only 220) might be skewing the results a bit. The 7200.7 on the other hand is in the 89th percentile with nearly 800 entries. The majority of Segate products listed in the database with a statistically significant number of entries are ranked in the 90+ percentile for reliability. Personally I have installed about 300 Segate HDD's in servers in the last 6 months and have only had one failure, but these are enterprise SCSI and FibreChannel drives.
They do, however if they have different ideas of what the offset should be for the timezone then things like kerberos tickets don't work. This is because the time is sent as UMT, if you manually change the clock to display the correct time then you effectively change the local idea of UMT because the computer backcalculates the UMT time from the displayed time and the offset from your timezone location. This is a big deal. In fact this is one of my biggest projects for Q1-07, and all because someone thinks they are going to save some minuscule amount of resources by changing when daylight shines relative to when people are awake which has never been shown to be the case.
Correct. The first time I thought it was a cookie or something, so I posted anonymously from my wife's pc which never goes to slashdot but which sits behind my nat'ing router, and my moderation still went poof.
Not sure how stable it is but there's gnash from GNU.
A friend of mine had a similar incident. He worked in the datacenter of a large bank. When the telco came to run new fibre into the building they put the fibre in the conduit, stuck in a a plug and blew it in. Only problem was they hadn't checked the conduit as per procedure. The conduit went under the subbasement and was full of water. They had thousands of gallons of water pushed into the under floor space, to the point where tiles floated. The amazing thing is nothing major shorted out, including a large chassis based Cisco switch (think 4500 series) which was mostly under the tile floor, luckily the power supplies were on the top! Needless to say they implemented their DR strategy that day =)
Wonder if that was before Cisco offered extended range products. These days you can get gear from Cisco that will survive in the Sahara in a NEMA3(sealed) outdoor enclosure.
That's weird because UL rating and the national electric code always allow a higher class device or fixture the be substituted for a lower class one (with the obvious exception of breakers and such, I'm talking about things like plenum rated stuff can be used in normal wiring situations)
Pricey? Lowes has a two bulb enclosure (admittedly ugly, but that has nothing to do with the electronics) for only $21.48. There's really no reason NOT to use T8's where they are appropriate. Personally I used em in my garage and would have used em in the basement but the previous owner hung the ceiling too low.
Actually neither works with current Slashcode, if a post is made from the same IP (possibly in a set period of time, haven't dug into it) then the moderation is removed. Sucks if you are at a big company with a proxy server, but it prevents the anonymous abuse hole you are talking about.
FoxIt is definitely nice. In fact it's so nice I haven't even bothered to install Adobe's bloatware on my newest PC. Seriously thinking about buying a personal license to get to Firefox plugin.
Actually they thought that the solar cells would be clouded over by the Martian dust and that the cooler nights during the Martian fall would cause the batteries to be drained by the heaters. For some still unknown reason the Martian winds were more powerful than expected and so the dust was cleared from the cells at a rate much greater than expected. This allowed them to survive through the Martian winter and consequently greatly exceed even their most optimistic predictions.
I don't know, I would think on a per line cost the lines in COBOL and other old code that used a two digit year for storing dates would be freaking expensive. The Y2K stuff cost the customers of the computer industry untold billions and I bet the total number of affected lines was in the thousands.
Actually that's kind of what they did when they had a problem with a bug filling the flash memory area of Spirit during the trip to mars, they set a register and booted without mounting the flash drive then cleaned up the drive to resume normal operations. This article talks about the way they fixed that problem. Another interesting thing I found in this article is that the uplink to the rovers while they were on their ways to Mars was only 2Kbit/s! Talk about limited bandwidth, speeds here at home haven't been that slow since 1987 with the introduction of the Hayes 96 with 9600 baud.
VxWorks is an amazing family of embedded OS's. I personally saw a lot of it when I supported the guys at Cisco/Aironet wireless before they switched over to IOS for their AP's and bridges. There was never a time that I am aware of that a problem was traced to a VxWorks bug. In fact the only reboot (not lockup!) problem that I am aware of with the VxWorks based AP's was due to memory exhaustion of the MAC table in a flat class A network. That client got a custom fix that involved the changing of one variable, viva object orientation and good coding practices! The reason that it rebooted was that the AP code stopped responding and and a hardware watchdog tripped and the unit self rebooted. Good embedded systems are very cool, too bad so few are open to study.
Since the NSA has a patent on a technique I think it's a little more than theory =)
Nope, not completely unrecoverable, just difficult. Using an SEM anything written to a modern (mid 90's or later) HDD can be recovered even after many passes with "secure" delete patterns. Peter Gutmann wrote about the problem years ago. Although he doesn't specifically mention flash ram I would imagine the problems facing DRAM and SRAM would be even more prevalent with flash due to wear leveling and other protection techniques meant to keep data safe on the flash device. When the data really needs to be secure physical destruction is the only way to go =)
While SBC might have been the purchasing party on paper I can guarantee you that internal politics meant the merger was really controlled by the AT&T side of the fence. This was bad for me at the time as our great SBC rep was essentially pushed out.
1080i MPEG4 streams only take ~9Mbit/s. I can get 6Mbit/s from my cable provider today for $65/month. I would expect 9Mbit/s for the same price in the next year or two, and that to be the base rate in another couple years as cable, WiMax and FIOS compete. The problem for those who want to lock content in is that there are so many technologies wanting to provide you with bandwidth that eventually you will have more than enough bandwidth to do whatever you need. Artificial speed limits imposed by Tier-1 ISP's was the only thing that was going to stop this inevitability, and this agreement by AT&T basically stops that idea.