• 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle




  • Depends on specific machine setup and how good the backup is.

    Backup requirements for /usr there are sticky bits set on some binaries. That needs to be preserved. In all cases soft links likely need to be preserved for things to work correctly on future package installs. Hard links can be problematic, but if you have a large enough drive or not that many it wont matter. Running package verification can be help after restore to make sure everything looks right. If running a Linux system with SELinux in enforcing mode (RHEL on many derivatives), then the security context will also need to be preserved BUT running a relabel will probably work if the security context was not included in backups. Sometimes running the relabel process wont work if there are files that needs a specific security context but are not listed in the security context database. Can’t provide more details because most of my experience with that is on systems we just replace (LSPP custom labeling resulted in systems that if you booted into permissive would then be unbootable, so they were just reinstalled once any debugging was done).

    For /boot things can get tricky depending on the distribution, what boot manager is used, and /boot was a separate partition or not. Basically the boot manager (probably grub) needs to know how to find the files in boot so it can load the kernel. In most cases if you restore /boot and rerun the tools to update the boot manger everything will be fine. BUT some distributions, hardware setups, or dual boot configurations are more complicated, so extra work might be needed.

    You didn’t mention /dev, which is all special files. These don’t need to be restored, just make sure the right processes recreate them. There are tools to do this, hopefully the packages are installed. Or boot from a rescue disk and fix it. Look up instruction for your specific distro.




  • Sugar and refined carbohydrates are two big culprits. Then changing the balance of HDL-cholesterol to LDL-cholesterol changes with weight gain making it all worse and possibly leading to a positive feedback loop. The historic denigration of all fats, good and bad, helped to further tilt the HDL to LDL in the population making lots of people less healthy. It isn’t HFCS, it is the over use of sugar in most of our food. This is especially true in North America, but then we exported much of the same food tech to the rest of the world who did the same.

    All that processed food? Full of refined carbs and sugar. Drinks? Often full of sugar. Cheap food? Usually highly processed and refined, so more sugar and refined carbs. You need carbs for energy and fats to keep everything going with balance of nutrients and protein. Any of that out of balance and health suffers. Too little fat can even kill you (rabbit starvation/protein poisoning). The modern diet in North America is terrible because we were told good things were bad and carbs were good. So we ate too little of the good fats, too much of the refined carbs, and too much sugar. Now were here, increased heat disease, diabetes, obesity, and cancer.


  • This is very good. Oklo is specifically aiming to provide power with minimal maintenance to remote areas that otherwise wouldn’t have power. This contract is a very good testbed for the technology before being deployed to remote areas.

    There have been research reactor that have been run successfully that cannot meltdown like Fukushima, Chernobyl, or Three Mile Island. Oklo is a fast reactor of similar design. Such reactor designs often will cool down and the nuclear reaction stop even when completely losing all coolant and power. They fundamentally cannot get into a positive feedback loop like an reactors that are have been run commercially. I’m unsure how long Oklo’s nuclear waste is dangerous, but some fast reactors can actually be used to burn up waste from other reactors making. Their waste is dangerous for a few hundred years, instead of the tens of thousands of years of other reactors.


  • Depends on environment.

    Real hardware separate for a server partitions for: /home, /var, swap, sometimes /usr, sometimes /var/log/audit Depends on deployment requirements, and if a system is expected to run after filling up audit.

    Real hardware for a at home desktop: /var, swap, maybe /home, or just one partition for / and one for swap.

    Cloud: all one partition, put swap in a file if it is needed. Cloud images are easy to grow if it is just one partition. Cloud-init will handle that automatically with the right packages installed, no configuration needed. Swap partitions are unlikely to be the right size as they vary according to memory and memory varies according to instance/guest sizes. Swap makes auto growing root partition harder (cloud-init custom config injection required). Best practice is to size workload and instances to not need swap whenever possible.


  • virr@lemmy.worldtoWorld News@lemmy.mlAnthony Fauci’s Deceptions
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    1
    ·
    11 months ago

    Cause it is trash.

    Media Bias doesn’t seem to have an entry for thefp.com, which is a red flag. That the website calls themselves the free press and has nothing to do with the Free Press organization, sure seems like they are trying to confuse that on purpose. Using a Rand Paul comment as a source in support of an article problematic (he’s a real life unreliable narrator and one of many idiots in congress). The current house subcommittee the article relies on has been criticized for good reason. Lots of opinion mixed in that is not commentary on the facts. Self citation isn’t the win they think it is with the other issues.

    Could the article be right? Sure. Is this an article that would convince me of that? No. An article with reputation of reporting from the center, or near center, with the same or similar conclusions and the it is worth discussion. Otherwise this article was a waste of storage and time.










  • I have not listened to the podcast unfortunately.

    Rebuilders are fine, and RedHat is fine to not spend the effort to debrand their source rpms. The problem is one of value. The value RedHat provides for some people is probably worth more than RedHat charges. The value RedHat provides to others is less than the effort it takes to renew a developer license once a year for 16 installs. The problem is that there are several who are ending support for RHEL because they fall into the latter group (notably Jeff Geerling for ansible roles). RHEL losing out on that support might be huge, might not, only time will tell.