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

help-circle

  • wow. Someone besides either author got all the way here in the thread to downvote the guy saying open source communities shouldn’t keep people around who make volunteers uncomfortable. Like, what exactly was lost here? A guys right to do free labor? Python is just about the worst language for any task you can imagine anyway, yet someone is going around spending their free time picking 3rd party fights about the community that manages it.

    question for the downvoters:

    Why do you care? Personally, I like having women and racial minorities in computer science. That’s why I care.

    But why would you defend Tim? Please note that I’m not saying you shouldn’t-- it’s just clear that this was never an argument in good faith.




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


  • hey, man. I’m sorry you felt like I was saying “just do it”. I’d be happy to help more, but I don’t have a CD ROM to test with. I just assumed the GUI would be more self explanatory. Like I said above, I’ve never had to burn a CD on Linux. Please remember that the Linux community is made of volunteers. Getting frustrated at them doesn’t really make them want to help, especially since I literally cannot help anymore than I have without a CD rom in my hands. If you want to ship one to me, I’d be happy to figure out Brasero and walk you through it. Since that is clearly unreasonable, remember that these forums are populated by well-intentioned people doing their best.




  • Aha! I understand now. So, on Linux, everything is a file. Even Disk Drives, CDs, flash drives, etc. I think this may be the root of your confusion. Instead of new drive D:// popping up somewhat parallel to your C:// file system (as it would in Windows), it shows up inside your existing file system.

    You were on the right path before. The cdrecord command you ran seems to have correctly told you the location of the CD in your file system (/dev/sr0) . I imagine this changes with distro and hardware, but I’m not sure because my CD burning days predate my Linux days. If you want to make sure that this is indeed the correct place to save the file, then run the command again with the CD removed. If it disappears, then you’ve got it.

    The closest thing I’ve done is install raspberry OS to a flash drive, which often shows up as /dev/sd0, so it seems like you were very much on the right track. The /dev folder means “device”, so most hardware peripherals will have some kind of presence here.






  • I have 4 of the 8bitdo controllers (various Bluetooth models) and games have varying levels of support for them. Sometimes all the controllers show up as 1st player, but mostly steam handles it fine. I’ve also use Microsoft branded controllers in the past with 0 issues, but then you’re locked into to that as mixing those with playstation or 3rd party ones can lead to the same player mapping weirdness. Also, the Xbox variety needs a 2.4Ghz dongle to work with the deck, but I’ve found this to be superior to Bluetooth in crowded environments.


  • I would ignore the people who say you should deploy a model from someone else as that will teach you next to nothing about how this stuff works.

    I would start with an older model and framework (e.g. scikitlearn) and go through all the processing, prediction, and evaluation steps using a model that’s fairly simple to understand. Since you already know about linear regression, start with some of these linear models.

    Then, and only then, would I worry about neural networks and deep learning, since the main difference is a non-linear activation function and a much more complicated set of weights (model parameters in the linear regression language).

    Here is an example

    Source: PhD in neural networks