NASA funded development of the falcon 9 and dragon and are currently funding development of the dragon 2. They are also the largest single buyer of the falcon 9 and the only buyer so far for the dragon capsule.
Customers don't like data limits because they find it hard to understand and control how much data different things use but adding more data capacity to mobile networks is difficult and expensive and once you give a customer an unlimited plan they won't make any attempt to control their data usage.
So this is where things end up. The main data category doesn't have a traffic limit but certain potentially high-traffic activities are either forbidden, throttled or placed in a seperate non-unlimited category.
When mobile phones were first introduced cellular airtime was rather expensive, it's got cheaper over the years but it's still more expensive than delivering a call to a landline.
In the UK at least (I don't know for sure about the rest of Europe but I think it's similar) mobile phones have special phone numbers which usually cost more to call. This pays for the cellular airtime of the person receiving the call so the call is free to the receiver (assuming the reciver is not roaming outside the EU).
In the USA mobile phones have regular phone numbers the same as landline phones. The receiver then pays for their cellular airtime.
Most countries in the EU are also part of the Schengen area. Of those who are not most are "legally required" to join and in the meantime are applying rules based on the Schengen rules. The only countries in the EU with opt-outs from Schengen are the UK and Ireland.
AIUI countries in Schengen are not allowed to negotiate visa-free agreements individually, so it's largely all or nothing for the UK getting visa-free access to mainland EU countries.
First understnad that immigration and customs are separate things. Immigration is about you, customs is about your stuff. The lanes are a customs thing.
First immigration, an EU citizen can show their passport or national ID card (if their country issues them) to border control of any EU country and with very few exceptions they will be let in. Once in they can live and work in the target country without needing to get a visa, work permit or similar. Some non-EU visitors can visit without a visa but they will be subject to limitations on the length and purpose of their stay and may have to convince a border gaurd that they are indeed a legitimate visitor. People from outside the EU wanting to work will need to get a visa and/or work permit (the details vary a bit by country) which can be a long and arduous process.
Then customs, the blue lane is for arrivals from other countries in the EU with nothing to declare. The green line is for arrivals from outside the EU with nothing to declare. The red lane is for travellers with goods to declare. Some countries don't bother with the blue lane and only have red and green lanes. Customs is about goods, so what matters is where you travelled from and what goods you are brining in with you, not your citizenship.
For normal goods* you can take as much as you like between EU countries without any need to declare them regardless of whether it is for personal or commercial use. OTOH if entering from outside the EU you must declare anything above a relatively low threshold and anything that is being imported on a commercial basis. You will then be expected to pay VAT and possibly customs duty.
* There are a handful of exceptions, for example tobacco and alcohol imported commercially (or in sufficiently large volumes that customs belive the imports are commerical).
Sometimes you have to try a design idea in the real world to see the problems with it that aren't apparent at a lab scale. So you make your initial design everything seems good at lab scale, so you push it out to the real world, the cracks then start to show.
Do you have your language evolve to fix the design issues, possibly at the expense of backwards compatibility or do you build up layers of cruft as new stuff is added but the stuff which didn't really work out right sticks around.
Locking out modified firmware takes a little bit of effort. Basically add a signature check to the firmware update mechanisms.
Locking down just the radio settings in question without locking out third party firmware is very difficult. The hardware simply wasn't designed to put a barrier between the router firmware and the radio chips.
No such thing, the first i7's were released until November 2008.
in some instances as fast as a i7 computer from 6 months ago.
That is because the fuckers at Intel slap the i7 brand on damn near everything from low clocked dual-core ultra-mobile parts to high end desktop monsters.
Progress has definitely been slower than in the past and intel's "mainstream first" strategy has left the high end market confused but nevertheless a Broadwell-e i7 will be substantially faster than the corresponding original i7.
Whether you will notice that speed of course depends on what you are using the computer for.
First there are the passive adapters. These will only work if the keyboard actually supports USB but comes with a PS/2 plug. You can usually identify these because they only have one PS/2 socket.
Then there are active adapters which nearly always have two PS/2 sockets. In theory a well-engineered active adapter should work with any PS/2 perhiperal or AT keyboard (the AT and PS/2 keyboards used the same protocol but a different connector). In practice I have found them hit and miss at least when used with KVM switches (I am not an old keyboard fetishist so I don't know how well they work with those). I found the Startech ones better then the no-name generics but they still seem to go crazy from time to time.
Old disk drives space ratings were the usable space because of disk format (FAT) which gave them 720k per side. Those same disks on my Amiga were 880k per side (1.76 meg for a ds dd) because it used a different directory system (hash)
Not quite.
The quoted capacities were the space available after low level formatting but before file system overhead. Earlier floppies were quoted in binary kilobytes while later floppies were quoted in a strange hybrid megabyte (1024000 bytes).
The reason some computers had slightly higher quoted capacities than others was because their vendors decided to use slightly different parameters for the disk controller resulting in different numbers of sectors per track.
The model of separating ordering and fulfilment essentially means they trap the customers. Before someone has paid they can easilly give up, once they have paid they can't easilly give up without losing their money.
For EU/EEA/Swiss citizens the job of border control in a Schengen country is simple. If the passport matches the person and there isn't an alert in an international police database let them in.
For non-EU citizens the job is more complicated. Check they are folloing the rules on time in verses time out using the stamps in the passport (AIUI they don't yet have a database for this though they are talking about creating one). Ask them some questions to assess the risk that they are an illegal immigrant pretending to be a visitor, and finally stamp the passport to record the entry.
The US debt is denominated in US dollars, creation of US dollars is ultimately controlled by the US governement. If the US government wants to "print" it's way out of debt they are free to do so.
The Greek debt is denominated in Euros, creation of Euros is not controlled by greece.
At some point Linux ABI was updated to support files exceeding 2^31 bytes while retaining full backwards compatibility so I I'm not buying insurmountable technical justifications other than simple lack of will.
There does in fact seem to be some progress taking a similar approach to large file suport..
Fixing the kernel is a good step, but isn't enough.
Indeed.
First they need to deal with the kernel, then they need to deal with the libraries, and finally the applications. Trying to do this without breaking existing binaries is hard and right now the benefits of Y2K38 compliance are not seen to exceed the drawbacks of breaking existing binaries.
There are people working quietly in the background to make the Linux kernel and glibc y2K38 compliant, the question is will they get their work completed in time for the distro and application devs to do their bit without a massive panic.
In general the advertised word size of a processor is the data size of the general purpose registers and the largest data size that most regular instructions can work on.
The one reasonablly common exception to this is the results of multiplications. Many processors with hardware multipliers have a multiply instruction where the result is double the size of the arguments and stored into two registers.
Larger additions/subtractions/comparisions can be performed by using a carry flag. Larger multiplications can be performed by a variant of long multiplication. There are ways to do larger divisions too though they get quite copmlex.
In practice what has happened is that "C style" interfaces have become the common point for interoperation between languages.
So you basically if you want to call code written in language A from language B you have to.
1. Wrap the code written in language A in a C style wrapper. 2. Wrap the C style wrapper in language B. 3. Work out how to build/link the resulting project.
This is doable but it's a sufficient PITA that a lot of the time rewriting the code seems more practical.
True you can change the typing of a variable at every assignment
And more importantly you can pass any type to a parameter, store any type in a data structure and so-on.
True when you come to actually do some maths you will probably notice that what was supposed to be a number is not in fact a number. When you come to call a method you will probably notice that your value was not in fact an object of the correct type. You then have to spend ages working backwards to figure out how the value of the wrong type got stored in the data structure in the first place.
(still python is much better than certain other languages where passing a string where a number was expected or a number where a string was expected is likely to blunder on producing broken results)
1. The raspberry pi foundation decided to enable ssh by default on their raspbian image despite a number of us telling them that it was reckless. They eventually back-peddled on this for later images but not before there were loads and loads of existing installations out there. 2. There are still end-user networks out there, particularly in academic settings that are largely open to the internet. 3. They have sold millions of Pis
Put all those together and you have a sufficient pool of Pis out there running ssh servers on the open Internet and accepting a login of pi/raspberry to be worthwhile for script kiddies to target.
You can't do virtual 8086 mode under a "long mode" OS but you can do 16 bit protected mode.
The reason you can't run win16 apps under 64-bit windows is simply because microsoft couldn't be bothered doing the development/debugging work to make wow work on top of wow64. You can run 16 bit windows apps on 32 bit wine on 64-bit linux.
Slashdot Mirror
NASA funded development of the falcon 9 and dragon and are currently funding development of the dragon 2. They are also the largest single buyer of the falcon 9 and the only buyer so far for the dragon capsule.
Customers don't like data limits because they find it hard to understand and control how much data different things use but adding more data capacity to mobile networks is difficult and expensive and once you give a customer an unlimited plan they won't make any attempt to control their data usage.
So this is where things end up. The main data category doesn't have a traffic limit but certain potentially high-traffic activities are either forbidden, throttled or placed in a seperate non-unlimited category.
When mobile phones were first introduced cellular airtime was rather expensive, it's got cheaper over the years but it's still more expensive than delivering a call to a landline.
In the UK at least (I don't know for sure about the rest of Europe but I think it's similar) mobile phones have special phone numbers which usually cost more to call. This pays for the cellular airtime of the person receiving the call so the call is free to the receiver (assuming the reciver is not roaming outside the EU).
In the USA mobile phones have regular phone numbers the same as landline phones. The receiver then pays for their cellular airtime.
apache, postfix and nginx come to mind as common packages that use openssl.
Most countries in the EU are also part of the Schengen area. Of those who are not most are "legally required" to join and in the meantime are applying rules based on the Schengen rules. The only countries in the EU with opt-outs from Schengen are the UK and Ireland.
AIUI countries in Schengen are not allowed to negotiate visa-free agreements individually, so it's largely all or nothing for the UK getting visa-free access to mainland EU countries.
First understnad that immigration and customs are separate things. Immigration is about you, customs is about your stuff. The lanes are a customs thing.
First immigration, an EU citizen can show their passport or national ID card (if their country issues them) to border control of any EU country and with very few exceptions they will be let in. Once in they can live and work in the target country without needing to get a visa, work permit or similar. Some non-EU visitors can visit without a visa but they will be subject to limitations on the length and purpose of their stay and may have to convince a border gaurd that they are indeed a legitimate visitor. People from outside the EU wanting to work will need to get a visa and/or work permit (the details vary a bit by country) which can be a long and arduous process.
Then customs, the blue lane is for arrivals from other countries in the EU with nothing to declare. The green line is for arrivals from outside the EU with nothing to declare. The red lane is for travellers with goods to declare. Some countries don't bother with the blue lane and only have red and green lanes. Customs is about goods, so what matters is where you travelled from and what goods you are brining in with you, not your citizenship.
For normal goods* you can take as much as you like between EU countries without any need to declare them regardless of whether it is for personal or commercial use. OTOH if entering from outside the EU you must declare anything above a relatively low threshold and anything that is being imported on a commercial basis. You will then be expected to pay VAT and possibly customs duty.
* There are a handful of exceptions, for example tobacco and alcohol imported commercially (or in sufficiently large volumes that customs belive the imports are commerical).
Sometimes you have to try a design idea in the real world to see the problems with it that aren't apparent at a lab scale. So you make your initial design everything seems good at lab scale, so you push it out to the real world, the cracks then start to show.
Do you have your language evolve to fix the design issues, possibly at the expense of backwards compatibility or do you build up layers of cruft as new stuff is added but the stuff which didn't really work out right sticks around.
Note that is only one of the co-maintainers and he didn't say it would never happen only he didn't think it should ever happen.
AIUI
Locking down nothing takes no effort.
Locking out modified firmware takes a little bit of effort. Basically add a signature check to the firmware update mechanisms.
Locking down just the radio settings in question without locking out third party firmware is very difficult. The hardware simply wasn't designed to put a barrier between the router firmware and the radio chips.
At least in firefox blue used to mean a DV certificate while green meant an EV certificate. At some point they started using green for everything.
your 10 year old i7
No such thing, the first i7's were released until November 2008.
in some instances as fast as a i7 computer from 6 months ago.
That is because the fuckers at Intel slap the i7 brand on damn near everything from low clocked dual-core ultra-mobile parts to high end desktop monsters.
Progress has definitely been slower than in the past and intel's "mainstream first" strategy has left the high end market confused but nevertheless a Broadwell-e i7 will be substantially faster than the corresponding original i7.
Whether you will notice that speed of course depends on what you are using the computer for.
From the diagrams I have seen the idea is that the sealed train is docked and the passengers and cargo are wheeled out the end.
USB to PS/2 adapters are a mess.
First there are the passive adapters. These will only work if the keyboard actually supports USB but comes with a PS/2 plug. You can usually identify these because they only have one PS/2 socket.
Then there are active adapters which nearly always have two PS/2 sockets. In theory a well-engineered active adapter should work with any PS/2 perhiperal or AT keyboard (the AT and PS/2 keyboards used the same protocol but a different connector). In practice I have found them hit and miss at least when used with KVM switches (I am not an old keyboard fetishist so I don't know how well they work with those). I found the Startech ones better then the no-name generics but they still seem to go crazy from time to time.
Old disk drives space ratings were the usable space because of disk format (FAT) which gave them 720k per side. Those same disks on my Amiga were 880k per side (1.76 meg for a ds dd) because it used a different directory system (hash)
Not quite.
The quoted capacities were the space available after low level formatting but before file system overhead. Earlier floppies were quoted in binary kilobytes while later floppies were quoted in a strange hybrid megabyte (1024000 bytes).
The reason some computers had slightly higher quoted capacities than others was because their vendors decided to use slightly different parameters for the disk controller resulting in different numbers of sectors per track.
The model of separating ordering and fulfilment essentially means they trap the customers. Before someone has paid they can easilly give up, once they have paid they can't easilly give up without losing their money.
For EU/EEA/Swiss citizens the job of border control in a Schengen country is simple. If the passport matches the person and there isn't an alert in an international police database let them in.
For non-EU citizens the job is more complicated. Check they are folloing the rules on time in verses time out using the stamps in the passport (AIUI they don't yet have a database for this though they are talking about creating one). Ask them some questions to assess the risk that they are an illegal immigrant pretending to be a visitor, and finally stamp the passport to record the entry.
The big difference between Greece and the USA is.
The US debt is denominated in US dollars, creation of US dollars is ultimately controlled by the US governement. If the US government wants to "print" it's way out of debt they are free to do so.
The Greek debt is denominated in Euros, creation of Euros is not controlled by greece.
At some point Linux ABI was updated to support files exceeding 2^31 bytes while retaining full backwards compatibility so I I'm not buying insurmountable technical justifications other than simple lack of will.
There does in fact seem to be some progress taking a similar approach to large file suport..
https://sourceware.org/glibc/w...
https://github.com/3adev/y2038
https://gitlab.com/bminor/glib...
If/when it will be completed/merged I do not know.
Fixing the kernel is a good step, but isn't enough.
Indeed.
First they need to deal with the kernel, then they need to deal with the libraries, and finally the applications. Trying to do this without breaking existing binaries is hard and right now the benefits of Y2K38 compliance are not seen to exceed the drawbacks of breaking existing binaries.
There are people working quietly in the background to make the Linux kernel and glibc y2K38 compliant, the question is will they get their work completed in time for the distro and application devs to do their bit without a massive panic.
From what I can find that only appears to be for windows server, not windows desktop.
In general the advertised word size of a processor is the data size of the general purpose registers and the largest data size that most regular instructions can work on.
The one reasonablly common exception to this is the results of multiplications. Many processors with hardware multipliers have a multiply instruction where the result is double the size of the arguments and stored into two registers.
Larger additions/subtractions/comparisions can be performed by using a carry flag. Larger multiplications can be performed by a variant of long multiplication. There are ways to do larger divisions too though they get quite copmlex.
In practice what has happened is that "C style" interfaces have become the common point for interoperation between languages.
So you basically if you want to call code written in language A from language B you have to.
1. Wrap the code written in language A in a C style wrapper.
2. Wrap the C style wrapper in language B.
3. Work out how to build/link the resulting project.
This is doable but it's a sufficient PITA that a lot of the time rewriting the code seems more practical.
True you can change the typing of a variable at every assignment
And more importantly you can pass any type to a parameter, store any type in a data structure and so-on.
True when you come to actually do some maths you will probably notice that what was supposed to be a number is not in fact a number. When you come to call a method you will probably notice that your value was not in fact an object of the correct type. You then have to spend ages working backwards to figure out how the value of the wrong type got stored in the data structure in the first place.
(still python is much better than certain other languages where passing a string where a number was expected or a number where a string was expected is likely to blunder on producing broken results)
The problem is threefold.
1. The raspberry pi foundation decided to enable ssh by default on their raspbian image despite a number of us telling them that it was reckless. They eventually back-peddled on this for later images but not before there were loads and loads of existing installations out there.
2. There are still end-user networks out there, particularly in academic settings that are largely open to the internet.
3. They have sold millions of Pis
Put all those together and you have a sufficient pool of Pis out there running ssh servers on the open Internet and accepting a login of pi/raspberry to be worthwhile for script kiddies to target.
You can't do virtual 8086 mode under a "long mode" OS but you can do 16 bit protected mode.
The reason you can't run win16 apps under 64-bit windows is simply because microsoft couldn't be bothered doing the development/debugging work to make wow work on top of wow64. You can run 16 bit windows apps on 32 bit wine on 64-bit linux.