this post was submitted on 10 Feb 2024
612 points (94.1% liked)

linuxmemes

21263 readers
674 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] captain_aggravated@sh.itjust.works 8 points 9 months ago (1 children)

    Pilot, flight instructor, and reader of many NTSB accident reports. NTSB accident reports often end with a list of recommendations, which in this case would look something like this:

    To the maintainers of steam.deb: use safer dependency management practices to prevent issues with less mainstream desktop environments.

    To System76, maintainers of Pop!_OS: Improve the new user onboarding experience to include a software update. Improve the Pop!_Shop such that checking for updates and thus updating the apt cache is a positive action whose function is obvious to the user. In the case the Pop!_Shop fails to install a package due to a dependency management error, have the error message suggest running the update process.

    To the maintainers of the APT package manager: No notes. This body finds that the warning offered by the terminal is human readable, clear and concise, and carries the appropriate gravity to the risk involved, and by requiring such a non-standard prompt, prevents users who aren't paying attention and used to APT's normal operations from confirming the action accidentally.

    To teachers and creators of Linux tutorials: Include in your Transitioning From Windows To Linux curricula a lesson on Linux warnings. The Microsoft Windows ecosystem presents warning messages to the effect of 'this action may harm your PC" on a frequent basis, such as when installing or removing software, changing certain settings, performing updates, or using certain external hardware. Windows users become accustomed to ignoring these warnings as nothing bad ever happens. The GNU/Linux ecosystem is not in the habit of over-using warning messages, so when one is encountered, it genuinely signposts a potential problem.

    To Linus Sebastian: When a computer gives you an error message, the first step in troubleshooting is to google the exact text of the error. Especially when doing something routine, such as installing popular software on a popular distribution of Linux, you probably are not the first person to have this problem. It has likely already been reported, discussed and solved.

    Damn, that was a good read. I have no doubt your students are trained very well