Giga * means 1 billion whether it is bits or bytes stored in ram, on disk or sent over a network is wholly irrelevant.
There is an easy answer for anyone still confused about this in the year 2013..insert a lowercase "i" after G. (e.g. GiB) and tada all of your ambiguities + 11" subway lawsuits melt away.
Unless you're trying to get PCI compliance, in which case expect to be told that mitigating BEAST attacks isn't good enough, you need to not be vulnerable to them at all!
Is this the same PCI that asserts "secure" hash algorithms can be used to tokenize credit card numbers?
Why are idiots even allowed to write security specifications and why do the rest of us tolerate it?
Advertisements for a cool new smartphone OS do not revolve around cloud, tweets, facebook, and slews of neatly bundled commercial services and integrated local/web search.
A real OS would provide a packaging option that included coming installed with nothing not even a phone dialer or SMS app. It should just focus on providing facilities to allow secure, effective communication and integration between apps and the users workflow. It should NOT define what that will be apriori.
The reason we don't have any good smartphone OS's is because too much value would be left on the table if one were to be designed where the user comes first and the value chain comes second. Ubuntu is being corrupted by its own success.
Switching browsers to FF version 19 trillion not made by MS... ah I see it now but I can't click on anything at all not even the navigational links at the top of the screen...nothing.
Switching browsers aga... on second thought screw that. I hope you took it out of beta cause you realized alpha comes *before* beta. This site is totally broken.
You can't just be angry at the messages coming out of this crazy factory. You have to be angry at institutional structures encouraging the lunacy coming out of these boards on a seemingly daily basis.
Or you can just buy 60ghz gear off the shelf today. The antennas are tiny, provides several gbits per device regardless of the number of devices. It has all of the same properties as visible light except you won't be destracted by it if you don't want the damn lights on.
I am constantly amused by those who sit around dreaming up reasons not to do something.
The two substantive arguments are nuclear is not an option because the world lacks material to build enough nuclear plants. It may not be an appealing option for other reasons but this aint one of them. When the cost of materials go up more money is allocated to increasing production. One need only look to the shale shit being stuffed into our refinaries and ultra deep oil wells being dug at enormous cost to see where there is a will and enough money on the line shit gets done.
The other argument is essentially a grade school lecture on compound interest taken to illogical absurdity.
First worlds per capita energy use is DECLINING due to efficiency gains. Aggregate growth rates are due to the rise of the rest with global population leveling off there is no reason to expect continued exponential growth of anything resembling infinity and beyond. The number of new people is a rounding error in terms of consumption due to the rise of living standards of everyone else.
Most of Australia is a sparsely populated desert at 1GW km^2 don't give me shit about there not being enough sunlight even if you can only get half of that out with a solar tower and only for a few hours a day.
At 1GW per KM^2 and millions of KM^2 of land area in Australia assume 10 KM^2 is needed per GW to account for effeciency and time of day.
Australia consumes about 190 GW.
You would need collectors of an area of 1900 KM^2... this is a massive area but still constitutes only %0.025 percent of the total land area of Australia.
"The fact is that Python today is taking over where Perl would have dominated in the past. "
And the reason for that is that python has equivalent functionality to perl (unless you really need to compose an entire program in 1 line of regexp and a loop), can also be used for quick-n-dirty tasks but is actually readable and structured and while its OO system isn't perfect its a damn site better than the nailed on dogs dinner that is Perls.
Python and Perl were both released in the late 80's. It is now 2013. As far back as I can remember from the mid 90's people were making these same arguments for Python being more readable and OOIsh. CS departments even then were pushing Python while ignoring perl.
Did something meaningful between Perl and Python change recently or are these essentially the same observations and arguments from 20 years ago?
9/11 comparisons and DoD goons routinely discussing threat from cyber war in terms of parity with nuclear weapons is quite amusing like comparing getting detention with being sent off to a Nazi concentration camp.
Asserting the age old problem of "espionage" is now "cyber" and dreaming up of doomsday scenarios which leave even braindead zombies asking the obvious question how hard is it really to keep "critical infustructure" off the Internet?
I have little doubt real intent of this media blitz and TLA warnings are to create an atmosphere conducive to tolerating government overreach. Overreach which cannot possibly work to accomplish better security for anyone.
If the government really cared about US infustructure being hacked via Internet they would find a legal framework making hacking against every government/public target without any restriction legal by US citizens with some rules against lame attacks (ddos) and intentional non-collateral damage.
Penalize agencies that get 0wn3d. Make it a huge game (with cash prizes) focus on educational resources to help and encourage hacking. Not only do you get better infustructure you get more knowledgable peeps.
the problem is that windows is already losing the app race.
I wish the marketeers would make up their mind. First it was apps, then it was thin clients/web sites, now it is apps, tomorrow angry birds will only run from the browser and the day after that it will be an app again except you will have to pay for each minute of play.
touch is an advantage only if you have the app for it, and all the good developer/ideas are committed to either ios/android
It's only a matter of time before platform islands begin to evaporate. There is just too much value locked up and accumulating on each island for this status quot to be maintainable on all of these locked down mobile devices. When it does the operating system will trend back to being a commodity as it should be before the rise of these crappy vendor locked down walled gardens.
forcing the windows 8 ready badge to be obtained only trough supporting metro and resolution independent touch device isn't a bad move - per se - given the context.
Quite meaningless when nobody cares.
even the cool kids, as chrome, do it completely wrong (I am typing on a bootcamped macbook retina with windows 8 at 200dpi right now)
I can live with people having different preferences of hardware and software. I can live with fanboys and lemmings. I can even live with the marketeers who wisper into our ears sweet tales of "new things" we ought to be liking.
What I simply cannot stand is sent from my (insert platform here) posters being plastered all over the place. Nobody gives a shit what you are using to compose your message.
- Torn or irritated rotator cuff injuries - Back pain from disproportional development of upper arm musculature (gorilla arm syndrome) - Elbow tendonitis - Fatigue
Apparently this is a much larger problem than we all thought
I recall myself and others on slashdot making this very prediction the act of repetitivly pressing upon a solid mass with no give for hours upon hours a day would make carpel tunnel look like getting a splinter.
How many people call and ask for IPv6? That 0.01% who are technical and who care?
Again I think it depends on who you are. If you are a business. If you are one of countless millions running a web site and ask about IPv6 because you want to offer the best experience to all customers this will have a measurable impact on the (in)actions of the ISP. If it is just a megaco access network your right it makes no difference.
As for RFPs... sadly people ask for many things when they provide requirements, but do not quite use them.
I don't give a shit if they use it or not. I just want to win. If checking yes in that box give me an advantage over someone who checks no thats all I care about.
You also depend on what _others_ do, and if there is a lot of content available only over IPv4 you still need a CGN in one form or another. Luckily Google, Youtube and some other large content providers have already made the right thing and switched IPv6 on.
Well - the main question that comes to my mind is: how are you going to migrate users from iv4 to ipv6?
The question at hand is how are you going to give users IPv6 in addition to IPv4 they already have.
I am talking about regular users who have four or five devices at home that connect to a dsl router at home either with Ethernet cable and/or Wifi. All using ipv4.
The IPv4 only router/NAT device either becomes obsolete or breaks and is replaced with a new one.
Every IPv6 capable thing on the broadcast domain of the customer router now has IPv6 without having to make changes or exert effort specific to IPv6.
Is somebody from the isp going to visit every customer and migrate them to ipv6?
Some plan to yet halflife of these devices is only a few years. There is not much to be gained in being overly aggressive in this regard. It is a statistical game. The faster you drive the more it costs for ever diminishing results.
Old technology will cycle out naturally on its own then remaining holdouts can be addressed with reasonable expendatures.
There have been various technology changes in the past requiring ISPs to draw a line in a sand and obsolete certain classes of CPEs. For example many ISPs won't allow docsis 1 era equipment on their network as it prevents them from requiring more secure BPI modes.
And don't mention tunneling and dual stack and all that stuff. That's not gonna do it for regular users, who simply turn on their laptop, desktop and smartphone and they simply get connected to the internet using ipv4 dhcp from the dsl router.
Dualstack IPv4 and IPv6 is the most generally accepted and widely deployed plan to get regular users access to the entire Internet (IPv4 and IPv6) with the least inconvinence and no breakage of existing applications.
Once a customer router is advertising IPv6 RA's to the network all IPv6 capable laptops, phones, tablets, game consoles or whatever get IPv6.
NK's little kingdom of retards is run entirely by fear and has a sell by date. Not everyone is a brainwashed tool of the state. Policy should be to offer a counterweight to NK propoganda thru all possible modes of communication.
Games use a client server model not a peer to peer model. A game server listens on a port for incoming requests from a client. All client to client interactions are server mediated.
things like Skype
If you count having to operate an army of supernode servers and routing calls thru strangers machines just because some sizable portion of users lack the necessary connectivity to establish an end-end session then yes Skype just "works".
This article was totally lacking in any useful facts about why CGN (Carrier Grade NAT) won't work just fine.
From quotes mentioning lots and lots of testing it sounds to me they are afraid of breakage and unhappy customers.
Frankly, your ISP doesn't care that much about you, because you're not the vast majority of their user base. People who have even *heard* the terms "IPv4" and IPv6" are probably less than 1% of their customers.
I think it depends on who you are. If you are just a residential customer getting service from megaco regardless of what your gripe is the sentiment is fairly universal.
Small ISPs on the other hand care about every customer especially if you happen to have a business account. It only takes a few such calls to light necessary fires.
The larger ones.. the ones who can afford to not care about their customers are paradoxically the ones currently much further along deploying IPv6.
As you wrote - each of ISPs mentioned in the article says in one way or the other that CGN is a neccessity.
Most also say they have no immediate plans to deploy CGN as sufficient IPv4 address space is available within their allocations.
Every last one of them have already or are in process of deploying IPv6.
Problem with IPv6 is that the business case is weak.
Q. Hello, I am Interested in Internet service, do you offer IPv6?
A. No, there is no business case for us to do so.
Q. Thanks for your time....click.
For me this is already reality today. Every RFP without exception we have participated in last 3 years either required or asked about IPv6.
ISPs have to spend money upgrading to IPv6 without offering anything new to get more income from subscribers.
CGN and "pay more for a public IPv4" is, sadly, one of such cases that is likely to go forward
This was never about providing anything "new" it is about getting to *continue* to provide the same level of service.
CGN costs more not only in terms of hardware it costs in customer support and administrative resources required to manage the system vs dumb packet punters.
As an ISP the less CGN you need the less you spend. The more IPv6 you deploy the less CGN you need.
Most US homes will have a choice of one or two providers. DSL from the phone company and cable.
While the cable scene is as you describe DSL is open to competition by independent ISPs. Telco provides last mile circuit and ISP provides Internet connectivity thru telco ATM cloud.
It may not be advertised as heavily or known to most people as an option but it is there in many areas.
For example, a struct stat contains several time_t values; if the size of time_t changes, the layout of that structure changes, and a program that calls stat() passing it a structure with the layout for 32-bit time_t will not work very well if stat() fills in a structure with the layout for 64-bit time_t.
Everyone is spending all of this time telling me why it can't be done without regard for the history of how these exact same issues have been addressed in the past.
When we call stat() it is not really even stat anymore. It is more like stat64 and the stat structure is really stat64. It is all just preprocessor aliases in a header file.
There is no reason the same thing can't be done with time_t.
This doesn't change the ABI for existing routines, although it does introduce new routines to the ABI.
Yes, absolutely. You will need a new round of functions for anything with time_t in it.
Unixland works differently; "system APIs" do use time_t, so either you'd have to statically link with the libraries that provide those ABIs
You update libraries with new round of functions. All previous software still works. New programs only work with the new set of libraries and won't run on older versions of the runtime libraries.
And, unless there's some reason to expect people to care about running 32-bit versions of your application at a time when they need a 64-bit time_t, or you don't have the resources to make your application work in 64-bit mode, you might just want to ship a 64-bit version and be done with it
There are still lots of 32-bit processors in the world..and lots of new ones being built each day which also can never run 64-bit linux. Arch files for currently largly non-existant 64-bit arm chips to even work didn't even exist until just very recently.
As myself and others have mentioned we don't really have 25 years unless none of our applications do any processing into the future. Anything dealing with dates for contracts, licensing, event scheduling..etc.etc. will have to care about these issues sooner than 25 years.
I don't see the position of 64-bit linux required for 64-bit time_t being any more valid than saying 64-bit linux is required for 64-bit file addressing. They are orthagonal issues.
KDE's gadgets are not windows 7 knock-offs. You got that backwards
I saw them in old longhorn betas long before kde had them in '05. What I was amused by specifically was config tool dialouge..I swear the behavior and icons are pixel for pixel identical.
Software raid? Not sure it ever was a real priority in linux-land, otoh, it might be a case of confirmation bias. You do seem like a windows guy.
I don't understand why this is not a priority? Do people not mirror their servers to increase uptime? If your not juggling parity there is no measurable overhead and no reason to spend money on unecessary hardware.
Is everyone expected to have hardware array controllers and fancy SANs?
Limited selection, right.. did you look? There's more than I can get a handle on, especially if you start looking at the latex/postscript ones.
From distro perspective selection out of the box is poor.
Fedora. You were doing quite well, but in the end you confused Fedora with "Linux". I guess that's your mistake. That's why you went with it to begin with, and that's why you confuse the state of Fedora with the general state of "Linux".
The ABI has to change to change the datatype of time_t.
Does not.
And that will magically cause all existing binaries (the "B" in "ABI") to be recompiled to have a 64-bit time_t?
I assume this is rhetorical.
If not, then, at least for dynamically-linked binaries, changing the size of time_t, and shipping systems with 32-bit system libraries that expect time_t to be 64-bit, will break binary compatibility.
This is where the "compiler switch" comes in. If I want 64-bit time_t on a 32-bit platform I have that option and I know what else I need to do to make it work.
time_t was 32-bits on windows until Microsoft updated their compiler to make it 64-bits without breaking compatibility. There is no reason other than lack of will the same can't be done on the linux platform.
It wouldn't be the first time either I seem to recall I/O being updated to address files larger than 2^31 bytes. Old applications still have the limit. New applications or old recompiled applications magically get to address larger files.
If not, then, at least for dynamically-linked binaries, changing the size of time_t, and shipping systems with 32-bit system libraries that expect time_t to be 64-bit, will break binary compatibility.
It will also be incompatible with network protocols and persistant storage which assume 32-bit storage of this field. None of this is a valid excuse for lack of action.
30-40 percent of all Internet traffic in the US is already Netflix. Those of us who don't download countless gigabytes each month are already subsidising the activities of heavier users. It has always been this way for the most part from the very beginning.
What concerns me more is the prospect of a network where what you can do depends on your ISP rather than just the size of ur pipe. LOL...
Slashdot Mirror
Offer them a bigass high contrast partially erasable boogie board with a save chalkboard option. Not exactly high tech but beats markers or chalk.
Giga * means 1 billion whether it is bits or bytes stored in ram, on disk or sent over a network is wholly irrelevant.
There is an easy answer for anyone still confused about this in the year 2013..insert a lowercase "i" after G. (e.g. GiB) and tada all of your ambiguities + 11" subway lawsuits melt away.
Unless you're trying to get PCI compliance, in which case expect to be told that mitigating BEAST attacks isn't good enough, you need to not be vulnerable to them at all!
Is this the same PCI that asserts "secure" hash algorithms can be used to tokenize credit card numbers?
Why are idiots even allowed to write security specifications and why do the rest of us tolerate it?
Advertisements for a cool new smartphone OS do not revolve around cloud, tweets, facebook, and slews of neatly bundled commercial services and integrated local/web search.
A real OS would provide a packaging option that included coming installed with nothing not even a phone dialer or SMS app. It should just focus on providing facilities to allow secure, effective communication and integration between apps and the users workflow. It should NOT define what that will be apriori.
The reason we don't have any good smartphone OS's is because too much value would be left on the table if one were to be designed where the user comes first and the value chain comes second. Ubuntu is being corrupted by its own success.
All I see is a loading bar cycling endlessly...
Switching browsers to FF version 19 trillion not made by MS... ah I see it now but I can't click on anything at all not even the navigational links at the top of the screen...nothing.
Switching browsers aga... on second thought screw that. I hope you took it out of beta cause you realized alpha comes *before* beta. This site is totally broken.
Wired ethernet is faster and more reliable.. just sayin...
"I believe my response would be go to Hell. "
You can't just be angry at the messages coming out of this crazy factory. You have to be angry at institutional structures encouraging the lunacy coming out of these boards on a seemingly daily basis.
Or you can just buy 60ghz gear off the shelf today. The antennas are tiny, provides several gbits per device regardless of the number of devices. It has all of the same properties as visible light except you won't be destracted by it if you don't want the damn lights on.
I am constantly amused by those who sit around dreaming up reasons not to do something.
The two substantive arguments are nuclear is not an option because the world lacks material to build enough nuclear plants. It may not be an appealing option for other reasons but this aint one of them. When the cost of materials go up more money is allocated to increasing production. One need only look to the shale shit being stuffed into our refinaries and ultra deep oil wells being dug at enormous cost to see where there is a will and enough money on the line shit gets done.
The other argument is essentially a grade school lecture on compound interest taken to illogical absurdity.
First worlds per capita energy use is DECLINING due to efficiency gains. Aggregate growth rates are due to the rise of the rest with global population leveling off there is no reason to expect continued exponential growth of anything resembling infinity and beyond. The number of new people is a rounding error in terms of consumption due to the rise of living standards of everyone else.
Most of Australia is a sparsely populated desert at 1GW km^2 don't give me shit about there not being enough sunlight even if you can only get half of that out with a solar tower and only for a few hours a day.
At 1GW per KM^2 and millions of KM^2 of land area in Australia assume 10 KM^2 is needed per GW to account for effeciency and time of day.
Australia consumes about 190 GW.
You would need collectors of an area of 1900 KM^2... this is a massive area but still constitutes only %0.025 percent of the total land area of Australia.
"The fact is that Python today is taking over where Perl would have dominated in the past. "
And the reason for that is that python has equivalent functionality to perl (unless you really need to compose an entire program in 1 line of regexp and a loop), can also be used for quick-n-dirty tasks but is actually readable and structured and while its OO system isn't perfect its a damn site better than the nailed on dogs dinner that is Perls.
Python and Perl were both released in the late 80's. It is now 2013. As far back as I can remember from the mid 90's people were making these same arguments for Python being more readable and OOIsh. CS departments even then were pushing Python while ignoring perl.
Did something meaningful between Perl and Python change recently or are these essentially the same observations and arguments from 20 years ago?
9/11 comparisons and DoD goons routinely discussing threat from cyber war in terms of parity with nuclear weapons is quite amusing like comparing getting detention with being sent off to a Nazi concentration camp.
Asserting the age old problem of "espionage" is now "cyber" and dreaming up of doomsday scenarios which leave even braindead zombies asking the obvious question how hard is it really to keep "critical infustructure" off the Internet?
I have little doubt real intent of this media blitz and TLA warnings are to create an atmosphere conducive to tolerating government overreach. Overreach which cannot possibly work to accomplish better security for anyone.
If the government really cared about US infustructure being hacked via Internet they would find a legal framework making hacking against every government/public target without any restriction legal by US citizens with some rules against lame attacks (ddos) and intentional non-collateral damage.
Penalize agencies that get 0wn3d. Make it a huge game (with cash prizes) focus on educational resources to help and encourage hacking. Not only do you get better infustructure you get more knowledgable peeps.
the problem is that windows is already losing the app race.
I wish the marketeers would make up their mind. First it was apps, then it was thin clients/web sites, now it is apps, tomorrow angry birds will only run from the browser and the day after that it will be an app again except you will have to pay for each minute of play.
touch is an advantage only if you have the app for it, and all the good developer/ideas are committed to either ios/android
It's only a matter of time before platform islands begin to evaporate. There is just too much value locked up and accumulating on each island for this status quot to be maintainable on all of these locked down mobile devices. When it does the operating system will trend back to being a commodity as it should be before the rise of these crappy vendor locked down walled gardens.
forcing the windows 8 ready badge to be obtained only trough supporting metro and resolution independent touch device isn't a bad move - per se - given the context.
Quite meaningless when nobody cares.
even the cool kids, as chrome, do it completely wrong (I am typing on a bootcamped macbook retina with windows 8 at 200dpi right now)
I can live with people having different preferences of hardware and software. I can live with fanboys and lemmings. I can even live with the marketeers who wisper into our ears sweet tales of "new things" we ought to be liking.
What I simply cannot stand is sent from my (insert platform here) posters being plastered all over the place. Nobody gives a shit what you are using to compose your message.
- Torn or irritated rotator cuff injuries
- Back pain from disproportional development of upper arm musculature (gorilla arm syndrome)
- Elbow tendonitis
- Fatigue
Apparently this is a much larger problem than we all thought
I recall myself and others on slashdot making this very prediction the act of repetitivly pressing upon a solid mass with no give for hours upon hours a day would make carpel tunnel look like getting a splinter.
User-agent: *
Disallow: /
How many people call and ask for IPv6?
That 0.01% who are technical and who care?
Again I think it depends on who you are. If you are a business. If you are one of countless millions running a web site and ask about IPv6 because you want to offer the best experience to all customers this will have a measurable impact on the (in)actions of the ISP. If it is just a megaco access network your right it makes no difference.
As for RFPs... sadly people ask for many things when they provide requirements, but do not quite use them.
I don't give a shit if they use it or not. I just want to win. If checking yes in that box give me an advantage over someone who checks no thats all I care about.
You also depend on what _others_ do, and if there is a lot of content available only over IPv4 you still need a CGN in one form or another.
Luckily Google, Youtube and some other large content providers have already made the right thing and switched IPv6 on.
Absolutely.
Well - the main question that comes to my mind is: how are you going to migrate users from iv4 to ipv6?
The question at hand is how are you going to give users IPv6 in addition to IPv4 they already have.
I am talking about regular users who have four or five devices at home that connect to a dsl router at home either with Ethernet cable and/or Wifi. All using ipv4.
The IPv4 only router/NAT device either becomes obsolete or breaks and is replaced with a new one.
Every IPv6 capable thing on the broadcast domain of the customer router now has IPv6 without having to make changes or exert effort specific to IPv6.
Is somebody from the isp going to visit every customer and migrate them to ipv6?
Some plan to yet halflife of these devices is only a few years. There is not much to be gained in being overly aggressive in this regard. It is a statistical game. The faster you drive the more it costs for ever diminishing results.
Old technology will cycle out naturally on its own then remaining holdouts can be addressed with reasonable expendatures.
There have been various technology changes in the past requiring ISPs to draw a line in a sand and obsolete certain classes of CPEs. For example many ISPs won't allow docsis 1 era equipment on their network as it prevents them from requiring more secure BPI modes.
And don't mention tunneling and dual stack and all that stuff. That's not gonna do it for regular users, who simply turn on their laptop, desktop and smartphone and they simply get connected to the internet using ipv4 dhcp from the dsl router.
Dualstack IPv4 and IPv6 is the most generally accepted and widely deployed plan to get regular users access to the entire Internet (IPv4 and IPv6) with the least inconvinence and no breakage of existing applications.
Once a customer router is advertising IPv6 RA's to the network all IPv6 capable laptops, phones, tablets, game consoles or whatever get IPv6.
NK's little kingdom of retards is run entirely by fear and has a sell by date. Not everyone is a brainwashed tool of the state. Policy should be to offer a counterweight to NK propoganda thru all possible modes of communication.
As you can see today, lots of games
Games use a client server model not a peer to peer model. A game server listens on a port for incoming requests from a client. All client to client interactions are server mediated.
things like Skype
If you count having to operate an army of supernode servers and routing calls thru strangers machines just because some sizable portion of users lack the necessary connectivity to establish an end-end session then yes Skype just "works".
This article was totally lacking in any useful facts about why CGN (Carrier Grade NAT) won't work just fine.
From quotes mentioning lots and lots of testing it sounds to me they are afraid of breakage and unhappy customers.
Frankly, your ISP doesn't care that much about you, because you're not the vast majority of their user base. People who have even *heard* the terms "IPv4" and IPv6" are probably less than 1% of their customers.
I think it depends on who you are. If you are just a residential customer getting service from megaco regardless of what your gripe is the sentiment is fairly universal.
Small ISPs on the other hand care about every customer especially if you happen to have a business account. It only takes a few such calls to light necessary fires.
The larger ones.. the ones who can afford to not care about their customers are paradoxically the ones currently much further along deploying IPv6.
As you wrote - each of ISPs mentioned in the article says in one way or the other that CGN is a neccessity.
Most also say they have no immediate plans to deploy CGN as sufficient IPv4 address space is available within their allocations.
Every last one of them have already or are in process of deploying IPv6.
Problem with IPv6 is that the business case is weak.
Q. Hello, I am Interested in Internet service, do you offer IPv6?
A. No, there is no business case for us to do so.
Q. Thanks for your time....click.
For me this is already reality today. Every RFP without exception we have participated in last 3 years either required or asked about IPv6.
ISPs have to spend money upgrading to IPv6 without offering anything new to get more income from subscribers.
CGN and "pay more for a public IPv4" is, sadly, one of such cases that is likely to go forward
This was never about providing anything "new" it is about getting to *continue* to provide the same level of service.
CGN costs more not only in terms of hardware it costs in customer support and administrative resources required to manage the system vs dumb packet punters.
As an ISP the less CGN you need the less you spend. The more IPv6 you deploy the less CGN you need.
Most US homes will have a choice of one or two providers. DSL from the phone company and cable.
While the cable scene is as you describe DSL is open to competition by independent ISPs. Telco provides last mile circuit and ISP provides Internet connectivity thru telco ATM cloud.
It may not be advertised as heavily or known to most people as an option but it is there in many areas.
For example, a struct stat contains several time_t values; if the size of time_t changes, the layout of that structure changes, and a program that calls stat() passing it a structure with the layout for 32-bit time_t will not work very well if stat() fills in a structure with the layout for 64-bit time_t.
Everyone is spending all of this time telling me why it can't be done without regard for the history of how these exact same issues have been addressed in the past.
When we call stat() it is not really even stat anymore. It is more like stat64 and the stat structure is really stat64. It is all just preprocessor aliases in a header file.
There is no reason the same thing can't be done with time_t.
This doesn't change the ABI for existing routines, although it does introduce new routines to the ABI.
Yes, absolutely. You will need a new round of functions for anything with time_t in it.
Unixland works differently; "system APIs" do use time_t, so either you'd have to statically link with the libraries that provide those ABIs
You update libraries with new round of functions. All previous software still works. New programs only work with the new set of libraries and won't run on older versions of the runtime libraries.
And, unless there's some reason to expect people to care about running 32-bit versions of your application at a time when they need a 64-bit time_t, or you don't have the resources to make your application work in 64-bit mode, you might just want to ship a 64-bit version and be done with it
There are still lots of 32-bit processors in the world..and lots of new ones being built each day which also can never run 64-bit linux. Arch files for currently largly non-existant 64-bit arm chips to even work didn't even exist until just very recently.
As myself and others have mentioned we don't really have 25 years unless none of our applications do any processing into the future. Anything dealing with dates for contracts, licensing, event scheduling..etc.etc. will have to care about these issues sooner than 25 years.
I don't see the position of 64-bit linux required for 64-bit time_t being any more valid than saying 64-bit linux is required for 64-bit file addressing. They are orthagonal issues.
KDE's gadgets are not windows 7 knock-offs. You got that backwards
I saw them in old longhorn betas long before kde had them in '05. What I was amused by specifically was config tool dialouge..I swear the behavior and icons are pixel for pixel identical.
Software raid? Not sure it ever was a real priority in linux-land, otoh, it might be a case of confirmation bias. You do seem like a windows guy.
I don't understand why this is not a priority? Do people not mirror their servers to increase uptime? If your not juggling parity there is no measurable overhead and no reason to spend money on unecessary hardware.
Is everyone expected to have hardware array controllers and fancy SANs?
Limited selection, right.. did you look?
There's more than I can get a handle on, especially if you start looking at the latex/postscript ones.
From distro perspective selection out of the box is poor.
Fedora. You were doing quite well, but in the end you confused Fedora with "Linux". I guess that's your mistake. That's why you went with it to begin with, and that's why you confuse the state of Fedora with the general state of "Linux".
Pure specious nonsense.
The ABI has to change to change the datatype of time_t.
Does not.
And that will magically cause all existing binaries (the "B" in "ABI") to be recompiled to have a 64-bit time_t?
I assume this is rhetorical.
If not, then, at least for dynamically-linked binaries, changing the size of time_t, and shipping systems with 32-bit system libraries that expect time_t to be 64-bit, will break binary compatibility.
This is where the "compiler switch" comes in. If I want 64-bit time_t on a 32-bit platform I have that option and I know what else I need to do to make it work.
time_t was 32-bits on windows until Microsoft updated their compiler to make it 64-bits without breaking compatibility. There is no reason other than lack of will the same can't be done on the linux platform.
It wouldn't be the first time either I seem to recall I/O being updated to address files larger than 2^31 bytes. Old applications still have the limit. New applications or old recompiled applications magically get to address larger files.
If not, then, at least for dynamically-linked binaries, changing the size of time_t, and shipping systems with 32-bit system libraries that expect time_t to be 64-bit, will break binary compatibility.
It will also be incompatible with network protocols and persistant storage which assume 32-bit storage of this field. None of this is a valid excuse for lack of action.
30-40 percent of all Internet traffic in the US is already Netflix. Those of us who don't download countless gigabytes each month are already subsidising the activities of heavier users. It has always been this way for the most part from the very beginning.
What concerns me more is the prospect of a network where what you can do depends on your ISP rather than just the size of ur pipe. LOL...