Yeah it's nothing new to put such emulation in place, apple did it twice when they switched to powerpc and when they switched to intel. DEC did it for windows NT on alpha. Intel did it for windows and linux on itanium (the itanium originally had hardware x86 support but it sucked so much that software emulation was faster and it was removed in later versions). qemu can do it for linux binaries across a wide range of cpu architecture combinations.
It's doable but there is a significant performance penalty. Thats tolerable if your new CPU is significantly better than your old one/competitors one but if your new chip is only slightly better than your old one or your competitors one then it's going to suck badly.
They also recently bought the SSD part of OCZ which had a reputation for being one of the shittiest SSD makers around. I'd want to hold off for a while to see if they can turn that around before buying their SSDs.
Also apparently their marketing was terrible, so they didn't reach out to the people who could benefit from their service and afford the price.
I would note that while the original irridium company did fail the new irridium company is managing to find enough money from it's subscribers to fund satellite renewal.
iirc they tried a few different methods over the years, IIRC they tried transmitting programs in the computers native tape format and they also tried using a special tape format that was designed to be used on multiple different computers (with a special loader program) and to be more tolerant of poor tranmission conditions. I think they may have tried program distribution over teletext at one point too but few people had a teletext decoder hooked up to their computer.
Granted you'd need a large number of such antenna to cover the earth since they'd be highly directional.
The trick is to use a phased array, the individual antennas in the array have relatively low gain (and are hence physically small) on their own, however by driving them as an array you can create highly directional beams and you can do it in many directions and it turns out you can do the same thing for receive by doing weighted sums of the inputs.
The handheld end is more problematic, the directionality of an antenna is highly dependent on size and there isn't much you can do about that. There is also the problem that if it's too directional you have to aim it at the sattelite (either physically or electronically)
handheld phone to geostationary orbit has been done with a phased array on the sattelite.
It takes just over 100ms to send a signal to geostationary orbit for your round trip time you have to multiply that by four (client-sattelite-server-sattelite-client) giving a minimum theoretical ping time of just under 500ms.
Lower orbits should do better and it should certainly be possible to bring the latency down to a level where it is comparable to the latency experianced when browsing an australian website from europe.
If you are seeing two seconds of latency from your sattelite provider there is some other factor at play besides the raw radio latency to/from orbit.
Bitlocker is REALLY not good enough, for most users won't have access to it -- since it is only in the ENTERPRISE version of Windows 7; in particular... Windows 7 Standard and Professional do not have the feature..
The problem with this idea is that if your competitor doesn't have a quota system, and they *do* just hire whoever is best, then statistically speaking they are likely to be hiring slightly better people than you and out innovate and out compete you.
The other problem is it breeds resentment among the white able bodied males who are discriminated against by the quota systems. It also breeds resentment amongst the companies own staff who may feel they are being forced to hire unqualified staff to meet quota.
The GNOME Foundation ran out of money because they funded a women's outreach program which ate a quarter of their entire budget a couple of years ago and pretty much destroyed their overall finances in 2013.
That is somewhat misleading, thier mistake wasn't really funding a couple of students on the outreach program, that was well within their resources.
Thier mistake was managing the program without insisting on pre-payment from the other funders and hence screwing up their cashflow. They could have got into a very similar mess with an outreach program that was not discriminatory.
Also once you start having pay for licenses you have to start tracking said pay for licenses, even if they are so cheap that the license cost itself is a rounding error the cost of tracking those licenses, ensuring software can only be downloaded/used by people who have licenses and so-on often is not.
what the big deal if the router to the ISP is a measly 1.5mbps or 10mbps ? like you can download faster than your ISP can provide
There is a world beyond your shitty little home or small buisness "broadband" connection.
While theoretical maximum speeds make good headlines the real purpose of advances in wireless communications is not so much supporting higher speeds to a single user as supporting more users of a given speed in a given area.
The bottle neck is the up and download link to your ISP. They need to solve that problem.
Other working groups in the IEEE and otherwise have been working on both getting more out of existing infrastructure and producing standards for new infrastructure.
Unfortunately slow home/small buisness broadband speeds are mostly an economic and/or regulatory problem. We have tapped out what conventional phone lines to the phone exchange can can deliver given their attenuation and noise/interference characteristics and while cable TV cables can carry much more data than phone lines they are fundamentally broadcast networks so available bandwidth per user is limited. To significantly improve from the current point in areas with conventional copper ADSL requires some or all of the infrastructure to be replaced with fiber.
New last mile infrastructure providers face large hurdles both economic and regulatory and existing monopoly/duopoly providers often see little gain in doing a large scale forklift upgrade of their infrastructure when only a minority will pay significantly more for the higher speeds and when the technology is still improving (so the more they delay the upgrade the better the system they will get in the end).
Don't get me wrong, I understand your frustration but it's not really something that the IEEE working groups can solve.
When you join all these techniques together, get into MIMO, add all sorts of clever coding theory, you can get as much as you like from the signal - the only limit is how accurate you are sending and receiving.
Noise and interference limit how many bits you can have per symbol on a channel and the lack of independence in the channels limits the gains from MIMO*. There are still gains to be had but you get into diminishing returns in terms of bandwidth delivered to a given location (bandwidth delivered to many different locations is another matter, there are major gains to be had from cross-cell mimo in cellular systems but also major implementation difficulties).
* MIMO relies on some clever maths to create inddependent channels out of non-independent channels but that math has the side affect of amplifying the noice.
AIUI the trouble with those cards is that the only interface between the card and the thing it's plugged into is a shared storage array and said shared storage array is rather lacking in terms of good mechanisms to handle writes from both sides without corruption.
This kind of limits their utility for anything beyond their intended use of making it slightly easier to get the pics off your camera.
The problem isn't so much "speaking IP", a PIC18 can do that.
But when you want TCP, SSL, HTTP, support for several types of VPN* and so-on it gets harder and harder to implement on a small microcontroller and something a bit more powerful that can run a proper OS (albiet a pretty stripped down one) looks more attractive.
* VPN support is useful in "internet of things" type applications because you often want to deploy them where you don't have a public IP and/or you don't control the network and yet you would quite like to be able to remote admin them.
unvaccinated people (and those 10%-30% or more ( for whom a vaccine does nothing) don't automatically harm people. By the way those high percentages of those who are not given immunity destroy any argument made using that nonsense phrase "herd immunity", there are ALWAYS many people in a group that will not have immunity, vaccine or not.
If you can keep the vulnerable people evenly spread out and at a low enough density then the disease will gradually die out. Many diseases that used to be endemic are now almost unheard of. One has even been wiped out.
But if the overall rate of vulnerable people rises too high or if you get clusters of vulnerbale people (e.g. a fundamentalist church) then the virus can start to spread again.
Now this won't work for every disease, some diseases have a combination of vaccine success rate, mutation rate and transmission rate that even with 100% vaccination they will still be endemic, just at a lower rate than without the vaccination.
And even if Theo and crew don't port it themselves I would pretty much bank on the fact that, say, someone at Debian will take the BSD code and port it to Linux - it's not as if OpenBSD will have a problem with this.
The problem with crypto is it's really easy to end up with something that works but isn't secure.
Libressl and openssl take different approaches. Openssl's appoach is to rely on the OS as little as possible. Libressl is targetted at openbsd and relies heavilly on library features provided by openbsd.
If and when there is a linux port of libressl that is blessed by the libressl team then it might be worth considering but a bad port of libressl could easilly end up being a lot worse than openssl.
Be careful with libressl though, the developers have been stripping out what they see as the wrong approach to portability and currently only support openbsd. There have been third party ports to other operating systems but great care is needed when making such ports as assumptions that hold on openbsd but not on other platforms may go unnoticed.
A badly done port of libressl could easilly end up significantly worse than openssl.
I'd say the horrendous state of ssl certiciate security has aspects in all three categories.
Specification failure: Certificates can only be signed by a single CA, no mechanism for multiple signatures on a cert to give a greater assurance level. No mechanism to limit a CA to a subset of the dns heirachy. Implementation failure: Major implementations include an insane default CA list*, poor handling of certificates of different trust levels (clever use of redirects can allow interception of form data for an EV site without making the green bar disappear) Deployment failure: noone looks at the list of CAs and makes an informed descion on what to accept, they just leave it at the software vendors defaults.
but yeah none of these are openssl's fault. By the time they came along the bad descisions had already been made.
* Seriously mozilla why the heck did you include the chineese government.
And you also need them because sometimes your demographic predictions say that a local increase in the number of schoolkids is temporary, or because your demographic predictions were wrong and you need to add capacity quickly.
There is also the question of what will your district look like in a decade or so? will it still be full of families with school-age children? or will it be full of older people whose kids have moved on to a new area?
They could do it the other way arround, make an update to the updater that (among other things) checks more thouroughly what edition of the OS it's running on, then make it so you have to update the updater to get any other updates.
I dunno about the rest of europe but here in the UK car tax for ordinary cars registered since 1 march 2001* is determined from official CO2 emmision figures. The ammount of CO2 that comes out of the exhaust is almost directly proportional to the ammount of carbon in the fuel that goes from the tank to the engine**. I don't know if they directly measure the CO2 or just calculate it from the fuel input but either way it isn't going to make a massive difference.
* Older cars and new cars for which official CO2 figures are not available (scratch built custom cars and such) are taxed based on engine size. Very old cars are classed as historic vehicles and exempt from road tax. ** Carbon that comes out in any form other than CO2 is bad since it represents incomplete combustion and can be a nasty polloutant in it's own right.
By the time I had a client request that function (people can change documents but not delete), it was no longer a possibility.
It's a dumb idea in most cases, usually blanking out a file or replacing it's contents with random garbage is just as bad as deleting it. Maybe worse because it makes people think the file is still there until they look inside.
AIUI with many potential and actual execution drugs complicated production facilities are required and the facilities that exist are sited in countries that are anti-death penalty. This poses a problem, especially as many of those drugs are also useful medically so the USA really doesn't want to be banned from buying them.
OTOH seperation of nitrogen from air is relatively trivial and done all over the world so it's hard for a foreign covernment to ban it.
Yeah it's nothing new to put such emulation in place, apple did it twice when they switched to powerpc and when they switched to intel. DEC did it for windows NT on alpha. Intel did it for windows and linux on itanium (the itanium originally had hardware x86 support but it sucked so much that software emulation was faster and it was removed in later versions). qemu can do it for linux binaries across a wide range of cpu architecture combinations.
It's doable but there is a significant performance penalty. Thats tolerable if your new CPU is significantly better than your old one/competitors one but if your new chip is only slightly better than your old one or your competitors one then it's going to suck badly.
They also recently bought the SSD part of OCZ which had a reputation for being one of the shittiest SSD makers around. I'd want to hold off for a while to see if they can turn that around before buying their SSDs.
Also apparently their marketing was terrible, so they didn't reach out to the people who could benefit from their service and afford the price.
I would note that while the original irridium company did fail the new irridium company is managing to find enough money from it's subscribers to fund satellite renewal.
iirc they tried a few different methods over the years, IIRC they tried transmitting programs in the computers native tape format and they also tried using a special tape format that was designed to be used on multiple different computers (with a special loader program) and to be more tolerant of poor tranmission conditions. I think they may have tried program distribution over teletext at one point too but few people had a teletext decoder hooked up to their computer.
Granted you'd need a large number of such antenna to cover the earth since they'd be highly directional.
The trick is to use a phased array, the individual antennas in the array have relatively low gain (and are hence physically small) on their own, however by driving them as an array you can create highly directional beams and you can do it in many directions and it turns out you can do the same thing for receive by doing weighted sums of the inputs.
The handheld end is more problematic, the directionality of an antenna is highly dependent on size and there isn't much you can do about that. There is also the problem that if it's too directional you have to aim it at the sattelite (either physically or electronically)
handheld phone to geostationary orbit has been done with a phased array on the sattelite.
It takes just over 100ms to send a signal to geostationary orbit for your round trip time you have to multiply that by four (client-sattelite-server-sattelite-client) giving a minimum theoretical ping time of just under 500ms.
Lower orbits should do better and it should certainly be possible to bring the latency down to a level where it is comparable to the latency experianced when browsing an australian website from europe.
If you are seeing two seconds of latency from your sattelite provider there is some other factor at play besides the raw radio latency to/from orbit.
Bitlocker is REALLY not good enough, for most users won't have access to it -- since it is only in the ENTERPRISE version of Windows 7; in particular... Windows 7 Standard and Professional do not have the feature. .
It's also in the ultimate edition.
The problem with this idea is that if your competitor doesn't have a quota system, and they *do* just hire whoever is best, then statistically speaking they are likely to be hiring slightly better people than you and out innovate and out compete you.
The other problem is it breeds resentment among the white able bodied males who are discriminated against by the quota systems. It also breeds resentment amongst the companies own staff who may feel they are being forced to hire unqualified staff to meet quota.
The GNOME Foundation ran out of money because they funded a women's outreach program which ate a quarter of their entire budget a couple of years ago and pretty much destroyed their overall finances in 2013.
That is somewhat misleading, thier mistake wasn't really funding a couple of students on the outreach program, that was well within their resources.
Thier mistake was managing the program without insisting on pre-payment from the other funders and hence screwing up their cashflow. They could have got into a very similar mess with an outreach program that was not discriminatory.
Also once you start having pay for licenses you have to start tracking said pay for licenses, even if they are so cheap that the license cost itself is a rounding error the cost of tracking those licenses, ensuring software can only be downloaded/used by people who have licenses and so-on often is not.
what the big deal if the router to the ISP is a measly 1.5mbps or 10mbps ? like you can download faster than your ISP can provide
There is a world beyond your shitty little home or small buisness "broadband" connection.
While theoretical maximum speeds make good headlines the real purpose of advances in wireless communications is not so much supporting higher speeds to a single user as supporting more users of a given speed in a given area.
The bottle neck is the up and download link to your ISP. They need to solve that problem.
Other working groups in the IEEE and otherwise have been working on both getting more out of existing infrastructure and producing standards for new infrastructure.
Unfortunately slow home/small buisness broadband speeds are mostly an economic and/or regulatory problem. We have tapped out what conventional phone lines to the phone exchange can can deliver given their attenuation and noise/interference characteristics and while cable TV cables can carry much more data than phone lines they are fundamentally broadcast networks so available bandwidth per user is limited. To significantly improve from the current point in areas with conventional copper ADSL requires some or all of the infrastructure to be replaced with fiber.
New last mile infrastructure providers face large hurdles both economic and regulatory and existing monopoly/duopoly providers often see little gain in doing a large scale forklift upgrade of their infrastructure when only a minority will pay significantly more for the higher speeds and when the technology is still improving (so the more they delay the upgrade the better the system they will get in the end).
Don't get me wrong, I understand your frustration but it's not really something that the IEEE working groups can solve.
When you join all these techniques together, get into MIMO, add all sorts of clever coding theory, you can get as much as you like from the signal - the only limit is how accurate you are sending and receiving.
Noise and interference limit how many bits you can have per symbol on a channel and the lack of independence in the channels limits the gains from MIMO*. There are still gains to be had but you get into diminishing returns in terms of bandwidth delivered to a given location (bandwidth delivered to many different locations is another matter, there are major gains to be had from cross-cell mimo in cellular systems but also major implementation difficulties).
* MIMO relies on some clever maths to create inddependent channels out of non-independent channels but that math has the side affect of amplifying the noice.
AIUI the trouble with those cards is that the only interface between the card and the thing it's plugged into is a shared storage array and said shared storage array is rather lacking in terms of good mechanisms to handle writes from both sides without corruption.
This kind of limits their utility for anything beyond their intended use of making it slightly easier to get the pics off your camera.
The problem isn't so much "speaking IP", a PIC18 can do that.
But when you want TCP, SSL, HTTP, support for several types of VPN* and so-on it gets harder and harder to implement on a small microcontroller and something a bit more powerful that can run a proper OS (albiet a pretty stripped down one) looks more attractive.
* VPN support is useful in "internet of things" type applications because you often want to deploy them where you don't have a public IP and/or you don't control the network and yet you would quite like to be able to remote admin them.
unvaccinated people (and those 10%-30% or more ( for whom a vaccine does nothing) don't automatically harm people. By the way those high percentages of those who are not given immunity destroy any argument made using that nonsense phrase "herd immunity", there are ALWAYS many people in a group that will not have immunity, vaccine or not.
If you can keep the vulnerable people evenly spread out and at a low enough density then the disease will gradually die out. Many diseases that used to be endemic are now almost unheard of. One has even been wiped out.
But if the overall rate of vulnerable people rises too high or if you get clusters of vulnerbale people (e.g. a fundamentalist church) then the virus can start to spread again.
Now this won't work for every disease, some diseases have a combination of vaccine success rate, mutation rate and transmission rate that even with 100% vaccination they will still be endemic, just at a lower rate than without the vaccination.
And even if Theo and crew don't port it themselves I would pretty much bank on the fact that, say, someone at Debian will take the BSD code and port it to Linux - it's not as if OpenBSD will have a problem with this.
The problem with crypto is it's really easy to end up with something that works but isn't secure.
Libressl and openssl take different approaches. Openssl's appoach is to rely on the OS as little as possible. Libressl is targetted at openbsd and relies heavilly on library features provided by openbsd.
http://insanecoding.blogspot.n...
http://insanecoding.blogspot.n...
If and when there is a linux port of libressl that is blessed by the libressl team then it might be worth considering but a bad port of libressl could easilly end up being a lot worse than openssl.
Be careful with libressl though, the developers have been stripping out what they see as the wrong approach to portability and currently only support openbsd. There have been third party ports to other operating systems but great care is needed when making such ports as assumptions that hold on openbsd but not on other platforms may go unnoticed.
A badly done port of libressl could easilly end up significantly worse than openssl.
IIRC recent versions of gnutls are under a LGPLv3+/GPLv2+ dual license.
I belive mozilla NSS is under the standard mozilla tri-license but i'm not positive on that.
I'd say the horrendous state of ssl certiciate security has aspects in all three categories.
Specification failure: Certificates can only be signed by a single CA, no mechanism for multiple signatures on a cert to give a greater assurance level. No mechanism to limit a CA to a subset of the dns heirachy.
Implementation failure: Major implementations include an insane default CA list*, poor handling of certificates of different trust levels (clever use of redirects can allow interception of form data for an EV site without making the green bar disappear)
Deployment failure: noone looks at the list of CAs and makes an informed descion on what to accept, they just leave it at the software vendors defaults.
but yeah none of these are openssl's fault. By the time they came along the bad descisions had already been made.
* Seriously mozilla why the heck did you include the chineese government.
And you also need them because sometimes your demographic predictions say that a local increase in the number of schoolkids is temporary, or because your demographic predictions were wrong and you need to add capacity quickly.
There is also the question of what will your district look like in a decade or so? will it still be full of families with school-age children? or will it be full of older people whose kids have moved on to a new area?
They could do it the other way arround, make an update to the updater that (among other things) checks more thouroughly what edition of the OS it's running on, then make it so you have to update the updater to get any other updates.
I dunno about the rest of europe but here in the UK car tax for ordinary cars registered since 1 march 2001* is determined from official CO2 emmision figures. The ammount of CO2 that comes out of the exhaust is almost directly proportional to the ammount of carbon in the fuel that goes from the tank to the engine**. I don't know if they directly measure the CO2 or just calculate it from the fuel input but either way it isn't going to make a massive difference.
* Older cars and new cars for which official CO2 figures are not available (scratch built custom cars and such) are taxed based on engine size. Very old cars are classed as historic vehicles and exempt from road tax.
** Carbon that comes out in any form other than CO2 is bad since it represents incomplete combustion and can be a nasty polloutant in it's own right.
By the time I had a client request that function (people can change documents but not delete), it was no longer a possibility.
It's a dumb idea in most cases, usually blanking out a file or replacing it's contents with random garbage is just as bad as deleting it. Maybe worse because it makes people think the file is still there until they look inside.
AIUI with many potential and actual execution drugs complicated production facilities are required and the facilities that exist are sited in countries that are anti-death penalty. This poses a problem, especially as many of those drugs are also useful medically so the USA really doesn't want to be banned from buying them.
OTOH seperation of nitrogen from air is relatively trivial and done all over the world so it's hard for a foreign covernment to ban it.