• 0 Posts
  • 37 Comments
Joined 4 months ago
cake
Cake day: July 6th, 2024

help-circle





  • That sounds like the non-techies would be able to fix it themselves on Windows without you being around, which in my experince isn’t the case.

    It might be different for you with a lot of tech-affine people in your family. But for those of us being forced to be the tech support anyway, it can really make a difference if you have to fix a Linux issue once in a while or have to reinstall Windows for the 5th time this year…



  • They don’t hate them. They just want to cut all support for citizens to have more money available to finance more tax cuts for rich people.

    But to do this you need to somehow convince the masses that money spend on them is a bad thing. For decades trickle-down fairy tales of how spending money on the already rich ones will help the economy and then be beneficial for all worked. But not anymore. So the next phase in desinforming gullible voters is much more dystopian and involves straight out brain-washing to decouple them from reality and make them believe that people actually helping them are evil and need to be fought.


  • ARM is shit at hardware discovery in general. So no, chromebooks don’t need a special distro. They however need a kernel adapted to the specific hardware, often down to the model (that’s also the reason Android updates take so long on phones and there is very time limited support… there’s always someone needed to adapt new updates to the specific hardware for each device, so they don’t bother for anything but their latest products).



  • Decryption isn’t a problem if you use the systemd hooks when creating your initrams. They try to decrypt every given luks volume with the first key provided and only ask for additional keys if that fails.

    I have 3 disks in a btrfs raid setup, 4 partitions (1 for the raid setup on each, plus a swap partition on the biggest disk), all encrypted with the same password.

    No script needed, just add rd.luks.name=<UUID1>=cryptroot1 rd.luks.name=<UUID2>=cryptroot2 rd.luks.name=<UUID3>=cryptroot3 rd.luks.name=<UUID4>=cryptswap to your kernel parameters and unlock all 4 with one password at boot.








  • When you say system drive this will also have your efi system partition (usually FAT-formated as that’s the only standard all UEFI implementations support), maybe also a swap partition (if not using a swap file instead) etc… so it’s not just copiying the btrfs partition your system sits on.

    Yes clonezilla will keep the same UUID when cloning (and I assume your fstab properly uses UUIDs to identify drivees). In fact clonezilla uses different tools depending on filesystem and data… on the lowest level (so for example on unlocked encrypted data it can’t handle otherwise) clonezilla is really just using dd to clone everything. So cloning your disk with clonezilla, then later expanding the btrfs partition to use up the free space works is an option

    But on the other hand just creating a few new partitions, then copying all data might be faster. And editing /etc/fstab with the new UUIDs while keeping everything else is no rocket science either.

    The best thing: Just pick a method and do it. It’s not like you can screw up it up as long if your are not stupid and accidently clone your empty new drive to your old one instead…