3 private links
CDB = Console DeBugger
Common WinDbg Commands (Thematically Grouped)
By Robert Kuster, November 2007. All rights reserved.
www.software.rkuster.com
We believe that humanity is about fine music, happy families, and good food. People look at things like the golden record and take pride in what humanity has to accomplish, and look forward to a future where Klingons and humans can cooperate.
What we should have done is included some photos of warfare, mushroom clouds, … all that stuff we do all the time that we pretend we don’t. If we’re going to give aliens or future humans a good idea of what we’re about, shan’t we offer forth both our best and our worst?
Except we’re embarrassed of ourselves, and we tell ourselves our achievements are great, and we look out into the stars in search of people like we are — the same way we once saw faces in nature in the sky, and called those “gods”. Our narcissism is so strong that we don’t even need reflections, and we just see ourselves in everything wherever we go. All I have to say is we’ll be damn lucky if aliens are even half like the ones you see on Star Trek.
There’s this saying that a deal predicated on a lie can only go downhill. If you were an extraterrestrial and you discovered humanity was lying to you, how would that make you feel? I, for one, would slowly back away and never return.
We’ll be fortunate if an alien life form can “feel” at all besides hungry. For all we know, the predominant life forms in the universe are just big blobs that consume solar systems like plankton in a cosmic ocean. But our hubris made us send out a beacon that not only signals nearby intelligent life, but we included a map on how to find us. Fortunately, it has later turned out to be woefully inaccurate.
https://news.ycombinator.com/item?id=19445483
I'd be interested in somebody doing this, but instead of scaling it to 1000ms (1 second), I'd like to see it scaled to 16ms (single frame @60fps).
I feel like this would give a better representation of "time to feedback". Saying a ping of 65ms is like 5 years doesn't make a ton of sense as that's a relatively decent ping time. Saying it's 4 frames has a direct correlation to it's perceived delay, and matters to users.
As requested:
System event Actual latency Scaled latency
------------ -------------- --------------
One CPU cycle 0.4 ns 1 frame (1/60 s)
Level 1 cache access 0.9 ns 2 frames
Level 2 cache access 2.8 ns 7 frames
Level 3 cache access 28 ns 1 s
Main memory access (DDR) ~100 ns 4 s
Intel Optane memory access <10 μs 7 min
NVMe SSD I/O ~25 μs 17 min
SSD I/O 50–150 μs 0.5—2 hrs
Rotational disk I/O 1–10 ms 0.5—5 days
Internet call: SF to NYC 65 ms 1 month
Internet call: SF to Hong Kong 141 ms^3 2 months
Conversions courtesy of Wolfram|Alpha, e.g.: https://www.wolframalpha.com/input/?i=65+ms+%2F+0.4+ns+%2F+6...
Perverse Downstream Consequences of Debunking: Being Corrected by Another User for Posting False Political News Increases Subsequent Sharing of Low Quality, Partisan, and Toxic Content in a Twitter Field Experiment
our gateway to the +HCU databases
More than 300 Reverse engineering essays by various +ORC's students and friends
Out of interest, why didn't you just bridge the two interfaces? Did you want everything on a separate subnet? (maybe I missed that but but you mentioned before how everything used to be directly plugged in any way.
eqvinox 1 day ago [–]
You can't bridge regular 802.11 wireless into ethernet at the client side. The on-air addressing requires the client MAC address to be the same as the ethernet packet's sender.
802.11 has the concept of "transmitter address" and "receiver address" in addition to source and destination. Those are MAC addresses too, but they're relevant for the on-air radio management. Things like RTS, CTS, ACKs, and fancier things like beamforming and sounding. The problem is that the design only includes 3 address fields in on-air frames; the AP can specify separate SA and TA (i.e. send a packet for somebody else, SA=real source, TA=AP MAC, RA=DA=client.) There is no mechanism for the client to do the same thing; that would require 4 address fields.
Coincidentally, 4 address fields is exactly what you get with "WDS" / "Wireless Extender" / ... modes. However, these need to be supported, enabled and configured on both the AP and client. The author of the post seems to have no access to the AP to do so (and the AP possibly doesn't support it anyway.)