• 1 Post
  • 497 Comments
Joined 1 year ago
cake
Cake day: February 1st, 2024

help-circle




  • No, that’s not really a useful way of modeling it for the case of light traveling through a linear medium.

    The absorption/re-emission model implicitly localizes the photons, which is problematic — think about it in an uncertainty principle (or diffraction limit) picture: it implies that the momentum is highly uncertain, which means that the light would get absorbed but re-emitted in every direction, which doesn’t happen. So instead you can make arguments about it being a delocalized photon and being absorbed and re-emitted coherently across the material, but this isn’t really the same thing as the “ping pong balls stopping and starting again” model.

    Another problem is to ask why the light doesn’t change color in a (linear) medium — because if it’s getting absorbed and re-emitted, and is not hitting a nice absorption line, why wouldn’t it change energy by exchanging with the environment/other degrees of freedom? (The answer is it does do this — it’s called Raman scattering, but that is generally a very weak effect.)

    The absorption/emission picture does work for things like fluorescence. But Maxwell’s equations, the Schrödinger equation, QED — these are wave equations.





  • IIRC chvt is a privileged command, which makes sense (if an unprivileged user could execute this command they could effectively brick the computer for a local user).

    That said, my understanding is that modern DE’s are given a lot of access, so presumably chvt is allowed (and in this case, is required because as others mentioned, password is required). So the only other option is to fail unlocked, which is all kinds of Bad.






  • For very simple tasks you can usually blindly log in and run commands. I’ve done this with very simple tasks, e.g., rebooting or bringing up a network interface. It’s maybe not the smartest, but basically, just type root, the root password, and dhclient eth0 or whatever magic you need. No display required, unless you make a typo…

    In your specific case, you could have a shell script that stops VMs and disables passthrough, so you just log in and invoke that script. Bonus points if you create a dedicated user with that script set as their shell (or just put in the appropriate dot rc file).





  • It’s completely context dependent; you’re right that using male/female is appropriate for humans in certain contexts, e.g., medical usage (“Patient, a 47yo female, presented with…”). But it is — for cultural and historical reasons — generally considered inappropriate to refer to our fellow humans that way in conversation.

    Re: mutt, fair enough. Bitch/stud are examples of how animal terms, when applied to humans, take on very different meanings. Purebred is afaik not specific to species, but it is wildly inappropriate to refer to people as such.

    At the end of the day, the logic behind what is and is not appropriate has history behind it; animal terms have been used extensively to refer to subjugated peoples; it may be scientifically accurate but that doesn’t mean that it’s inoffensive.


  • Of course we’re animals, but let’s use some common sense wrt cultural norms here. A dog of mixed lineage is mutt, but it’s completely inappropriate to refer to a multiracial person as such. A female dog is a bitch, a male is a stud; the sexism is pretty obvious when applied to humans. It’s fine to talk about owning a dog; it’s not ok to talk about owning another human (except perhaps children, in certain contexts).

    Yes, we are animals too, but that doesn’t mean we should talk about each other in the same way. (And I say this as a vegetarian who thinks we should treat all animals with significantly more respect than we currently do.)