leodag's comments

On: A Lufthansa A350's frustrating Oakland diversion

[leodag]

Now I am confused - I have no actual knowledge on this but on the post there is a comment from an experienced pilot saying the opposite:

> [...] But IMO ATC was absolutely not doing what they are supposed to do. Air traffic control is literally a service provided to and paid for by the airlines.

[filleduchaos → leodag]

...how is that the opposite of what I said?

On: Chrome Users Beware: Manifest V3 Is Deceitful and ...

[leodag]

Have you used it recently, or just years ago? It definitely used to be very slow, but since ~2 years ago it's very good, and my go to browser (my phone is not high end, by the way)

[marginalia_nu → leodag]

I give it a spin every few months. Then I uninstall it because it's still irredeemably unresponsive.

On: How fast are Linux pipes anyway? (2022)

[leodag]

That's wrong though, it's got nothing to do with different buffering (which is usually done at the application level, by the way).

On: SICP in JavaScript

[leodag]

You'd be surprised at how readable Lisp is for people who actually learn it instead of just saying "look, weird language ha-ha!"

On: Build your own Docker with Linux namespaces, cgrou...

[leodag]

It's not necessarily interactive, it's also pretty common to have a shell script for initialization/setup.

On: A large crash spike affecting Firefox users on Lin...

[leodag]

Wasn't that because of Variable-Length Arrays? I remember a while back there was a movement to remove all of them from the kernel.

[asveikau → leodag]

Perhaps. I think there are other reasons to avoid VLAs. I've heard the code generated for them kinda sucks.

But IMO a compiler should generate extra benign reads on a large stack allocation. You mention avoiding VLAs in the kernel, but even user mode code has this problem.

Certainly a browser JITing random JS from the internet should be able to work around such a problem.

On: “Exit traps” can make your Bash scripts more robus...

[leodag]

> The "ssh-agent -k" command will emit shell commands

Does it really? I've executed it here and it just runs kill, doesn't emit any bash. Running just ssh-agent (without any args) does that though, which is what's probably causing the confusion.

[chasil → leodag]

I am on OpenBSD 7.2, and I see:

  $ eval $(ssh-agent)
  Agent pid 56785

  $ ssh-agent -k
  unset SSH_AUTH_SOCK;
  unset SSH_AGENT_PID;
  echo Agent pid 56785 killed;

The correct processing of that output requires an eval.

Did you have any other questions?

[pmarreck → chasil]

Why do you need to eval it?

$(ssh-agent)

won’t substitute that with the stdout and run that?

[chasil → pmarreck]

Because the intended use for "ssh-agent -k" is for eval.

While redirecting to /dev/null will certainly work, the agent is holding sensitive credentials (by design), and confirmation of shutdown has a tangible security benefit.

On: Changes to Tailscale Pricing and Plans

[leodag]

They said he should reconsider if the free plan covers his usage, not that he'd get the same features. Which could be true if e.g you were only paying so you could get more than one user.