• 0 Posts
  • 521 Comments
Joined 9 months ago
cake
Cake day: January 3rd, 2024

help-circle

  • MajorHavoc@programming.devtoLinux@lemmy.mlThe Dislike to Ubuntu
    link
    fedilink
    arrow-up
    15
    arrow-down
    1
    ·
    edit-2
    1 day ago

    Ubuntu was a big part of my path to full time Linux use. I adore everyone who has contributed to Ubuntu.

    But also, Snaps are bullshit, and are why I replaced all my Ubuntu installs with Debian.

    Canonical doesn’t get to pretend to be surprised by the backlash for pushing an unnecessary closed proprietary platform on their freedom seeking users.

    I still adore everyone at Canonical and in the Ubuntu community, for all they’ve done for the Linux community. Y’all still rock. Thanks!









  • Yeah. It’s not hardware, then.

    I would try searching “black screen <bios version>” with any name and version number you can figure out about your bios, next.

    If you can get it back to booting from install media, I would do a full reinstall.

    There’s recovery layers (such as grub shell) that ought to kick in if this was just a display config issue, so I’m thinking corrupted install files is more likely.

    Also, do a careful check through your various BIOS settings - search each one with “Debian 12 <setting name>”, to find out if they work with Debian 12, or need adjusted. Debian 12 supports most boot security features, that I have encountered, but I believe there’s still a couple out there that have to be turned off.

    I suspect your next practical goal will be to get the (presumably failed) bootloader install replaced.

    Edit: Tried to add a lot of specific thoughts as search term leads.






  • Bare minimum place to start: See if you can get the team to agree that these documents should exist in every project root folder:

    • README.md - What is this even for? Audience: Managers.
    • CONTRIBUTING.md - What steps are needed to build this? What steps are needed to be able to run the tests? Audience: Developers.
    • CHANGELOG.txt - Describes the contents of every tagged release. Audience: end users.

    Stretch goal: pick a spot (readme is fine) and make a list of sources (data in) and sinks (data out). Include contact information for whoever can reset the credentials or fix the firewall.



  • I figured out how to remove most of the safeguards from some AI models.

    Nice.

    How do you feel about this?

    It’s another kind of power. I try to use mine responsibly, but also to give myself a break when I don’t meet my own standards.

    Some good advice I got once was that it’s impossible to “un-say” something, so it pays to think twice before speaking.

    If your gut is telling you to pause, listen to it. Wait to move forward until you feel better about it.

    As someone else pointed out, responsible disclosure is an option.

    You also have the option to just quietly enjoy a better copy of the AI than others have.

    If you decide to publish your discoveries, be aware that others will judge you for how you go about it. For me that means the two options are responsibly, or anonymously.