I don't "believe in evolution"; I don't "believe in creation".
I "believe in evidence".
Oh, and I have seen older evidence of eggs than of chickens.
But no evidence on the relative age of chicken eggs as that's a semantic trick not a real solvable question.
Well, of course they can, each wavelength of your signal there are billions of cycles of the carrier frequency and untold numbers of photons. Of course classical mechanics works perfectly fine in this state.
What the OP is talking about is trying to push the bit rate beyond the baud rate of the carrier by switching frequencies and phases mid cycle, this works wonderfully in the kHz range and is probably workable upto somewhere in the GHz range but if you try to do this to a signal of half an petahertz you're well into the regime where quantum mechanics reigns and the maths of classical wave theories are just plain wrong.
You wouldn't be able to get enough photons in your signal to get anywhere near classical mechanics, if I've done the maths right a laser of 2mW would have about one photon per bit when modulated at a petabit rate. We already have single photon sensors so I don't doubt that it's possible but it's not gonna be wave mechanics.
Except QAM and QPSK require a medium with a practically pure wave nature, pulse modulation of light is more a particle nature effect with the pluses of light consisting of numbers of individual photons each with their own specific frequency. The higher the data rate the fewer photons in each pulse.
Optical frequency division multiplexing is even more a particulate effect where the prism or grating effectively sorts the photons into individual streams. Though or course the fact that it works at all is actually a wave effect which will go away if you try to measure which slit an individual photon goes through.
I still think we'll get petabyte streams, but it won't be with QAM/QPSK.
.
IrDA! I don't think I've ever used that for real; I always had a laplink cable available. It's main problem IMO was that it was one of those 'bastardised by committee' standards (like the ISO seven layer cake) where they tried to make it fit with every special interest they could. This meant that unless your software was made by a member that specific group it probably wouldn't work because the standard was what they thought they would implement, not what they eventually did. Bluetooth is very much the same. OTOH WiFi, which is technically very similar to BlueTool interoperates very well, presumably because the standards people limited themselves to one task... moving ethernet packets... no packets moving == no WiFi logo.
I think I'd disagree with you there, I know that one to ten or one to a hundred are "the same" it's true and I would suppose their intervals are the same. Perhaps it's something to do with multiplication tables.
But large numbers are always logarithmic. People talk in 'thousands' and 'millions' and 'billions' you know intuitively that the difference between one million and one million and one is tiny even though you've been taught it's the same as between two and three.
The only difference I see here is a matter of scale, one to a hundred are the same because we can see it; you can get a hundred pennies and put them on a multiplication table and see they're the same. But ask most people to visualise a million and you don't get a million pennies.
PS: Check out the megapenny project to see how close you are.
Firefox doesn't have to be installed as superuser.
It's quite possible to install it into the home directory of a 'ffox' user and use sudo to switch from your user to the ffox user when you want to run it. Never run anything else as ffox and never run firefox as yourself. In this setup firefox is quite capable of updating itself.
Of course it's debatable how much extra security this provides (if any, you are still downloading stuff after all) but it is nice shutting down firefox and seeing that there are no processes running under the ffox user.
What I'd like is a nice simple dwiS flag that I can attach... but,
Of course if the first one doesn't work for you maybe Google has already decided you're too dumb...
3G and similar connections across the phone network are connection based. If you don't send packets the connection drops and takes a substantial fraction of a second to reconnect. Remotes sending you packets (usually) won't bring the connection up so they don't hit either your bill or your battery. (Nor do they waste the very limited shared bandwidth of the network)
This happens even if you have a global IP address.
Sigh, you don't need NAT to intercept connections, at the primitive level you can block the connection with a firewall and receive and respond to the connection with packet capture. All the IPtables 'REDIRECT' target does it wrap this up into a 'simple' interface; when your server program receives the connection it still has the IP address that the original connection was being made to so it can continue the proxy connection even if the client doesn't say what it was trying to do. NAT actually breaks this.
The mobile phone companies looked into using NAT, in fact they are using NAT because there are simply not enough IPv4 addresses for them. They have hundreds of millions of customers, so they have to use multiple copies of 10.0/8 , one isn't enough.
It doesn't matter; even if they put those addresses back into the pool now it would last about 6 months top. The "burn rate" for IP addresses when they ran out at the top level was three/8 networks per month; think about that at the peak rate what you're proposing would last about 80 days!
The thing is you really don't have any concept of the number of IP capable mobile phones being made in the world.
I don't have 2020 vision, but it's really unlikely that the new guy can be as successful as the extremely "unique" individual who built the company. The board of directors, who took control when he left, wouldn't allow it. They will basically choose someone just like them with the exception that this person is willing to take a greater risk, ie when something goes wrong they will be kicked out, for a better reward.
This is nothing like Steve Jobs who basically loved the game, he was very, very good at it but basically played to the game because he wanted to, the money was just the way of keeping score.
As for being successful enough; well there's a good reason the guy before him to left so he wasn't bought in to captain a sinking ship which probably means he will be successful because he'll be able to leave 'for personal reasons' before the ship hits the fan.
That's easy, for patents, the environment hasn't changed much since the Patent was invented.
So if a "little guy" gets a markable idea a big company will come along, copy it, and use it's larger manufacturing capacity to put through a shitty knock off before the little guy gets the first one out of the door. If the little guy tries to go to court (which will still in theory be possibly) he'll be swamped under lawyers. If two middle size companies come out with similar products at the same time they'll sue each other and waste lots of court time trying to convince everyone that the other guy knocked them off.
So nope, patent reform is needed, abolishing patents is still a really bad idea.
NB: The "equation" is different for copyrights though.
It's not talked about much, but one of the things that helps reduce the price of fertiliser is treated sewage. So it basically sets up a cycle with what's taken out of the land for food being "given back". This frequently works as a double loop with crops grown with Human sewage used to feed cattle and bullshit used to feed the crops for people as this is generally "less yukky" and normally safer because diseases don't switch between species much.
In Africa (in general) this cycle doesn't exist, the sanitation is often poor and the sewage treatment worse. Even when sanitation does exist many people seem to prefer a quiet spot in the bushes. Without the cycle fertiliser is expensive without fertiliser you will only get a couple of crops from a piece of land before you drain it of nutrients.
This is a basic rule of farming, another way of doing the same thing is crop rotation now this works on a much more local scale which keeps big business out of the equation but but will probably work best if the soil recovery is aided by a contract with the local 'nightsoil collector.'
Sure, they don't want to kill the internet connections of thousands (or millions) of people in one night, this will cause the odd serious problem.
But leaving some servers running perfectly isn't going to solve anything either. If everything is working fine these people are just going to leave it be; as they were told by the last guy who charged them to fix their machine last time!
The answer is actually very simple; leave the server running but make sure it's CRAP.
On day zero it works perfectly.
On day one just one percent of queries are given a serverfail.
On day two two percent are failed
By the end of the first week people will start to notice that their internet is getting crap.
By the end of the first month they will be asking around for help
By the end of the second month they'll be ready to pay for help
And finally, after just three months (and a week) the servers can be turned off, they're not doing anything anymore.
I eventually RTFA (and movie), They appear to be 'unbricking' the iPhone with a custom bootloader from the USB. Once they've done this they can grab the flash and post it to the PC. For a PC brute forcing a 4 digit passcode is a millisecond job (hell, a 20digit passcode is just an annoying little pause).
It's very much a dumb user tool, if your fingers are too fat to properly push the iPhone's buttons they even have special recovery options for when you mess up.
I used to use this, but I tend to use rsync nowadays; it automatically does something very similar (only better in that the physical copy only copies new data) in a fraction of the command size. And it has it's -P argument.
SOME services can be restarted, For example 'REST'full things like web servers. But for many services state is held in memory so 'just' restarting the service is almost as bad as restarting the whole box. Even with web servers it's likely that users will get logged out.
If you're lucky the in memory stuff is 'only a cache' and the service "only runs slow for a little while".
This is why 'live migration' is popular in some circles, where a service or virtual machine moves between physical machines without interrupting any service state, network connections or running tasks.
On, and BTW; most Linux init like programs can be restart easily, just send them the right signal and they 'exec' themselves. Of course they do have state, which they have to save for the new instance of the process.
I've worked under the flight path of Concord taking off from Heathrow.
You are not wrong, the engines are very very very loud.
The office was specially soundproofed. From the right rooms you could see the planes landing; they are heading straight for you looking like they're rather likely to land in the car park.
The Smokers (who weren't allowed to smoke in the office) made real sure that they were never outside when the Concord went over.
It sets of car alarms.
On a good day shakes your eyeballs, the whole world goes wobbly.
Except that quote is assuming that the attacker is starting from either now or last tuesday. The POC executable that was leaked was written back in November so there's nothing to say that someone hasn't been working on it the LAST 30 days.
If that's true expect a worm starting up on Friday evening at the latest.
The threat is real and the lack of a public RCE means little.
Yes, I look at it in the same way as a libc upgrade. It's all very nice that the system can continue and if you're lucky and the job the system is doing doesn't need the new version of libc but at some point the services and system needs to be restarted because you MUST be able to do a cold start.
People make mistakes and a cold start during an emergency is NOT the time to discover that someone made a mistake during an upgrade 18 months ago.
Those 315 seconds per year (Five minutes) that you get from the calculation for ''five nines' reliability is NOT a maintenance window! It's the time you have to fix things WHEN something breaks unexpectedly. What you're looking at is 24x7 availability this is a different problem and in this sort of situation preventative maintenance must be designed for with zero downtime even if that PM is physically replacing a machine.
The five or ten seconds that some clusters take to switch nodes during a crash (or even sometimes a planned node migration) is what gets charged to the 315 seconds of the 99.999% reliability BUT only if it's within the availability times (if that's 24x7 well, that's what you have to design for).
And BTW, your two examples are pretty easy to arrange a cluster, the phone calls you just bring a new node online and change your front end routers to stop sending new calls to the machine that's going out and start sending them to the new one. A few minutes later the old machine is idle and can be rebooted/removed etc. The CCTV cameras are even easier; they can be switched between frames or by allowing a couple of seconds of overlap. If you haven't got the hardware for that, well, your system isn't designed for 24x7 operation even if it's got 'five nines'.
Slashdot Mirror
I don't "believe in evolution"; I don't "believe in creation".
I "believe in evidence".
Oh, and I have seen older evidence of eggs than of chickens.
But no evidence on the relative age of chicken eggs as that's a semantic trick not a real solvable question.
Well, of course they can, each wavelength of your signal there are billions of cycles of the carrier frequency and untold numbers of photons. Of course classical mechanics works perfectly fine in this state.
What the OP is talking about is trying to push the bit rate beyond the baud rate of the carrier by switching frequencies and phases mid cycle, this works wonderfully in the kHz range and is probably workable upto somewhere in the GHz range but if you try to do this to a signal of half an petahertz you're well into the regime where quantum mechanics reigns and the maths of classical wave theories are just plain wrong.
You wouldn't be able to get enough photons in your signal to get anywhere near classical mechanics, if I've done the maths right a laser of 2mW would have about one photon per bit when modulated at a petabit rate. We already have single photon sensors so I don't doubt that it's possible but it's not gonna be wave mechanics.
Except QAM and QPSK require a medium with a practically pure wave nature, pulse modulation of light is more a particle nature effect with the pluses of light consisting of numbers of individual photons each with their own specific frequency. The higher the data rate the fewer photons in each pulse.
Optical frequency division multiplexing is even more a particulate effect where the prism or grating effectively sorts the photons into individual streams. Though or course the fact that it works at all is actually a wave effect which will go away if you try to measure which slit an individual photon goes through.
I still think we'll get petabyte streams, but it won't be with QAM/QPSK.
.
IrDA! I don't think I've ever used that for real; I always had a laplink cable available. It's main problem IMO was that it was one of those 'bastardised by committee' standards (like the ISO seven layer cake) where they tried to make it fit with every special interest they could. This meant that unless your software was made by a member that specific group it probably wouldn't work because the standard was what they thought they would implement, not what they eventually did. Bluetooth is very much the same. OTOH WiFi, which is technically very similar to BlueTool interoperates very well, presumably because the standards people limited themselves to one task ... moving ethernet packets ... no packets moving == no WiFi logo.
I think I'd disagree with you there, I know that one to ten or one to a hundred are "the same" it's true and I would suppose their intervals are the same. Perhaps it's something to do with multiplication tables.
But large numbers are always logarithmic. People talk in 'thousands' and 'millions' and 'billions' you know intuitively that the difference between one million and one million and one is tiny even though you've been taught it's the same as between two and three.
The only difference I see here is a matter of scale, one to a hundred are the same because we can see it; you can get a hundred pennies and put them on a multiplication table and see they're the same. But ask most people to visualise a million and you don't get a million pennies.
PS: Check out the megapenny project to see how close you are.
Firefox doesn't have to be installed as superuser.
It's quite possible to install it into the home directory of a 'ffox' user and use sudo to switch from your user to the ffox user when you want to run it. Never run anything else as ffox and never run firefox as yourself. In this setup firefox is quite capable of updating itself.
Of course it's debatable how much extra security this provides (if any, you are still downloading stuff after all) but it is nice shutting down firefox and seeing that there are no processes running under the ffox user.
"Do what I mean" is the worst possible response from a computer, "Do what I say" might be bad but it's better than any of the alternatives.
That's why my Google links have a veritable alphabet soup attached to them... Google Search 1 vs. Google search 2
What I'd like is a nice simple dwiS flag that I can attach ... but,
Of course if the first one doesn't work for you maybe Google has already decided you're too dumb...
Air drag goes up as a fourth power of the speed.
3G and similar connections across the phone network are connection based. If you don't send packets the connection drops and takes a substantial fraction of a second to reconnect. Remotes sending you packets (usually) won't bring the connection up so they don't hit either your bill or your battery. (Nor do they waste the very limited shared bandwidth of the network)
This happens even if you have a global IP address.
Sigh, you don't need NAT to intercept connections, at the primitive level you can block the connection with a firewall and receive and respond to the connection with packet capture. All the IPtables 'REDIRECT' target does it wrap this up into a 'simple' interface; when your server program receives the connection it still has the IP address that the original connection was being made to so it can continue the proxy connection even if the client doesn't say what it was trying to do. NAT actually breaks this.
The mobile phone companies looked into using NAT, in fact they are using NAT because there are simply not enough IPv4 addresses for them. They have hundreds of millions of customers, so they have to use multiple copies of 10.0/8 , one isn't enough.
It doesn't matter; even if they put those addresses back into the pool now it would last about 6 months top. The "burn rate" for IP addresses when they ran out at the top level was three /8 networks per month; think about that at the peak rate what you're proposing would last about 80 days!
The thing is you really don't have any concept of the number of IP capable mobile phones being made in the world.
I don't have 2020 vision, but it's really unlikely that the new guy can be as successful as the extremely "unique" individual who built the company. The board of directors, who took control when he left, wouldn't allow it. They will basically choose someone just like them with the exception that this person is willing to take a greater risk, ie when something goes wrong they will be kicked out, for a better reward.
This is nothing like Steve Jobs who basically loved the game, he was very, very good at it but basically played to the game because he wanted to, the money was just the way of keeping score.
As for being successful enough; well there's a good reason the guy before him to left so he wasn't bought in to captain a sinking ship which probably means he will be successful because he'll be able to leave 'for personal reasons' before the ship hits the fan.
That's easy, for patents, the environment hasn't changed much since the Patent was invented.
So if a "little guy" gets a markable idea a big company will come along, copy it, and use it's larger manufacturing capacity to put through a shitty knock off before the little guy gets the first one out of the door. If the little guy tries to go to court (which will still in theory be possibly) he'll be swamped under lawyers. If two middle size companies come out with similar products at the same time they'll sue each other and waste lots of court time trying to convince everyone that the other guy knocked them off.
So nope, patent reform is needed, abolishing patents is still a really bad idea.
NB: The "equation" is different for copyrights though.
It's not talked about much, but one of the things that helps reduce the price of fertiliser is treated sewage. So it basically sets up a cycle with what's taken out of the land for food being "given back". This frequently works as a double loop with crops grown with Human sewage used to feed cattle and bullshit used to feed the crops for people as this is generally "less yukky" and normally safer because diseases don't switch between species much.
In Africa (in general) this cycle doesn't exist, the sanitation is often poor and the sewage treatment worse. Even when sanitation does exist many people seem to prefer a quiet spot in the bushes. Without the cycle fertiliser is expensive without fertiliser you will only get a couple of crops from a piece of land before you drain it of nutrients.
This is a basic rule of farming, another way of doing the same thing is crop rotation now this works on a much more local scale which keeps big business out of the equation but but will probably work best if the soil recovery is aided by a contract with the local 'nightsoil collector.'
Sure, they don't want to kill the internet connections of thousands (or millions) of people in one night, this will cause the odd serious problem.
But leaving some servers running perfectly isn't going to solve anything either. If everything is working fine these people are just going to leave it be; as they were told by the last guy who charged them to fix their machine last time!
The answer is actually very simple; leave the server running but make sure it's CRAP.
On day zero it works perfectly.
On day one just one percent of queries are given a serverfail.
On day two two percent are failed
By the end of the first week people will start to notice that their internet is getting crap.
By the end of the first month they will be asking around for help
By the end of the second month they'll be ready to pay for help
And finally, after just three months (and a week) the servers can be turned off, they're not doing anything anymore.
Because that's the default if you have a single colon like in my example.
rsync -PAX -Hax somedir remote@remotehost::module/remote/path
This is for a bare rsync server, (or use rsync:// )
The wrong one; they reboot the iphone into unbricking mode and suck all or part of it's flash onto the PC. Probably decrypt it there.
I eventually RTFA (and movie), They appear to be 'unbricking' the iPhone with a custom bootloader from the USB. Once they've done this they can grab the flash and post it to the PC. For a PC brute forcing a 4 digit passcode is a millisecond job (hell, a 20digit passcode is just an annoying little pause).
It's very much a dumb user tool, if your fingers are too fat to properly push the iPhone's buttons they even have special recovery options for when you mess up.
I used to use this, but I tend to use rsync nowadays; it automatically does something very similar (only better in that the physical copy only copies new data) in a fraction of the command size. And it has it's -P argument.
rsync -PAX -Hax somedir remote@remotehost:/a/remote/path
Okay, I tried to look it up ...
WXGA 1280 720 16:9 0.922
WXGA 1280 768 5:3 0.983
WXGA 1280 800 16:10 1.024
WXGA 1360 768 ~16:9 1.044
WXGA 1366 768 ~16:9 1.049
It looks more like you're trolling; so now I too ask WTF is WXGA!
SOME services can be restarted, For example 'REST'full things like web servers. But for many services state is held in memory so 'just' restarting the service is almost as bad as restarting the whole box. Even with web servers it's likely that users will get logged out. If you're lucky the in memory stuff is 'only a cache' and the service "only runs slow for a little while". This is why 'live migration' is popular in some circles, where a service or virtual machine moves between physical machines without interrupting any service state, network connections or running tasks.
On, and BTW; most Linux init like programs can be restart easily, just send them the right signal and they 'exec' themselves. Of course they do have state, which they have to save for the new instance of the process.
I've worked under the flight path of Concord taking off from Heathrow.
You are not wrong, the engines are very very very loud.
The office was specially soundproofed. From the right rooms you could see the planes landing; they are heading straight for you looking like they're rather likely to land in the car park.
The Smokers (who weren't allowed to smoke in the office) made real sure that they were never outside when the Concord went over.
It sets of car alarms.
On a good day shakes your eyeballs, the whole world goes wobbly.
Except that quote is assuming that the attacker is starting from either now or last tuesday. The POC executable that was leaked was written back in November so there's nothing to say that someone hasn't been working on it the LAST 30 days.
If that's true expect a worm starting up on Friday evening at the latest.
The threat is real and the lack of a public RCE means little.
Yes, I look at it in the same way as a libc upgrade. It's all very nice that the system can continue and if you're lucky and the job the system is doing doesn't need the new version of libc but at some point the services and system needs to be restarted because you MUST be able to do a cold start.
People make mistakes and a cold start during an emergency is NOT the time to discover that someone made a mistake during an upgrade 18 months ago.
What!
Those 315 seconds per year (Five minutes) that you get from the calculation for ''five nines' reliability is NOT a maintenance window! It's the time you have to fix things WHEN something breaks unexpectedly. What you're looking at is 24x7 availability this is a different problem and in this sort of situation preventative maintenance must be designed for with zero downtime even if that PM is physically replacing a machine.
The five or ten seconds that some clusters take to switch nodes during a crash (or even sometimes a planned node migration) is what gets charged to the 315 seconds of the 99.999% reliability BUT only if it's within the availability times (if that's 24x7 well, that's what you have to design for).
And BTW, your two examples are pretty easy to arrange a cluster, the phone calls you just bring a new node online and change your front end routers to stop sending new calls to the machine that's going out and start sending them to the new one. A few minutes later the old machine is idle and can be rebooted/removed etc. The CCTV cameras are even easier; they can be switched between frames or by allowing a couple of seconds of overlap. If you haven't got the hardware for that, well, your system isn't designed for 24x7 operation even if it's got 'five nines'.