• 1 Post
  • 515 Comments
Joined 9 months ago
cake
Cake day: September 27th, 2023

help-circle
  • If you listen to the video of the interaction with the police officer and the two Waymo guys, it’s clear to me he’s not making anything up about the events that took place. The car did run through the intersection when he turn on the light. He’s not trying to issue tickets or anything - he really is interacting with the Waymo people to let the know “your car was behaving erratically. It needs to be off the road”. Its very possible the road construction uncertainty plus being in an oncoming traffic lane plus being lit up by the police triggered some very specific failure of process in the code.


















  • I’m using a sandwich style case with the PCIE port at the top of the case and the 3 scews for the slots are at the bottom. It basically pushing the card up and backwards into the PCIE extension cable’s slot. No ass sag, but I can tell there’s a limit to how much it would be able to handle like that. I’ve got a 7900xt (not xtx) so it works for what I need right now.



  • “the order in which the system discovered it” is not deterministic

    This is the same problem they had with hard drive names and it seems to have been solved in a sensible way, i.e. /dev/sda still points to the first disk detected by the system, but you can look look in /dev/disk/by-path (or by-uuid, etc) to see the physical address of the devices on the system and what they are symlinked back to, and set your fstab or mdadm arrays to be configured based on those unique identifiers instead.

    So, I guess what I’d like to know is why hasn’t this been solved the same way? When you boot up they should present every hard wired Ethernet port as ethX, and the hardware address interface should be present as well but aliased back to the eth. Then you can build the your network configs based on either one.

    Shouldn’t be that hard right?