@[email protected] to [email protected] • 11 hours agoTinkering and Stabilitylemm.eeimagemessage-square28fedilinkarrow-up148arrow-down11file-text
arrow-up147arrow-down1imageTinkering and Stabilitylemm.ee@[email protected] to [email protected] • 11 hours agomessage-square28fedilinkfile-text
What are some of the easiest ways for a beginner to make their system untable when they start tinkering with it?
minus-square@[email protected]linkfedilink10•edit-27 hours agoonce you have some experience under your belt, these are non-issues: deciding to “learn Linux” the hard way by starting with a specialized distro (Slackware, Gentoo, Alpine) switching to unstable or testing branches before you’re ready ’cause you want bleeding edge or “stable is too far behind” playing around with third-party repositories before understanding them (PPAs in Ubuntu, AUR in Arch) bypassing the package manager (especially installing with curl | sudo sh) changing apps for no other reason than “it hasn’t been updated for a year”
minus-squareyoumaynotknowlinkfedilink1•39 minutes ago changing apps for no other reason than “it hasn’t been updated for a year” That’s the only part I disagree with. Software not updated in a long time can easily become a risk. Everything else though, spot in.
minus-square@[email protected]linkfedilink1•8 minutes agoaimed at beginners who confuse “hasn’t been updated for a year” with “hasn’t needed to be updated for a year”
once you have some experience under your belt, these are non-issues:
curl | sudo sh)That’s the only part I disagree with. Software not updated in a long time can easily become a risk.
Everything else though, spot in.
aimed at beginners who confuse “hasn’t been updated for a year” with “hasn’t needed to be updated for a year”