• 2 Posts
  • 34 Comments
Joined 7 months ago
cake
Cake day: February 4th, 2024

help-circle



  • My Lord. Type “Halliburton oil Ukraine” into Google maps and look at the god-damned oil field that’s owned by a US company. Or look at how the US has has record natural gas exports every year since 2014.

    Or look up how the US weapons weren’t given to Ukraine. They were sold and those loans must be paid back. Britain and Russia didn’t pay back their WW2 lend-lease debts until 2006.

    The US is making a killing on this conflict. Ukrainians are also dying for their nation, but two things can be true at the same time. Anyone who isn’t a moron can see that.


  • must be your client. the link works fine for me. If you see the timeline, locals mostly weren’t involved and lots of local anti fascists organized and fought back This island was nominated for the Nobel prize when the crisis started, but there’s only so much people can take when the refugees kept coming, the island couldn’t support thousands of extra people, and refugees were forced to cut down centuries old olive trees for cooking fuel. Something had to give. Moria camp is essentially an open air prison without running water or shower and most people who arrive are children, or were before they walked to Turkey from the Congo or Afghanistan or whatever and boarded boats for a chance at a better life.








  • Look at the top level comment by the user, lurch. If I’m understating him correctly, a reboot should fix it in case that happens. Generally you need to run the dd command to brick stuff in the way you’re imagining. It’s short for either disk duplicator or disk destroyer (if you fuck up). I suspect the cdrecord utility would prevent you from doing anything too stupid on accident.





  • Another user says that you’re not going to brick the drive and that anything you do will probably be fixed by a reboot. If you want to be sure you’re not writing to the main file system drive, the best method is to physically disconnect the device to see that the dev/srX disappears when you do so. At least, that’s the method I’ve always used when burning SD cards for a raspberry pi.



  • no. no. that’s correct. Linux is warning you that you’re about to burn to the disk which will overwrite any files that are there (rewritable CD Roms are a thing and Linux doesn’t necessarily know what kind it is). It’s just warning you that in either case, you’re writing to the disk.

    It’s also no uncommon to have two locations. for example, on my Ubuntu install, I have several /dev/sdX (replace X with a sequential number). One for each physical disc. Those also show up in a folder called /mnt/media but I’m not 100% why. There’s probably some subtle difference that exists for security reasons that’s documented… somewhere.


  • oh! I’m more of a debian guy than a fedora guy which is why this is a bit out of my depth, but /dev/sr1 is just the equivalent of the E:// drive (that is, for whatever reason, you OS mounted it as a new disk). Perhaps this means it burned successfully?

    Unfortunately, yeah, not all documentation can cover the entirety of Linux design from the bottom up and back in this era, Linux was used almost exclusively by academics at universities. As such, the documentation was never written for a general user. It has come a very long way since then, but back when cd roms were common, it was a thousand times worse. Also, YouTube didnt work on Linux at all, so you had to be really committed to fuck around with it.