• 0 Posts
  • 5 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle


  • If that is necessary depends on your BIOS/MoBo. I did have to on mine. But the effort for a normal CachyOS install is t really like 5 minutes: boot into live iso, enter ‘cachy-chroot’ or whatever the command is, follow instructions on screen. Then just reinstall grub and/or kernel (which regenerates initramfs). There’s a wiki entry and pinned posts in discord for this whole thing. Ask in discord if you get stuck, they are incredibly responsive and helpful.

    Once you’ve done it, you’ll notice it’s really no big deal. Btw. “Losing” your Linux install is very hard. It’s not as fragile as Windows. You can bork things, but they can usually be un-borked as well. The only real way is fully deleting partitions or their contents, which you can’t just do accidentally.

    Especially just moving it to a new host can’t break it, you just need to get it to boot. Once you know how, it’s like 5 minutes. You can take the drive from a 20 year old PC, pop it into a modern system and it’ll work fine (assuming the system is semi-updated). Windows has a hard time moving to a different MoBo or platform. Linux doesn’t care. Drivers aren’t ‘installed’ like they are in Windows. They are just in the kernel available to be used. Almost everything is detected fresh on every boot, making this incredibly robust. As I said, you might just have to fiddle a bit to get it to boot, once it does, it’ll just work fine.


  • This is actually not even necessary. The systems are similar enough it’ll just work. I have recently swapped an SSD from a laptop to a newer model with CachyOS, and that was more of a generational jump in terms of cpu and other hardware.

    But CachyOS has a quirk. Linux systems specify which partitions are mounted to which directories in the /etc/fstab file. Unfortunately, the boot partition is specified using a device name and not a UUID. this is problematic when switching an SSD from a system to another as this may very well change device names. It did for me and I then had to rescue boot + chroot to fix it.

    The fix, if done before, is trivial: edit the line for /boot in that file to start with UUID= (followed by the actual UUID of the partition) instead of with /dev/nvme0n1p1 or whatever the current device name is. Google should be able to tell you how to find the UUID of your boot partition.


  • Tailscale is WireGuard under the hood, if you didn’t know. It’s an overlay network that uses WireGuard to make the actual connections, and has some very clever “stuff” to get the clients actually to connect, even if behind firewalls without needing port forwarding.

    Using WireGuard directly basically just changes the app you use, which may or may not help with your issues. But the connecting technology is the exact same.