• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: August 22nd, 2023

help-circle


  • For what it’s worth, you are supposed to be able to access documents stored in OneDrive in Linux. (I haven’t tried it myself; I’m just aware of it.)

    Basically: Go to GNOME’s settings, then select online accounts, and sign into OneDrive.

    Here the same instructions with lots of details and screenshots: https://www.omgubuntu.co.uk/2024/04/set-up-onedrive-file-access-in-ubuntu (Nothing in that link is Ubuntu specific. This applies to other distros too, like Fedora, Debian, Arch, Mint, etc. — as long as you have GNOME 46.)

    Other desktops have to use various other options, but aren’t natively integrated: https://linuxstans.com/microsoft-onedrive-on-linux/


    Of course, once you have access to files like this, you’ll probably want to copy them locally and back them up yourself.

    (I suspect Microsoft was trying to make it so people don’t lose their files, ironically, by handling document storage themselves? It’s still absurd that they do this so aggressively.)

    My favorite backup software is Pika. It’s powered by Borg, has a friendly UI, and supports both local (including USB drives) and remote locations. https://flathub.org/apps/org.gnome.World.PikaBackup

    Deja Dup is also good and uses Duplicity behind the scenes. https://flathub.org/apps/org.gnome.DejaDup

    There are a ton of other backup solutions too, including Vorta (another UI for Borg) and a bunch of command line tools, like rclone, rsync, etc.


  • Doesn’t distrobox (and podman) come with SteamOS these days too?

    You wouldn’t be able to layer, but using distrobox-export from inside a distrobox container would let you export command line apps as well as graphical ones too. The graphical apps will even show up in your menu and can be pinned as well.

    (Of course, if something is available on Flathub already as a Flatpak, installing the app via Discover is easier and better. While Flathub has a lot of apps, it doesn’t have everything, so being able to pick and choose from any distribution using distrobox is nice for a very large selection of software.)


  • darktable, hands down. It has a learning curve, but it’s a pro app and app pro apps have learning curves.

    The linear pipeline is great, masking is superb, and the app keeps getting better every release.

    The one downside is that darktable is not opinionated by default (so raw files look a little flat to begin with, without doing anything), but it’s customizable that you can even change that with auto applied presets. On the other hand, it does let you do what you want to do with an image, versus fighting with defaults (which is what it’s like to edit something in Lightroom, if you want to diverge from what it suggests by default).

    There are a bunch of great tutorials on YouTube and you’ll want to check out https://discuss.pixls.us/ too. Create an account on the Pixls forum, read some threads, try out some “play raws” (where people post their raw files under a CC license and then lots of people try their own take at editing it and post their edit).

    Rico Resolves has a half hour getting started video for darktable 4.6 at https://youtu.be/ucjAmTMIEOI

    Anything from Bruce Williams https://youtube.com/@audio2u and Boris Hajdukovic https://youtube.com/@s7habo are both great too, and more people are posting darktable videos all the time as well.

    The documentation for darktable is actually very good as well. Do not skip it. You don’t have to read it all, but try reading the intro parts and going back to it when you want some reference on how a part of darktable works. https://docs.darktable.org/usermanual/4.6/en/

    Some tips:

    • You can right click on sliders to get a special UI and you can also enter numbers (often even outside the bounds of what the slider would normally permit).

    • Modules will be applied in the best order regardless of which one you work on first.

    • There are some somewhat redundant modules, as darktable did start out as a “display referred” workflow (just like most all of the other raw editors everywhere) and moved to a “scene referred” (aka “linear rgb”) workflow, which provides better editing, improved color handling, vastly better tone mapping, and so on. If there are two similar modules, try to go with the version that has “RGB” in its title. Older modules still exist mainly for older edits. (You can also change darktable back to the old display referred workflow in the settinfs, but I strongly suggest to not do this. Scene referred is much better.)

    I used to shoot film and do darkroom stuff years ago. I’ve used Aperture on OS X. I used Lightroom on OS X and then on Windows. A few years ago, I switched to darktable on Linux… and darktable has gotten so, so much better each release. When I switched years ago, it was more or less a Lightroom competitor (with some advantages and disadvantages). But darktable is really amazing software now, and can give you much better results than Lightroom, when you know how to use it.


  • Agreed.

    Additionally, the graphic oversimplifies things as well. The resulting genetically modified crop is often not even all that close close to the same as the non-GMO, as seen by studies such as this one:

    https://enveurope.springeropen.com/articles/10.1186/s12302-023-00715-6

    Basically; GMO soybeans contain proteins which differ and also include additional proteins. This can cause allergic reactions to modified soy where non-modified soy might not cause an issue.

    Monsanto supposedly even knew about these proteins and higher risk of allergic reaction and chose to not disclose it. (I saw some research that mentioned this years ago… It’d be hard to find the exact source I read back then.) This specific paper, which talks about additional proteins and side-effects brought in by the new transgenic splicing, also explicitly states that Monsanto did studies themselves and failed to report relevant findings:

    https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5236067/

    Obviously, other methods can also change proteins too, but these papers show it isn’t as clear cut as the graphic in the original post claims.

    Along these lines, here’s a study that finds differences not just in soybeans grown organically versus ones treated by glyphosate (Monsanto Round-Up pesticide) but also between GMO and non-GMO crops, both treated by the pesticide.

    https://www.sciencedirect.com/science/article/pii/S0308814613019201

    But, yeah this is just a long way of agreeing with the parent post and saying that the end goal is to make the plants resistant to poison, not to make them better for humans, all to make more money. (In this case, Monsanto is even double-dipping by selling both the pesticide and the crops tailor-made for the pesticide.)

    Other GMO crops might be closer to the original crop and might also actually be beneficial for humans without drawbacks. However, Monsanto’s soybeans are problematic, and other crops might be as well, especially if they’re made by companies who have money as their primary goal.



  • My first attempt to try to fix something like this would be to:

    1. Download Fedora Workstation live media. (Within Windows or some other computer that boots.)
    2. Flash it to a USB stick.
    3. Reboot to the live desktop from the USB stick. (It might require pressing F12 or some other key combo during boot.)
    4. “Try out” Fedora. (That is: do not install.)
    5. Open GNOME Disks. (I think it’s included. Otherwise, you can sudo dnf install gnome-disks to install it temporarily on the live session.)
    6. Try to mount the main filesystem that contains /etc/fstab (it should ask you for the LUKS password.
    7. Comment out the Windows mount point. Or if you want to keep it (if the partition still exists and is just “dirty” and still needs a check from Windows) add “,nofail” after “auto” to the options in the line for the mount, so your system should still boot without that mount point.
    8. Save the /etc/fstab file.
    9. Shut down the computer.
    10. Unplug USB stick.
    11. Boot computer. Linux should successfully boot… hopefully. 😉

    I’m also wondering: How did you add the Windows partition to Fedora? Was it from within Fedora’s installer (aka: “Anaconda”)? Or did you add it in a different way?

    (BTW: I use Silverblue and have a long history with Fedora. 😁)