Why would I enter in my Comcast credentials into an untrusted wifi? What, so they can setup a fake wifi, steal my creds, and use my account to log into other real Comcast wifi's and do all kinds of illegal stuff in my name?... right.
Re-reading when I posted, this was meant for just the first sentence talking about the blogs. The rest of the information is "true", but based off of memory. The part about the threaded api code for FreeBSD 11 was from a youtube from BSDCON(or similar convention)(https://www.youtube.com/watch?v=7CvIztTz-RQ) that was just published a week or two ago. The zero copy part is about "netmap" I think. Another/. post in this thread also mentioned it.
They're random blogs that I tend to come across when googling how to tweak network stacks for handling lots of connections. Take it as you will. It was an entirely anecdotal and opinionated blob of text that I probably just should have left out.
A lot of sysadmins from companies that push a lot of data over lots of connections have blogs about tweaking your OS to handle stuff like 10gb+ of traffic and millions of connections. A lot of these people complain about Linux having strange problems under these loads, and FreeBSD just seems to work. Linux may be faster in some cases, but it still has stability issues that are hard to debug.
Then there's the whole thing about most network stack research happening primarily on FreeBSD because of licensing. There's a new zero-copy network API that was developed in FreeBSD that allows line rate 64byte 10gb traffic on a 450mhz quadcore cpu. Linux and old-api FreeBSD were about 1/10th the packets-per-second.
A new thread friendly socket API has just been pushed to FreeBSD 11. One of Netflix' engineers had a pet project that now allows near zero lock-contention thread scaling. He was able to done line speed 40gb/s with 150k TCP sessions. Instead of having one file descriptor with a single listening thread, you instead have one file-descriptor and listening thread per MSS queue from the NIC and you can lock your thread to the same CPU as the MSS queue, so the packet is already in L2 cache. No shared network state. This also means no share locks with nearly perfect linear scaling and virtually no cache trashing or bouncing.
They're starting work for extend the API to also allow the OS to better handle NUMA and to attach the MSS queues to the CPU to which the NIC is attached. This will virtually remove all cross-talk among the CPU cores trying to handle the network state.
They're looking into expanding this same concept to the Storage IO system.
You can't just copy/paste code and expect it to work, it must be refactored, and may not even be compatible until completely new features are added in the current code to allow the new code to function. It's like saying "that fusion reactor is an open design, why not just place that in our coal power plant?". You may need to make some changes to your current power plant before you change its core.
if the firewall sees traffic it doesn't understand it's just going to drop it.
MPTCP is backwards compatible with stateful firewalls, so unless your firewall knows about MPTCP, it will think it's just another TCP stream for an unknown Layer7 protocol and nothing will look wrong.
With a 40Gb stream, there is about 5MB of data per millisecond. You're going to need some large network buffers to handle out of order packets.
The biggest issue is you went from firewalls that didn't need to know about each other's state to not only sharing state, but every packet. Essentially you went from a lock-free design to a giant lock.
I assume this would be way too much load for the firewalls, so you'd be better off mirroring all edge traffic to a central server to demultiplex the streams. Imagine you're a company with several 100gb connections, with a total of 1tb of bandwidth, and you have a central server that needs to somehow handle 1tb of mirrored packets getting forwarded to it. That'll be interesting.
You should define what you mean by "woman" or "man". There are men with XX chromosomes, and I don't mean transgender or hermaphrodite. Fully functional with no defects or issues, except missing one gene that allows their sperm to swim, but that's one Y to X gene movement away. It will be interesting to define man and women if we all became XX and the only difference was gene expression to control hormones during fetal development.
If the pool of men is drastically reduces, we run a stronger chance of a monoculture waiting for the next pandemic. Children, especially women, who grow up without a father figure have a much greater risk of confidence issues, which can drastically aspect every aspect of their life, and a slew of other psychological problems. Technically we could get by without men to some degree, but it would probably be detrimental.
It was never brought to court, but the very real reality is that he accessed a server and explicitly accessed a server after being told not to with the intention of committing a very likely copyright infringement, all in the "name" of Linux. Linus was not happy with this.
GCC is the OpenSSL of compilers. I'm amazed how many people don't appreciate design and quality. This is why Linus and OpenBSD love to yell at people. They'd rather not have to deal with stupid, so they scare them away.
You mean when Tridgdell violated the EULA and illegally accessed the Bitkeeper service with the intent to reverse engineer, when Linus said not to? Tridgdell claims to have done it to help the Linux project by gaining access to meta data not available to the free version of the client, but Linus agreed to the EULA and had access to this information already. Because of Tridgdell's actions, Linus had a large mess to clean up.
Linus only goes off the rails like this for nothing but complete and utter unforgivable incompetence. They deserve exactly what he said. He calls it like it is, and I respect him for that. No beating around the bush when people are doing the most horrible of "mistakes".
Install OpenBSD on a computer not behind a firewall and see if it gets hacked. I think they've had 2 remote security vulnerabilities in the past forever.
What are you talking about? PFSense supports IPv6 uPnP with the base install. Just enable uPnP service and it will allow uPnP to punch holes in the firewall for the requesting IPv6 address. Worked just fine with my Windows box and Torrent. It was quite turn-key. Enable service, done.
Why would they be able to discern anything about your internet network without a NAT. You just saying that indicated you don't know what you're talking about or you're trolling.
Except NAT has no official implementation, so many implementations have many different security bugs to be exploited. Firewalls are easy to test, NAT implementations, not so much.
If, however, time slows as it approached the blackhole and the particle never actually crossed the event horizon
Can someone please explain this. It seems to be accepted that not only does the object's time slows down as it approaches the event horizon, but it's velocity does also. I don't get that. If an object is moving away from me at 0.9999c, I could expect is to actually be moving away from me at that speed, not slowing down relative to me. If from my perspective an object has stopped moving, then it is no longer moving relative to me and its time should be pretty much the same to my reference.
I seem to be missing something. I assume it has to do with gravitational fields instead of "proper" velocity.
Any light emitted from the "black hole" itself could also be dwarfed by the noise of all the other em coming from the accretion disk, making it nearly impossible to detected remotely.
Time must be reversible. Once information falls into a blackhole, there is no way to reverse time and get the same information out because the information becomes ambiguous in something that in infinitely dense.
Slashdot Mirror
Why would I enter in my Comcast credentials into an untrusted wifi? What, so they can setup a fake wifi, steal my creds, and use my account to log into other real Comcast wifi's and do all kinds of illegal stuff in my name?... right.
Indians are still more expensive than a script.
Re-reading when I posted, this was meant for just the first sentence talking about the blogs. The rest of the information is "true", but based off of memory. The part about the threaded api code for FreeBSD 11 was from a youtube from BSDCON(or similar convention)(https://www.youtube.com/watch?v=7CvIztTz-RQ) that was just published a week or two ago. The zero copy part is about "netmap" I think. Another /. post in this thread also mentioned it.
They're random blogs that I tend to come across when googling how to tweak network stacks for handling lots of connections. Take it as you will. It was an entirely anecdotal and opinionated blob of text that I probably just should have left out.
A lot of sysadmins from companies that push a lot of data over lots of connections have blogs about tweaking your OS to handle stuff like 10gb+ of traffic and millions of connections. A lot of these people complain about Linux having strange problems under these loads, and FreeBSD just seems to work. Linux may be faster in some cases, but it still has stability issues that are hard to debug.
Then there's the whole thing about most network stack research happening primarily on FreeBSD because of licensing. There's a new zero-copy network API that was developed in FreeBSD that allows line rate 64byte 10gb traffic on a 450mhz quadcore cpu. Linux and old-api FreeBSD were about 1/10th the packets-per-second.
A new thread friendly socket API has just been pushed to FreeBSD 11. One of Netflix' engineers had a pet project that now allows near zero lock-contention thread scaling. He was able to done line speed 40gb/s with 150k TCP sessions. Instead of having one file descriptor with a single listening thread, you instead have one file-descriptor and listening thread per MSS queue from the NIC and you can lock your thread to the same CPU as the MSS queue, so the packet is already in L2 cache. No shared network state. This also means no share locks with nearly perfect linear scaling and virtually no cache trashing or bouncing.
They're starting work for extend the API to also allow the OS to better handle NUMA and to attach the MSS queues to the CPU to which the NIC is attached. This will virtually remove all cross-talk among the CPU cores trying to handle the network state.
They're looking into expanding this same concept to the Storage IO system.
You can't just copy/paste code and expect it to work, it must be refactored, and may not even be compatible until completely new features are added in the current code to allow the new code to function. It's like saying "that fusion reactor is an open design, why not just place that in our coal power plant?". You may need to make some changes to your current power plant before you change its core.
if the firewall sees traffic it doesn't understand it's just going to drop it.
MPTCP is backwards compatible with stateful firewalls, so unless your firewall knows about MPTCP, it will think it's just another TCP stream for an unknown Layer7 protocol and nothing will look wrong.
Al though most deep packet inspection problem looks for port-numbers
IPv6+IPSEC. Port numbers are also encrypted.
With a 40Gb stream, there is about 5MB of data per millisecond. You're going to need some large network buffers to handle out of order packets.
The biggest issue is you went from firewalls that didn't need to know about each other's state to not only sharing state, but every packet. Essentially you went from a lock-free design to a giant lock.
I assume this would be way too much load for the firewalls, so you'd be better off mirroring all edge traffic to a central server to demultiplex the streams. Imagine you're a company with several 100gb connections, with a total of 1tb of bandwidth, and you have a central server that needs to somehow handle 1tb of mirrored packets getting forwarded to it. That'll be interesting.
You should define what you mean by "woman" or "man". There are men with XX chromosomes, and I don't mean transgender or hermaphrodite. Fully functional with no defects or issues, except missing one gene that allows their sperm to swim, but that's one Y to X gene movement away. It will be interesting to define man and women if we all became XX and the only difference was gene expression to control hormones during fetal development.
If the pool of men is drastically reduces, we run a stronger chance of a monoculture waiting for the next pandemic. Children, especially women, who grow up without a father figure have a much greater risk of confidence issues, which can drastically aspect every aspect of their life, and a slew of other psychological problems. Technically we could get by without men to some degree, but it would probably be detrimental.
Multiprocess means lots of threads and IPC, which are both horrible for scaling unless you're doing heavy work. Death by via thread scheduling.
It was never brought to court, but the very real reality is that he accessed a server and explicitly accessed a server after being told not to with the intention of committing a very likely copyright infringement, all in the "name" of Linux. Linus was not happy with this.
GCC is the OpenSSL of compilers. I'm amazed how many people don't appreciate design and quality. This is why Linus and OpenBSD love to yell at people. They'd rather not have to deal with stupid, so they scare them away.
You mean when Tridgdell violated the EULA and illegally accessed the Bitkeeper service with the intent to reverse engineer, when Linus said not to? Tridgdell claims to have done it to help the Linux project by gaining access to meta data not available to the free version of the client, but Linus agreed to the EULA and had access to this information already. Because of Tridgdell's actions, Linus had a large mess to clean up.
Linus only goes off the rails like this for nothing but complete and utter unforgivable incompetence. They deserve exactly what he said. He calls it like it is, and I respect him for that. No beating around the bush when people are doing the most horrible of "mistakes".
I wonder if some people are just born with strong interests, so they just have more time consumed with something that caused them to be better.
Install OpenBSD on a computer not behind a firewall and see if it gets hacked. I think they've had 2 remote security vulnerabilities in the past forever.
No, I expect users who want to run services that listen on ports (which makes them not "average!") to know about those things.
You mean like the "server-less" P2P console games that elect the host from one of the current people in game?
Unless you want to reinvent uPnP for v6
What are you talking about? PFSense supports IPv6 uPnP with the base install. Just enable uPnP service and it will allow uPnP to punch holes in the firewall for the requesting IPv6 address. Worked just fine with my Windows box and Torrent. It was quite turn-key. Enable service, done.
Why would they be able to discern anything about your internet network without a NAT. You just saying that indicated you don't know what you're talking about or you're trolling.
Except NAT has no official implementation, so many implementations have many different security bugs to be exploited. Firewalls are easy to test, NAT implementations, not so much.
They didn't use taxes, they used bonds.
If, however, time slows as it approached the blackhole and the particle never actually crossed the event horizon
Can someone please explain this. It seems to be accepted that not only does the object's time slows down as it approaches the event horizon, but it's velocity does also. I don't get that. If an object is moving away from me at 0.9999c, I could expect is to actually be moving away from me at that speed, not slowing down relative to me. If from my perspective an object has stopped moving, then it is no longer moving relative to me and its time should be pretty much the same to my reference.
I seem to be missing something. I assume it has to do with gravitational fields instead of "proper" velocity.
Another orthogonal explanation.
Any light emitted from the "black hole" itself could also be dwarfed by the noise of all the other em coming from the accretion disk, making it nearly impossible to detected remotely.
Time must be reversible. Once information falls into a blackhole, there is no way to reverse time and get the same information out because the information becomes ambiguous in something that in infinitely dense.