• 0 Posts
  • 31 Comments
Joined 1 year ago
cake
Cake day: July 24th, 2023

help-circle




  • There are functioning Thorium based Molten Salt Breeder reactors, which for ~50MW can be built in a shipping container size - they are small, so can be deployed at local sites, thus reducing transmission losses, much harder to use for weapons (thats why the world tilted towards the use of uranium reactors in the first place), dont need prior enrichment, and can use much higher percentage of the fuel - so much less waste product. Also since the whole stuff is a molten salt, you just drain it from the reactor core and the reaction simply comes to halt.

    The technology works, as it was tested when they were deciding if the industry goes with uranium or thorium, but the war lobby win out unfortunately, as they wanted a source for their nuclear weapons, at which the Thorium reactors are not great.

    And yes, nuclear is super clean even if we compare it with solar+wind batteries not even counted in to the equation. BTW you can use “spent” fuel rods from conventional nuclear plants in a breeder reactor, to further diminish waste and use them up. https://en.wikipedia.org/wiki/Thorium-based_nuclear_power





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








  • yes, and that command I pasted will run that /stop command inside the docker container. The same way you can list files or do any other commands on a running container:

    # docker exec heimdall ls -la /
    total 148
    drwxr-xr-x   1 root root  4096 Jul 14 07:09 .
    drwxr-xr-x   1 root root  4096 Jul 14 07:09 ..
    -rwxr-xr-x   1 root root     0 Jul 14 07:09 .dockerenv
    drwxr-xr-x   1 abc  abc   4096 Jul 14 07:09 app
    drwxr-xr-x   1 root root  4096 Jun 17 15:30 bin
    drwxr-xr-x   2 root root 12288 Jun 17 15:30 command
    drwxr-xr-x   7 abc  abc   4096 Dec  3  2022 config
    drwxr-xr-x   1 abc  abc   4096 Jun 23 20:35 defaults
    drwxr-xr-x   5 root root   340 Aug 19 04:52 dev
    -rwxr--r--   1 root root 18257 Jan  1  1970 docker-mods
    drwxr-xr-x   1 root root  4096 Aug 19 04:52 etc
    drwxr-xr-x   2 root root  4096 Jun 23 20:35 heimdall