• 1 Post
  • 84 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle
  • I don’t know how recent your experience is with installing Linux, but there are no “hacks” required, haven’t been for many years. In 99.5% of cases everything just works, including sleep & suspend. This is just incredibly outdated or just plain bad advice. There is no tech-savvy-ness needed to use it either.

    I’ve installed it for as tech illiterate people as you can imagine and told them “just use it like you have before”. They had a few questions where the answer would usually be “well what did you do before”, told em to try and that was that. I personally found the PCs to feel faster, but that’s my own comment, not theirs. I don’t think they noticed.





  • the form factor is easy to get around

    Why did you just ignore everything I wrote, but you still replied to me? No, it isn’t easy to get around. You can use a server to game, but the server mainboards and CPUs expect and work with differently configured memory (registered DIMMs). All the AI infratructure uses that type. You can’t use that memory in a normal PC. Wikipedia reference if you’d like to read about it, but a relevant quote:

    […] the motherboard must match the memory type; as a result, registered memory will not work in a motherboard not designed for it, and vice versa.

    You would have to un-solder all the chips and remanufacture new memory modules, and nobody is doing that, especially not at scale. It might be an actual buisness model to do that once the bubble pops, but it isn’t a problem that’s “easy to get around”.>




  • Dual booting is perfectly fine. Just try to not use the windows boot partition for both OS or Windows will occasionally “lose” the Linux entry… “Oops” I guess.

    If Linux is on its own drive, or at least has it’s own uefi partition, it’s just fine and dandy. Just chain load windows from it and there’s basically nothing that can break.





  • Ah now I understand the purpose. I only use it for my (personal) dotfiles, which as a term is ambiguous at best, but in my case I mean config files. That was how I essentially misread your title. Obviously all those files are owned by my user, and most live in ~/.config or similar locations beneath my home directory. Things like application preferences, basically.

    Obviously your tool also works for this, but I now understand it’s more meant for system wide config files.






  • 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.