For a long time back in the day people wanted to stay at 5 volts to preserve compatibility, so everyone just kept putting it into going faster.
I don't think preserving compatibility had much to do with concentrating on making things go faster. If you wanted to make a low voltage chip that was compatible with 5v power and TTL data then that would be fairly trivial (onboard voltage regulator and some TTL switching at the edges). The simple fact is that for a long time there was pretty much no need for trying to make things consume less power - no one cared about power consumption. Eventually we got to a point where we *had* to care about power consumption because there was just no sane way to cool the chips down (many transistors switching a relatively high voltage in parallel at very high speeds == very high power consumption == very high heat output). These days, we have more and more mobile devices with relatively tiny batteries, so power consumption is becoming an even more important factor.
Frankly, I'm not sure there is a lot of point in going much faster for most people - why do you need an 8 core 10GHz machine to word process and browse the web (which is what most people use their computers for)? Ok, I guess the horrifically inefficient Flash video players might want that.:) The people who are going to want processors a lot faster than what we have today are people doing large number crunching projects, and a lot of those can be parallelised, and we can already do many cores. I'm a professional software developer and my main workstation is now 8 years old (it has had memory and hard drive upgraded several times over the years, but the CPU is the same old one) and amazingly I don't really feel the need to upgrade it. 10 Years ago, if you had told me a workstation would last at least 8 years I would've laughed. Then again, 10 years ago if you had told me that my phone would have a 528MHz ARM, 8 gig of non-volatile storage (upgradable) and a battery life that isn't measured in seconds, I wouldn't have believed you either:).
3D chip layouts are part of this roadmap. This kind of roadmap isn't really intended to say what their process will be, however. It's intended to give numbers to their core design teams about how many transistors they will be able to play with, what the latencies will be, and so on.
I'm unconvinced - the latency characteristics of a 3D architecture are going to be vastly different to those you'll find on any 2D chip, no matter how small you make the features.
That said, I'm assuming Intel is basing this roadmap on some data with at least _some_ substance, rather than just blindly assuming we can keep pushing Moore's law out forever. I'd be interested to know how much of this is based on existing research and how much is BS.
If they go badly wrong, you get something like the Pentium 4.
So I'm going to need a bigger nuclear reactor in my laptop then?:)
what is 1,234? One thousand two hundred and thirty four, or one and two hundred and thirty four thousandths? Mixing the styles is certainly ambiguous at best unless you *always* include tenths in your numbers.
A contract works both ways. They agree to provide certain services and I agree to pay for them. If they don't provide those services that's their choice but I am under no obligation to continue paying.
Sadly the last time I tried to not pay an MNO for illegal charges I was told in no uncertain terms that they would trash my credit rating. Since I didn't have the time to take them to court over it I paid up (if it had been more than a couple of pounds they would've found themselves in the small claims court though).
The way the credit reference system works is completely wrong - the creditors do not have to get a CCJ against you in order to record a default on your credit history. You are assumed to be guilty and you then have to take them to court to prove your innocence.
Even more than that, information is in the public domain. You cannot copyright the fact that a particular train is supposed to arrive at a particular stop at a particular time.
You can't copyright facts, however there are database rights that apply. So whilst you can copy a single fact (since there is no copyright), you can't copy a large chunk of the database.
This sort of crazyness goes on with TV listings and post code databases too - the companies want to have their cake and eat it: the TV channels want people to know what shows are on but also want to be able to make money out of selling the listings, the post office wants everyone to use post codes but also wants to continue making huge amounts of money out of selling the database.
That and the fact that, for pretty much any phone style and available waterproofing technology, the waterproof phone is going to be some combination of larger/heavier/more expensive than the non-waterproof one. And, while everybody wishes their phone were waterproof once it is sitting in a puddle, most will go for the slimmer/cheaper/lighter one when they are in the shop.
It shouldn't take much to waterproof an iPhone, given that it has no buttons...
Old.. Probably around the 2002 era. It is one of the old monochrome ones.
As I understand it, the old "nitrogen filled" waterproff GPS units lose a lot of their waterproofness over the years as the nitrogen slowly leaks out.
The case is in 2 halves - a back and a front. The join between the two halves is sealed with tape and then the rubber band goes over the top of the tape. The problem is that the (electrical) buttons are under the tape and the rubber buttons moulded into the band just push them through the tape. This lead to the tape splitting around the buttons, so no longer waterproof. So it is really a bit of a design flaw and I'm pretty sure that any eTrex of the same design that has had much use is going to have the same problem.
It was in an AquaPac, but it seems that enough water was inside that (from handling the GPS with wet hands before the AquaPac was sealed) that the GPS drowned (I was using it while windsurfing in the sea, so it got drowned in salt water). I dismantled it, soaked the bits in deionised water, let it dry, and chucked in a sachet of silica gel when I put it all back together and re-sealed it with PVC tape. It all works except for an intermittent fault on the screen that can been cleared by hitting it, which I presume is caused by some salt that didn't get washed off.
Because Europe is a land where people enjoy having their actions and lives dictated to them under the guise of protecting themselves from themselves. Which for the record, is not possible with anything less than handcuffs, force fed tranquilizers, and 24 hour supervision. I'm so glad I'm the age I am in the country I'm in, knowing that very soon I will be dead and shortly after my country will end up just as FUCKED.
Yes, you're absolutely right - the police call round my house 4 times a day to feed me those tranquillisers...
If a company's product cannot work in the environments you plan to use it in, don't buy the product... and don't blame the company if their warranties are voided by using the device in that environment.
Well that very much depends on how the warranty is worded doesn't it? If the warranty says it won't cover a device that has ever been exposed to high humidities then fair enough (although I wouldn't be at all surprised if a court struck down the warranty clause as unreasonable). However, if the warranty says it will be voided by dunking it in liquid water, and your warranty claim gets rejected just because it was in a humid environment then that is a serious problem.
I'm despairing at the state of the cellphone industry at the moment - T-mobile and Carphone Warehouse have both basically told me that they are no longer selling the G1 (HTC Dream - under a year since it was released) because it has been superseded by the G2 (which looks positioned for a different audience to me). The guy in Carphone Warehouse justified this by saying the G2 was "more iPhone like" and thus "better" - I pointed out that if I wanted an iPhone I would get an iPhone, I'm buying an HTC Dream because it suits me better. I would have thought that it would be more sensible to sell a range of devices to suit everyone's needs instead of a million and one iPhone clones.
For at least 10 years the product life cycles have been far too short - they release a device prematurely, full of bugs, and before the bugs have been worked out they cease production and start on a new device which a whole new set of bugs. This is why I've decided not to buy a phone with a closed source OS again - the vendors don't care enough to stabilise the software so the users are the only people who are going to do it. With an open OS there's a chance that this might happen. For example, my current phone which I'm replacing is a 6 year old Sony Ericsson P900 - it was crap and buggy when I bought it but I've not seen anything in the past 6 years that I had any confidence of being better (the email client is so bad that it is completely unusable and the bluetooth stack tends to crash the whole phone a few times a day so you can't really get away with leaving bluetooth turned on).
Even cheap cell phones have submersion detectors these days to prevent people from turning in phones that got dropped into water.
If enough people drop their phones in water to warrant sticking sensors in to void the warranty claims, I would have thought that demonstrates a consumer demand for waterproof devices rather than a demand for warranty voiding sensors...
In any case, I think all the phones I've ever had have got wet one way or another (2 of them soaked in sea water more than once). They all survived surprisingly well, coming back to life after being dismantled, soaked in deionised water and a couple of days drying out. The only device I've drowned which hasn't done so well is my "waterproof, nitrogen filled" Garmin eTrex Venture GPS, which turned out to not be so waterproof - it has mostly recovered, but the screen goes crazy every so often (percussive maintenance fixes it) so I think I need to dismantle it and soak it again. Oh, and a cheap waterproof Casio watch which survived many windsurfing sessions only to fill with water when I washed the car.
Twitter isn't completely worthless. Like MySpace is serves a very good purpose - it keeps the idiots occupied on a very small chunk of the web so the rest of us can easily avoid them and get on with out lives.
Shh cities that are actually smart about travel are hard to find.
Though my personal favorite is to tearup a parking lot replace it with a parting garage with half the car slots. And add in a new office building or condo complex. It is like they don't expect people to travel.
Though iwish city streets were drivable by permit only. Without a permit you haveto park at large garages with regular mass transit to take you into the city.
Around here the EU have a habit of making development grants dependent on developments being "public transport friendly". Unfortunately, "public transport friendly" tends to mean encouraging people to use public transport by not providing anywhere near enough parking spaces... even if there happens to be no sane public transport to get there.
Compiz Fusion is an OpenGL compositing manager. If you don't have 3D acceleration, Compiz will run like crap.
Which is why I explicitly said "Compiz Fusion runs just fine on an Intel GPU" - you don't need your fancy super powerful nVidia or AMD GPU (with its lack of decent drivers) to do what most people care about, which is running the desktop.
And to be frank, most people probably don't use a compositing window manager anyway, so don't even care about that.
xfwm4, metacity
Since when did XFWM4 and Metashitty do compositing?
If there is a vulnerability with said character, then just using it would not be legitimate until the problem was fixed on the phone firmware.
I haven't seen anything saying what the character is (and more saying that the character being displayed is just a side effect of the crack, not actually the vulnerability). But, that aside, if a legitimate character affects a vulnerability on a *single device*, the service provider has no business breaking legitimate uses of that character by the majority of people (i.e. those that don't own an iphone).
As much as you may like to believe that there is no legitimate use for non-ASCII characters, you are wrong. I already get pissed off that there is no way to enter a "Å" character into my P900 (a bit of a pain since that character appears in my street address.).
Cleaning the character at the carrier could prevent problems spreading to the phone and be a "quick fix", but doesn't make it go away, the phone would need to release a patch eventually, then you can use your Unicode heart character (or whatever else char it is) in your text messages again.
By that mentality, all ISPs should block all web traffic every time a security hole in Internet Explorer is found. Blocking everyone from going about their business because a minority device has a bug is unacceptable, especially since the vendor was informed a month ago and has done nothing to fix the problem. To make things even worse, if they did decide to filter such messages, they would disappear into a black hole - SMS provides no functionality to inform the sender that a message has been blocked.
This may be a silly question, but apart from causing a nuisance, what would be the point of doing this? Hacker 1: Hey, watch this! I'm sending messages to let me control a million iPhones. Hacker 2: Cool, it worked. What now? Hacker 1: Um... I could, like, turn their cameras on or something...
Or I could make all the phones call a premium rate phone line that I own... Just a thought.
That continued into the Internet era. There used to be apps that sent ICMP packets with the string +++ATH0 in the payload. Some modems would hang up when they received it.
This is why modems have had +++ guard timers for decades.
Correct me if I'm wrong, but since the SMS messages have to go through the carrier towers, can't this character be "cleaned" from the message there before it even hits the phone?
What if I want to use that character legitimately?
Does FreeBSD even have any 3D video drivers for Nvidia or AMD? If not, then it's not worth even thinking about using it on the desktop for most people.
I think you'll find that most people actually don't really care about 3D. So long as the graphics drivers can run their desktop then most people are happy (Compiz Fusion runs just fine on Intel GPUs).
A minority of people are gamers and therefore do care about 3D. These people will be running Windows since thats where most PC games are.
An even tinier minority actually work in the field of 3D graphics.
Because modern-day admins don't know how to restart a service?
Oooh! Oooh! I think I can get this one! Either of these should work:
# service named restart; #/etc/rc.d/init.d/named restart;
Properly designed packages do "service foo condrestart" on upgrade anyway, so most of the time you don't need to manually restart anything.
But... if you have a properly designed network, why the **** wouldn't you reboot your name server? Given that there are minimally TWO of them registered for your domain name, that the DNS protocol is designed to seamlessly fail over in the event of a failure, rebooting the name server will have no discernible effect for any end user,
I'm afraid you're wrong. If one of your DNS servers disappears, stuff will continue to work *slowly*. If you have 2 NS records then each server will get 50% of the requests. That means that 50% will go to the dead server and have to wait for a timeout before trying the working one.
There are other reasons for not rebooting - restarting bind takes approximately 2 seconds, rebooting one of my servers takes several minutes. As with all reboots I then have to spend time checking that all the other services on the box came back up ok (yes, they should, but these things don't always work so you have to check).
but will provide assurance that all libraries and settings have taken full effect, as the O/S vendor intended.
There is only one OS vendor I can think of who intends you to reboot after anything gets updated, and they don't do Linux distributions...
More so because some package managers (such as CentOS) tend to replace customized init.d files with the stock ones (renaming the ones you had). This is not really a big deal, but it sometimes breaks some services.
If you are modifying packaged files that aren't marked as %config in the RPM spec then you're doing it wrong. 99% of the time you don't need to modify those files anyway, the other 1% of the time you really should be building a custom package and adding it to yum's exclude list.
I would suggest you read about Stateful Packet Inspection, I am quite at a loss to know why you are not already aware that it is a standard feature in firewalls these days.
I am aware - I already mentioned it (aka connection tracking). I also already pointed out why it is completely infeasible to do this. Please go back and read the previous posts in the thread.
Admittedly I got SYN+ACK the wrong way round but the point stands that they should be using some sort of connection tracking to make it irrelevant.
Again, please go back and read the previous posts in the thread - I already explicitly explained to you why connection tracking is not feasible. You are proposing solutions and ignoring all the reasons why they are unworkable, even when clearly explained to you.
The method to identify these could even be the same they used for blocking the SYN+ACK packets (IE, manually).
Manually? are you crazy? Unwired said they were getting 1Gbps of collateral traffic - that equates to about 7.8 million SYN+ACK packets per second, how are you going to manually filter those?
Which should be accounted for when you design the network not when you are faced with an attack.
You really don't understand how large scale IP routing works I'm afraid. You're dealing with enormous networks that have multiple redundant routes via multiple peers and transits over which you have limited control. You cannot design a network that big and redundant so that it can reasonably have the connection tracking that you are suggesting.
You already give one possible solution (shared state tables)
I wasn't really suggesting that as a solution, I was providing it as an example of how any "solution" is utterly unworkable. Shared state tables would require an inordinate amount of internal network bandwidth, would be highly vulnerable to attach and the inherent race conditions would be extremely problematic. The cure would be far worse than the disease.
Care to 'expand' on how routers that can handle over 5.5Gbps of stateful inspection aren't up to the task?
Aside from the aforementioned problems of sharing that amount of state data between the border routers, I'm sure you can agree that AT&T handle orders of magnitude more data than 5.5Gbps.
And you appear to lack imagination or just couldn't be arsed to do a job properly, touche.
No, I just have enough experience to know that your "solutions" are unworkable for many reasons. In AT&T's position I probably would have done exactly the same thing, given the immense problems associated with any "solution" - I don't believe the solutions you are suggesting to be remotely workable, especially not when they are having to be implemented at the drop of a hat.
Slashdot Mirror
For a long time back in the day people wanted to stay at 5 volts to preserve compatibility, so everyone just kept putting it into going faster.
I don't think preserving compatibility had much to do with concentrating on making things go faster. If you wanted to make a low voltage chip that was compatible with 5v power and TTL data then that would be fairly trivial (onboard voltage regulator and some TTL switching at the edges). The simple fact is that for a long time there was pretty much no need for trying to make things consume less power - no one cared about power consumption. Eventually we got to a point where we *had* to care about power consumption because there was just no sane way to cool the chips down (many transistors switching a relatively high voltage in parallel at very high speeds == very high power consumption == very high heat output). These days, we have more and more mobile devices with relatively tiny batteries, so power consumption is becoming an even more important factor.
Frankly, I'm not sure there is a lot of point in going much faster for most people - why do you need an 8 core 10GHz machine to word process and browse the web (which is what most people use their computers for)? Ok, I guess the horrifically inefficient Flash video players might want that. :) The people who are going to want processors a lot faster than what we have today are people doing large number crunching projects, and a lot of those can be parallelised, and we can already do many cores. I'm a professional software developer and my main workstation is now 8 years old (it has had memory and hard drive upgraded several times over the years, but the CPU is the same old one) and amazingly I don't really feel the need to upgrade it. 10 Years ago, if you had told me a workstation would last at least 8 years I would've laughed. Then again, 10 years ago if you had told me that my phone would have a 528MHz ARM, 8 gig of non-volatile storage (upgradable) and a battery life that isn't measured in seconds, I wouldn't have believed you either :).
3D chip layouts are part of this roadmap. This kind of roadmap isn't really intended to say what their process will be, however. It's intended to give numbers to their core design teams about how many transistors they will be able to play with, what the latencies will be, and so on.
I'm unconvinced - the latency characteristics of a 3D architecture are going to be vastly different to those you'll find on any 2D chip, no matter how small you make the features.
That said, I'm assuming Intel is basing this roadmap on some data with at least _some_ substance, rather than just blindly assuming we can keep pushing Moore's law out forever. I'd be interested to know how much of this is based on existing research and how much is BS.
If they go badly wrong, you get something like the Pentium 4.
So I'm going to need a bigger nuclear reactor in my laptop then? :)
what is 1,234? One thousand two hundred and thirty four, or one and two hundred and thirty four thousandths? Mixing the styles is certainly ambiguous at best unless you *always* include tenths in your numbers.
It's fine.
A contract works both ways. They agree to provide certain services and I agree to pay for them. If they don't provide those services that's their choice but I am under no obligation to continue paying.
Sadly the last time I tried to not pay an MNO for illegal charges I was told in no uncertain terms that they would trash my credit rating. Since I didn't have the time to take them to court over it I paid up (if it had been more than a couple of pounds they would've found themselves in the small claims court though).
The way the credit reference system works is completely wrong - the creditors do not have to get a CCJ against you in order to record a default on your credit history. You are assumed to be guilty and you then have to take them to court to prove your innocence.
Even more than that, information is in the public domain. You cannot copyright the fact that a particular train is supposed to arrive at a particular stop at a particular time.
You can't copyright facts, however there are database rights that apply. So whilst you can copy a single fact (since there is no copyright), you can't copy a large chunk of the database.
This sort of crazyness goes on with TV listings and post code databases too - the companies want to have their cake and eat it: the TV channels want people to know what shows are on but also want to be able to make money out of selling the listings, the post office wants everyone to use post codes but also wants to continue making huge amounts of money out of selling the database.
That and the fact that, for pretty much any phone style and available waterproofing technology, the waterproof phone is going to be some combination of larger/heavier/more expensive than the non-waterproof one. And, while everybody wishes their phone were waterproof once it is sitting in a puddle, most will go for the slimmer/cheaper/lighter one when they are in the shop.
It shouldn't take much to waterproof an iPhone, given that it has no buttons...
How old is that eTrex?
Old.. Probably around the 2002 era. It is one of the old monochrome ones.
As I understand it, the old "nitrogen filled" waterproff GPS units lose a lot of their waterproofness over the years as the nitrogen slowly leaks out.
The case is in 2 halves - a back and a front. The join between the two halves is sealed with tape and then the rubber band goes over the top of the tape. The problem is that the (electrical) buttons are under the tape and the rubber buttons moulded into the band just push them through the tape. This lead to the tape splitting around the buttons, so no longer waterproof. So it is really a bit of a design flaw and I'm pretty sure that any eTrex of the same design that has had much use is going to have the same problem.
It was in an AquaPac, but it seems that enough water was inside that (from handling the GPS with wet hands before the AquaPac was sealed) that the GPS drowned (I was using it while windsurfing in the sea, so it got drowned in salt water). I dismantled it, soaked the bits in deionised water, let it dry, and chucked in a sachet of silica gel when I put it all back together and re-sealed it with PVC tape. It all works except for an intermittent fault on the screen that can been cleared by hitting it, which I presume is caused by some salt that didn't get washed off.
Because Europe is a land where people enjoy having their actions and lives dictated to them under the guise of protecting themselves from themselves. Which for the record, is not possible with anything less than handcuffs, force fed tranquilizers, and 24 hour supervision. I'm so glad I'm the age I am in the country I'm in, knowing that very soon I will be dead and shortly after my country will end up just as FUCKED.
Yes, you're absolutely right - the police call round my house 4 times a day to feed me those tranquillisers...
If a company's product cannot work in the environments you plan to use it in, don't buy the product... and don't blame the company if their warranties are voided by using the device in that environment.
Well that very much depends on how the warranty is worded doesn't it? If the warranty says it won't cover a device that has ever been exposed to high humidities then fair enough (although I wouldn't be at all surprised if a court struck down the warranty clause as unreasonable). However, if the warranty says it will be voided by dunking it in liquid water, and your warranty claim gets rejected just because it was in a humid environment then that is a serious problem.
I'm despairing at the state of the cellphone industry at the moment - T-mobile and Carphone Warehouse have both basically told me that they are no longer selling the G1 (HTC Dream - under a year since it was released) because it has been superseded by the G2 (which looks positioned for a different audience to me). The guy in Carphone Warehouse justified this by saying the G2 was "more iPhone like" and thus "better" - I pointed out that if I wanted an iPhone I would get an iPhone, I'm buying an HTC Dream because it suits me better. I would have thought that it would be more sensible to sell a range of devices to suit everyone's needs instead of a million and one iPhone clones.
For at least 10 years the product life cycles have been far too short - they release a device prematurely, full of bugs, and before the bugs have been worked out they cease production and start on a new device which a whole new set of bugs. This is why I've decided not to buy a phone with a closed source OS again - the vendors don't care enough to stabilise the software so the users are the only people who are going to do it. With an open OS there's a chance that this might happen. For example, my current phone which I'm replacing is a 6 year old Sony Ericsson P900 - it was crap and buggy when I bought it but I've not seen anything in the past 6 years that I had any confidence of being better (the email client is so bad that it is completely unusable and the bluetooth stack tends to crash the whole phone a few times a day so you can't really get away with leaving bluetooth turned on).
Even cheap cell phones have submersion detectors these days to prevent people from turning in phones that got dropped into water.
If enough people drop their phones in water to warrant sticking sensors in to void the warranty claims, I would have thought that demonstrates a consumer demand for waterproof devices rather than a demand for warranty voiding sensors...
In any case, I think all the phones I've ever had have got wet one way or another (2 of them soaked in sea water more than once). They all survived surprisingly well, coming back to life after being dismantled, soaked in deionised water and a couple of days drying out. The only device I've drowned which hasn't done so well is my "waterproof, nitrogen filled" Garmin eTrex Venture GPS, which turned out to not be so waterproof - it has mostly recovered, but the screen goes crazy every so often (percussive maintenance fixes it) so I think I need to dismantle it and soak it again. Oh, and a cheap waterproof Casio watch which survived many windsurfing sessions only to fill with water when I washed the car.
Twitter isn't completely worthless. Like MySpace is serves a very good purpose - it keeps the idiots occupied on a very small chunk of the web so the rest of us can easily avoid them and get on with out lives.
Nah, just "No user-serviceable parts inside" and some scored stickers on the screws so they know if you've been fiddling around inside there.
An apple logo tattooed across your head should do the job :)
Shh cities that are actually smart about travel are hard to find.
Though my personal favorite is to tearup a parking lot replace it with a parting garage with half the car slots. And add in a new office building or condo complex. It is like they don't expect people to travel.
Though iwish city streets were drivable by permit only. Without a permit you haveto park at large garages with regular mass transit to take you into the city.
Around here the EU have a habit of making development grants dependent on developments being "public transport friendly". Unfortunately, "public transport friendly" tends to mean encouraging people to use public transport by not providing anywhere near enough parking spaces... even if there happens to be no sane public transport to get there.
Compiz Fusion is an OpenGL compositing manager. If you don't have 3D acceleration, Compiz will run like crap.
Which is why I explicitly said "Compiz Fusion runs just fine on an Intel GPU" - you don't need your fancy super powerful nVidia or AMD GPU (with its lack of decent drivers) to do what most people care about, which is running the desktop.
And to be frank, most people probably don't use a compositing window manager anyway, so don't even care about that.
xfwm4, metacity
Since when did XFWM4 and Metashitty do compositing?
I already get pissed off that there is no way to enter a "Å" character into my P900
Seems Slashdot is also broken at handling unicode characters - that is supposed to be a "Y" with a "^" accent.
If there is a vulnerability with said character, then just using it would not be legitimate until the problem was fixed on the phone firmware.
I haven't seen anything saying what the character is (and more saying that the character being displayed is just a side effect of the crack, not actually the vulnerability). But, that aside, if a legitimate character affects a vulnerability on a *single device*, the service provider has no business breaking legitimate uses of that character by the majority of people (i.e. those that don't own an iphone).
As much as you may like to believe that there is no legitimate use for non-ASCII characters, you are wrong. I already get pissed off that there is no way to enter a "Å" character into my P900 (a bit of a pain since that character appears in my street address.).
Cleaning the character at the carrier could prevent problems spreading to the phone and be a "quick fix", but doesn't make it go away, the phone would need to release a patch eventually, then you can use your Unicode heart character (or whatever else char it is) in your text messages again.
By that mentality, all ISPs should block all web traffic every time a security hole in Internet Explorer is found. Blocking everyone from going about their business because a minority device has a bug is unacceptable, especially since the vendor was informed a month ago and has done nothing to fix the problem. To make things even worse, if they did decide to filter such messages, they would disappear into a black hole - SMS provides no functionality to inform the sender that a message has been blocked.
This may be a silly question, but apart from causing a nuisance, what would be the point of doing this?
Hacker 1: Hey, watch this! I'm sending messages to let me control a million iPhones.
Hacker 2: Cool, it worked. What now?
Hacker 1: Um... I could, like, turn their cameras on or something...
Or I could make all the phones call a premium rate phone line that I own... Just a thought.
That continued into the Internet era. There used to be apps that sent ICMP packets with the string +++ATH0 in the payload. Some modems would hang up when they received it.
This is why modems have had +++ guard timers for decades.
Correct me if I'm wrong, but since the SMS messages have to go through the carrier towers, can't this character be "cleaned" from the message there before it even hits the phone?
What if I want to use that character legitimately?
Does FreeBSD even have any 3D video drivers for Nvidia or AMD? If not, then it's not worth even thinking about using it on the desktop for most people.
I think you'll find that most people actually don't really care about 3D. So long as the graphics drivers can run their desktop then most people are happy (Compiz Fusion runs just fine on Intel GPUs).
A minority of people are gamers and therefore do care about 3D. These people will be running Windows since thats where most PC games are.
An even tinier minority actually work in the field of 3D graphics.
Because modern-day admins don't know how to restart a service?
Oooh! Oooh! I think I can get this one! Either of these should work:
# service named restart; /etc/rc.d/init.d/named restart;
#
Properly designed packages do "service foo condrestart" on upgrade anyway, so most of the time you don't need to manually restart anything.
But... if you have a properly designed network, why the **** wouldn't you reboot your name server? Given that there are minimally TWO of them registered for your domain name, that the DNS protocol is designed to seamlessly fail over in the event of a failure, rebooting the name server will have no discernible effect for any end user,
I'm afraid you're wrong. If one of your DNS servers disappears, stuff will continue to work *slowly*. If you have 2 NS records then each server will get 50% of the requests. That means that 50% will go to the dead server and have to wait for a timeout before trying the working one.
There are other reasons for not rebooting - restarting bind takes approximately 2 seconds, rebooting one of my servers takes several minutes. As with all reboots I then have to spend time checking that all the other services on the box came back up ok (yes, they should, but these things don't always work so you have to check).
but will provide assurance that all libraries and settings have taken full effect, as the O/S vendor intended.
There is only one OS vendor I can think of who intends you to reboot after anything gets updated, and they don't do Linux distributions...
More so because some package managers (such as CentOS) tend to replace customized init.d files with the stock ones (renaming the ones you had). This is not really a big deal, but it sometimes breaks some services.
If you are modifying packaged files that aren't marked as %config in the RPM spec then you're doing it wrong. 99% of the time you don't need to modify those files anyway, the other 1% of the time you really should be building a custom package and adding it to yum's exclude list.
It's not illiteracy, it's attention deficit. Why read the whole sentence when you can just read until you've formed an opinion and ignore the rest?
Must work for Acer customer "support"
I would suggest you read about Stateful Packet Inspection, I am quite at a loss to know why you are not already aware that it is a standard feature in firewalls these days.
I am aware - I already mentioned it (aka connection tracking). I also already pointed out why it is completely infeasible to do this. Please go back and read the previous posts in the thread.
Admittedly I got SYN+ACK the wrong way round but the point stands that they should be using some sort of connection tracking to make it irrelevant.
Again, please go back and read the previous posts in the thread - I already explicitly explained to you why connection tracking is not feasible. You are proposing solutions and ignoring all the reasons why they are unworkable, even when clearly explained to you.
The method to identify these could even be the same they used for blocking the SYN+ACK packets (IE, manually).
Manually? are you crazy? Unwired said they were getting 1Gbps of collateral traffic - that equates to about 7.8 million SYN+ACK packets per second, how are you going to manually filter those?
Which should be accounted for when you design the network not when you are faced with an attack.
You really don't understand how large scale IP routing works I'm afraid. You're dealing with enormous networks that have multiple redundant routes via multiple peers and transits over which you have limited control. You cannot design a network that big and redundant so that it can reasonably have the connection tracking that you are suggesting.
You already give one possible solution (shared state tables)
I wasn't really suggesting that as a solution, I was providing it as an example of how any "solution" is utterly unworkable. Shared state tables would require an inordinate amount of internal network bandwidth, would be highly vulnerable to attach and the inherent race conditions would be extremely problematic. The cure would be far worse than the disease.
Care to 'expand' on how routers that can handle over 5.5Gbps of stateful inspection aren't up to the task?
Aside from the aforementioned problems of sharing that amount of state data between the border routers, I'm sure you can agree that AT&T handle orders of magnitude more data than 5.5Gbps.
And you appear to lack imagination or just couldn't be arsed to do a job properly, touche.
No, I just have enough experience to know that your "solutions" are unworkable for many reasons. In AT&T's position I probably would have done exactly the same thing, given the immense problems associated with any "solution" - I don't believe the solutions you are suggesting to be remotely workable, especially not when they are having to be implemented at the drop of a hat.