• 0 Posts
  • 31 Comments
Joined 7 months ago
cake
Cake day: April 13th, 2024

help-circle

  • I'll just quote the OpenWRT Wiki here, because I think half the comments here confuse mesh and roaming:

    Are you sure you want a mesh?

    If you are looking for a solution to enable your user devices to seamlessly roam from one access point to another in your home, you need 802.11r (roaming), not 802.11s.

    It is unfortunate that some manufacturers have used the word “Mesh” for marketing purposes to describe their non-standard, closed source, proprietary “roaming” functionality and this causes great confusion to many people when they enter the world of international standards and open source firmware for their network infrastructure.

    • The accepted standard for mesh networks is ieee802.11s.
    • The accepted standard for fast roaming of user devices is ieee802.11r.

    These are two completely unrelated standards.

    Source: https://openwrt.org/docs/guide-user/network/wifi/mesh/802-11s#are_you_sure_you_want_a_mesh











  • My dad told me recently, when he started practicing medicine the old people with heart failures he was treating were often born in the late 1800s, but now those are all dead, and the people he's treating are more likely to have a birth years that are around 1940-1950. Which is also starting to become uncomfortably close to his own, 1960.



  • Is it OK to simply dd the 128GB disk to the 32GB disk using count to stop after the 16GB partition was cloned?

    I think it would work, but it seems a little overcomplicated, you can just use the partition paths as if and of of dd directly, as long as the output partition is not smaller than the input partition. For example dd if=/dev/sdc1 of=/dev/sdd1 bs=4M status=progress

    Your method would also copy the partition table I suppose, which might be something you want under specific circumstances, but then it would be a little harder to get the count right, just taking the size of partition 1 would be wrong, because there is some space before it (where the partition table lives) and dd would start at 0. You'd need to add up the start position and the size of partition 1 instead.

    Personally I would prefer making a new partition table on the new eMCC, and create a target partition on it. Then you clone the content of the partition (i.e. the file system). This way the file system UUID will still be the same, and the fstab should still work because these days it usually refers to mounts by filesystem UUID in my experience.

    If you make the target partition larger than the source partition, and you intend to use the full partition going forward you will additionally need to resize the filesystem to fit the new larger partition, for example with resize2fs.


  • Kazumara@discuss.tchncs.detotraingangYes
    ·
    edit-2
    2 months ago

    I checked Wikipedia real quick:

    The Los Angeles Metro Rail is an urban rail transit system serving Los Angeles County, California in the United States. It consists of six lines: four light rail lines (the A, C, E and K lines) and two rapid transit lines (the B and D lines)

    Looking further, since this happened in Boyle Heights, and only Line E runs through there, it must have been a Kinki Sharyo P3010. The empty weight of one car is 45t. On pictures I can see there were three cars, so 140t (plus content) were pushing forward there. But only the first half in front of the articulation point of the first car derailed. Looking at the schema picture on the bottem here (PDF) it looks like there are three bogies. So I guess we can assume roughly 15t (plus content) would need to be bounced off the track.

    I've seen the result of the same thing happening here in Zürich to our Bombardier Cobra light rail which weighs 39.2t. So I'm not that surprised anymore, but it is still impressive.





  • I wrote a script to turn the power of the the Wifi+Bluetooth chip off, then enumerate the PCIe bus again to start it back up.

    The chip sometimes hung itself when using both. I looked for the bug and even found an Intel engineer on some mailing list admitting that they had issues with coexistance mode.

    Just turning the wireless off and back on wasn't enough I needed to reeinitialize the hardware and that was the best way I knew.