Comment Re:They believe it because it's true (Score 1) 928
Sounds like someone's society deserves to fall.
Sounds like someone's society deserves to fall.
Only if you put those shots into your presentation. Perv.
FUSE doesn't count because it suffers limitations that are inherent with being executed as user-mode software. FUSE ZFS is also an incomplete implementation.
Proof of citizenship is a little more involved than simply checking a list. You forget that in the Land of the Free, anyone that is born here has a birthright to citizenship. Birth doesn't guarantee inclusion in any supposed lists of citizenry.
You forgot about the nuclear bombs. Why sire a new society when you can just vaporize it? I suppose you'll try to make another comparison regarding civility and how it matters in how "bad" or "worse" one war is than another. When you do, don't forget to blame Islam.
Yes, but you could move between them like Sliders.
This guy is either trolling or is very naive about RF.
"It's not that hard to make sure one's service doesn't interfere with the next."
Give me a break.
Magic The Gathering
DPI doesn't necessarily mean that it happens before a switch or router forwards a packet. Flows of traffic can be analyzed separately from the processes of a router or switch in making packet forwarding decisions. This separate analysis can influence adjustments to QoS rules. So, no, DPI does not necessarily interfere with all traffic.
You are the Worst Person in the World!
Stuff with brains can learn.
An IP address DOES identify a computer- but not the way the judge thinks. My IP address identifies my router, which in turn owns 5 to 6 computers. With the wireless open, it could refer to the whole neighborhood, for all I know/care. They need to revise, an IP address identifies a NETWORK, but not neccessarily conclusively any particular computer.
You say that "an IP address does identify a computer" and then argue that it does not. It's much less confusing to just say that an IP address DOES NOT identify a computer--and it does not identify a computer, a customer, or anything other than a logical endpoint of a tcp/ip network. This is especially true when the IP address is not statically assigned. A lot of people like to think about IP addresses as accounting tools, when they are really not meant to serve as such. People also like to think that a DHCP server's logs can be used as a way to make IP addresses into accounting tools, but they would also be wrong. For example, a cable internet subscriber can usually make use of his internet connection regardless of being assigned an IP address as long as his cable modem is authorized and his computer assumes an IP address that is valid for his network segment (and isn't a duplicate of another address currently in-use). In such a case (and it does happen quite often), there would be no accountability for that subscriber to the ISP as far as IP addresses in the DHCP server logs are concerned.
Let me get this straight.
You propose that ISP's should count packets tied to a subscriber account in such a real-time fashion as to put this logic to use in rewriting the packet headers in-transit?
Once you're done actually building a system even capable of that, how do you keep such a bad-ass future network from becoming Skynet?
Real-time accounting is hard enough--having the networking devices actually make decisions about header mangling based on that accounting on a packet-by-packet basis is not something that exists yet and isn't going to invent itself for free or cheap.
I live in that zip code, you insensitive clod!
Only through hard work and perseverance can one truly suffer.