@partizan - eviltoast
  • 0 Posts
  • 68 Comments
Joined 1 year ago
cake
Cake day: July 24th, 2023

help-circle









  • Well not really, cloning is much easier than reinstalling and then configuring everything again…

    I have LVM set up from the start, so usually I just copy the /boot partition to the new disk, and the rest is in a LVM volume group, so I just use pvmove from old disk to the new one, fix the bootloader and fstab UUIDs, and Im ready to reboot from new disk, while I didnt even left my running system, no live USB needed or anything. (Of course I messed it up a first few times, so had to fix from a live OS).

    But once you know all the quirks, I can be up and ready on a new drive withing 20mins (depends mainly on the pvmove), with all the stuff preserved and set



  • partizan@lemm.eetolinuxmemes@lemmy.worldlow effort maymay
    link
    fedilink
    arrow-up
    24
    arrow-down
    1
    ·
    5 months ago
    $ head -3 /var/log/pacman.log 
    [2009-04-04 12:40] installed filesystem (2009.01-1)
    [2009-04-04 12:40] installed expat (2.0.1-2)
    [2009-04-04 12:40] installed dbus-core (1.2.4.4permissive-1)
    

    I installed my Arch on Desktop in 2009 and it was just cloned from one disk to another through multitude of PCs, and sure, there were occasional troubles, like upgrade from SysV init to systemd, when KDE plasma 4 released, or the time, when I had to run a custom kernel and mesa which supported the AMD Vega 56 card ~month after release.

    But nowadays, I didnt had a single breakage for several years, my RX6800 GPU was well supported 3 months after release, and most things just work… BTW I run arch also on my home server, in 6 years it had literally zero issues.