And if you bothered to look at what's in sysv-rc, you'd understand the "dep:". It's what created all the rc.d directories, rcS script, and rc script that actually enumerates and calls the rc.d scripts, and on various systems include the helper scripts update-rc.d and invoke-rc.d. Yes, you can run a system without it. But you'll be replacing it with almost exactly the same shell loop to process rc.d scripts, so why bother? (*cough*file-rc*cough* which is historically how BSD does things)
While we're on this horse... rcS is what calls all the scripts dropped by the initscripts package. (the equiv of a redhat rc.sysinit split into a bunch of files)
... or why AT&T couldn't tell what was what when he called. A call from local media, and the whole thing is figured out in seconds??? If it was "long distance", there'd be line items (i.e. each. individual. call.) on that bill.
Exactly. If there's a bug, fix it. Forcing me to "upgrade" to the next release (which may never be available for a particular device) is NOT the answer.
5.0 (and 5.1) have low adoption numbers because many people (me included) simply don't want that shit. I hate the new UI, and refuse to use any of the "new and more like facebook than ever" 5.0 gapps.
Aluminium is not found in a raw state in nature. It's an oxide ore that requires a fantastic amount of power to extract the metal. (i.e. break the O2 away so Mg has somewhere to go.) The sand used for glass, is pretty much right out of the dessert. (very little effort is put into splitting the Si from the O2)
Adding someone to a circle doesn't magically give me permission to see their NON-PUBLIC posts. Plus, you can block anyone, and they won't see any of your posts. This is no different than facebook.
The entire problem was that it wasn't different from FB. G+ was just one in a long line of attempts to be facebook; and forcing everyone to "use" G+ certainly didn't make them any friends. So, the choice is Facebook By Facebook -- a system that's been around for a long time with relatively little change, or Facebook by Google -- who is well know for chucking things under the bus. Gee, surprise! Google's chucking G+ under the bus. Google simply cannot. leave. things. alone.
No, they aren't. Goggle is a bunch of f'ing children with the attention span of a 1yo in a room full of shinny things. They lack any vision, want every thing to look and function like Facebook (*cough*gmail*cough*), and constantly change shit that works and people ("the user") like because ooooo shinny.
Maybe. But if they're still there (and that's a big IF given the growing lameness of their products), they're chained in a cave deep under the Marketing Department tower.
With C and C++, the programmer has to keep up with it; thus they are constantly aware of memory usage. (well, those that aren't complete shits do.) In Java, the programmer has no say in it, so they don't think about it -- or for younger "programmers" (who may have never learned C/C++), don't know how.
You've obviously not work in the Real World(tm). Companies will continue using hardware as long as it works -- not broken, don't need new features/functions not possible through software update(s), or don't need additional capacity (based on space and/or power)
(Cell providers cycle through tech due to the last two.)
How the hell do you summarize two distant/56's out of some other provider's "non-portable"/32? Yes, the ISP ("owner" of the/32) will announce only the entire block. No other piece of that block should exist anywhere outside the ISP's network.
We've allowed that bullshit in IPv4 for decades. The potential size that represents within IPv6 means it must be absolutely FORBIDDEN, from day one until the end of days.
RA, aka. ICMP router advertisement. Abandoned circa 1970 as a "bad idea". It was a colossally bad idea in the 90's, and f'ing suicidally bad in 2000+. Yeah, let's trust whoever the f*** on the cable claims to be a router and send it our traffic. Oh, to protect my network(s) from that brain damage, I have to buy new switches that support "RA Guard".
They didn't like DHCP. So "no f***ing DHCP in IPv6!" DHCPv6 is a bolt-on, staple-on, and bandaid addition to IPv6. It's a horribly incomplete shadow of DHCPv4, and still requires an RA tell you to use it.
SLAAC... originally 80bit prefix plus 48bit MAC. They ignored the fact that ethernet is not the only technology in the universe. That was later amended (breaking older stacks) to 64bits. The entire purpose for the vast over-simplification of address selection (for tiny embeded systems with limit RAM/ROM/CPU) became moot 7sec into the IPng committee's existance -- IPSec shoots all three in the head, repeatedly, with artillery. Everything supports privacy extensions these days, so the logic for random address generation and duplicate address detection is there -- and rather trivial. Yet it, and SLAAC, demands the prefix-length be 64. Just to put that silliness in perspective, that's a single LAN with every ethernet device ever created (that will ever be created) in it 65,536 times over.
This leads nicely into the blindness to history... a 64bit LAN is pure lunacy. Today and likely for several decades. But we "have an infinite amount of address space." Actually, NO, it is, in fact, quite finite: 128bits, to be exact. If we carve it up with the same pez-like abandon as the early IPv4 assignments, it will be even less "infinite". Sure, we can change the way we do things "with the next::/8", but that dooms us to live with the colossal stupid of this::/8 for ever. Again, dooming us (and our children's great grand-children) to live with our bullshit. We did a lot of stupid things with IPv4; and we're doing them all over again with IPv6.
If you're behind CGN, then by definition you aren't allowed to run "servers" -- i.e. services that require outside systems to initiate connections toward you. (www, smtp, bittorrent, etc.)
Why would the home be the "first" place for wide IPv6 adoption
Because it only takes one ISP to stop being a little shit and turn it on for millions of users to suddenly appear. Enterprise networks require the network admin(s) to actively set it up; no amount of tweaks at the ISP can convert them.
Indeed. A great many don't know that switch has been flipped (aka Uverse.) In many cases, it's not until things are suddenly "broken" that anyone notices. (youtube suddenly gets slow -- going through an overloaded 6rd tunnel server, websites don't load as fast -- trying IPv6 first that then timesout, etc.)
Wrong. The protocol has IPsec bolted-on at the socket level. However, you are correct in that nothing knows how to actually use it.
2: Attackers can view your entire IP space.
A: FIREWALL. B: A 2^64 (::/64) LAN will take a LONG time to scan. But, yes, if you know the address of the machine not protected by anything, it's a lame duck.
3: Untested stack, relatively.
Less tested than IPv4, maybe. IPv6 has been around a lot longer than you may realize, and while issues are still emerging, many of them are due to poor protocol design and not poor stack programming.
4: Support is spotty.
This depends on where you are and how much work you put into correcting it (read: tunnels.) But this is ultimately what the entire thread is about... ISPs simply aren't bothering to support IPv6. Those that do are doing so in a mostly jedi-hand-wave gesture for marketing.
Not the way most idiot admins want to use it. "Can I announce "my"/56 to other ISPs?" By "my" they mean the address block provided by one of their ISPs. I see this bullshit all the time. This leads to hundreds (or thousands eventually) of PI address blocks, none of which can be summarized.
Hah! Can you say "reference leak"? I knew that you could. (it's actually *easier* in Java/C# to leak memory, because you have no way to explicitly destroy an object, so programmers never think about it.)
Actually, in the process of solving the one problem it's supposed to solve, they created about 14 trillion other problems, stuck their head in the sand refusing to learn from history or listen to the industries that use the technology -- *cough*DHCP*cough*, didn't give a single second to privacy or security, and finally simply gave up without ever trying when it came to any type of transition policy/mechanism.
We might as well be converting the internet to Appletalk. While they share a few characters in their name, IPv4 and IPv6 are radically different technologies. From an application programming level, there's not much difference, but that's never been much of a hindrance to IPv6 adoption.
Slashdot Mirror
And if you bothered to look at what's in sysv-rc, you'd understand the "dep:". It's what created all the rc.d directories, rcS script, and rc script that actually enumerates and calls the rc.d scripts, and on various systems include the helper scripts update-rc.d and invoke-rc.d. Yes, you can run a system without it. But you'll be replacing it with almost exactly the same shell loop to process rc.d scripts, so why bother? (*cough*file-rc*cough* which is historically how BSD does things)
While we're on this horse... rcS is what calls all the scripts dropped by the initscripts package. (the equiv of a redhat rc.sysinit split into a bunch of files)
... or why AT&T couldn't tell what was what when he called. A call from local media, and the whole thing is figured out in seconds??? If it was "long distance", there'd be line items (i.e. each. individual. call.) on that bill.
Exactly. If there's a bug, fix it. Forcing me to "upgrade" to the next release (which may never be available for a particular device) is NOT the answer.
5.0 (and 5.1) have low adoption numbers because many people (me included) simply don't want that shit. I hate the new UI, and refuse to use any of the "new and more like facebook than ever" 5.0 gapps.
Aluminium is not found in a raw state in nature. It's an oxide ore that requires a fantastic amount of power to extract the metal. (i.e. break the O2 away so Mg has somewhere to go.) The sand used for glass, is pretty much right out of the dessert. (very little effort is put into splitting the Si from the O2)
Since when is kevlar transparent?
Not even remotely. Glass is stupid-cheap to make -- and is made from the most abundant stuff on earth.
Adding someone to a circle doesn't magically give me permission to see their NON-PUBLIC posts. Plus, you can block anyone, and they won't see any of your posts. This is no different than facebook.
The entire problem was that it wasn't different from FB. G+ was just one in a long line of attempts to be facebook; and forcing everyone to "use" G+ certainly didn't make them any friends. So, the choice is Facebook By Facebook -- a system that's been around for a long time with relatively little change, or Facebook by Google -- who is well know for chucking things under the bus. Gee, surprise! Google's chucking G+ under the bus. Google simply cannot. leave. things. alone.
Windows (XP), Tivo, Apple (Mac OSX, iOS), ...
No, they aren't. Goggle is a bunch of f'ing children with the attention span of a 1yo in a room full of shinny things. They lack any vision, want every thing to look and function like Facebook (*cough*gmail*cough*), and constantly change shit that works and people ("the user") like because ooooo shinny.
Maybe. But if they're still there (and that's a big IF given the growing lameness of their products), they're chained in a cave deep under the Marketing Department tower.
With C and C++, the programmer has to keep up with it; thus they are constantly aware of memory usage. (well, those that aren't complete shits do.) In Java, the programmer has no say in it, so they don't think about it -- or for younger "programmers" (who may have never learned C/C++), don't know how.
You've obviously not work in the Real World(tm). Companies will continue using hardware as long as it works -- not broken, don't need new features/functions not possible through software update(s), or don't need additional capacity (based on space and/or power)
(Cell providers cycle through tech due to the last two.)
Unless you're AT&T (Uverse), whose entire plan for IPv6 is 6rd.
How the hell do you summarize two distant /56's out of some other provider's "non-portable" /32? Yes, the ISP ("owner" of the /32) will announce only the entire block. No other piece of that block should exist anywhere outside the ISP's network.
We've allowed that bullshit in IPv4 for decades. The potential size that represents within IPv6 means it must be absolutely FORBIDDEN , from day one until the end of days.
RA, aka. ICMP router advertisement. Abandoned circa 1970 as a "bad idea". It was a colossally bad idea in the 90's, and f'ing suicidally bad in 2000+. Yeah, let's trust whoever the f*** on the cable claims to be a router and send it our traffic. Oh, to protect my network(s) from that brain damage, I have to buy new switches that support "RA Guard".
They didn't like DHCP. So "no f***ing DHCP in IPv6!" DHCPv6 is a bolt-on, staple-on, and bandaid addition to IPv6. It's a horribly incomplete shadow of DHCPv4, and still requires an RA tell you to use it.
SLAAC... originally 80bit prefix plus 48bit MAC. They ignored the fact that ethernet is not the only technology in the universe. That was later amended (breaking older stacks) to 64bits. The entire purpose for the vast over-simplification of address selection (for tiny embeded systems with limit RAM/ROM/CPU) became moot 7sec into the IPng committee's existance -- IPSec shoots all three in the head, repeatedly, with artillery. Everything supports privacy extensions these days, so the logic for random address generation and duplicate address detection is there -- and rather trivial. Yet it, and SLAAC, demands the prefix-length be 64. Just to put that silliness in perspective, that's a single LAN with every ethernet device ever created (that will ever be created) in it 65,536 times over.
This leads nicely into the blindness to history... a 64bit LAN is pure lunacy. Today and likely for several decades. But we "have an infinite amount of address space." Actually, NO, it is, in fact, quite finite: 128bits, to be exact. If we carve it up with the same pez-like abandon as the early IPv4 assignments, it will be even less "infinite". Sure, we can change the way we do things "with the next ::/8", but that dooms us to live with the colossal stupid of this ::/8 for ever. Again, dooming us (and our children's great grand-children) to live with our bullshit. We did a lot of stupid things with IPv4; and we're doing them all over again with IPv6.
If you're behind CGN, then by definition you aren't allowed to run "servers" -- i.e. services that require outside systems to initiate connections toward you. (www, smtp, bittorrent, etc.)
Bullshit. XP supports IPv6. (it's "experimental" and has no GUI, but it a) exists, and b) works.)
Because it only takes one ISP to stop being a little shit and turn it on for millions of users to suddenly appear. Enterprise networks require the network admin(s) to actively set it up; no amount of tweaks at the ISP can convert them.
Indeed. A great many don't know that switch has been flipped (aka Uverse.) In many cases, it's not until things are suddenly "broken" that anyone notices. (youtube suddenly gets slow -- going through an overloaded 6rd tunnel server, websites don't load as fast -- trying IPv6 first that then timesout, etc.)
Wrong. The protocol has IPsec bolted-on at the socket level. However, you are correct in that nothing knows how to actually use it.
A: FIREWALL. B: A 2^64 (::/64) LAN will take a LONG time to scan. But, yes, if you know the address of the machine not protected by anything, it's a lame duck.
Less tested than IPv4, maybe. IPv6 has been around a lot longer than you may realize, and while issues are still emerging, many of them are due to poor protocol design and not poor stack programming.
This depends on where you are and how much work you put into correcting it (read: tunnels.) But this is ultimately what the entire thread is about... ISPs simply aren't bothering to support IPv6. Those that do are doing so in a mostly jedi-hand-wave gesture for marketing.
Most of it already can. If your ISP is still using 20 year old hardware without IPv6 silicon, it's time to find a better ISP.
Not extensively tested within their network (software, hardware, and management) is the real bottleneck.
Not the way most idiot admins want to use it. "Can I announce "my" /56 to other ISPs?" By "my" they mean the address block provided by one of their ISPs. I see this bullshit all the time. This leads to hundreds (or thousands eventually) of PI address blocks, none of which can be summarized.
Hah! Can you say "reference leak"? I knew that you could. (it's actually *easier* in Java/C# to leak memory, because you have no way to explicitly destroy an object, so programmers never think about it.)
Something we've gone out of our way to intentionally break (read: FIREWALLS) on purpose for decades.
Actually, in the process of solving the one problem it's supposed to solve, they created about 14 trillion other problems, stuck their head in the sand refusing to learn from history or listen to the industries that use the technology -- *cough*DHCP*cough*, didn't give a single second to privacy or security, and finally simply gave up without ever trying when it came to any type of transition policy/mechanism.
We might as well be converting the internet to Appletalk. While they share a few characters in their name, IPv4 and IPv6 are radically different technologies. From an application programming level, there's not much difference, but that's never been much of a hindrance to IPv6 adoption.