| |
| ▲ | maxbond 3 hours ago | parent [-] | | `apt-get update` bricked your system multiple times? How, by filling up your disk? That doesn't install or upgrade any software. It just updates the local cache of the registry. I believe you that there was a real problem I'm just confused about how it happened. I've been unable to login after filling my disk before, I wouldn't call the system bricked because I was able to fix it by mounting the disk on another computer and freeing up space, but I wouldn't quibble over the term either. | | |
| ▲ | subjectsigma 2 hours ago | parent [-] | | It was apt-get upgrade, then. Whichever command updates all packages on the system. I must have misspoke, I don’t use Debian-based systems all that much anymore. I remember it had a particular fondness for deleting old kernel versions, failing to install the new kernel, and thus bricking the system on boot. Alternatively, uninstalling the entire WM because one package had a conflict. | | |
| ▲ | maxbond an hour ago | parent [-] | | Weird! Sounds like maybe `apt-get dist-upgrade` or `apt-get full-upgrade`. `upgrade` shouldn't uninstall anything or update your kernel as far as I know. `dist-upgrade` or `full-upgrade` could do either. If your `/boot` partition was exhausted or you lost power in the middle of a kernel upgrade, that could leave the system in a broken state. At any rate, sorry you had such a frustrating experience. |
|
|
|
