Out of nowhere my Linux Mint crashed and I can only enter emergency mode. What the hell Mr. Torvalds?

Thank god my home folder is in a separated partition and all my data is on remote git but I am atill very annoyed since the crash was in middle of my tunnel blick.

god damn penguins 🐧

As far as i know crashes don't occur out of nowhere (atleast considering the Destro you are using). Could be something you did in your session.

@agiletelescope Yeah that was my thought too. Maybe I did fuck up, let me think... I was coding, listening to music.... I can not remember what I have done, seriously

@dontbeevil I guess that's because this is a programmer community, windows is used to only play games and nothing else (atleast for me), I log into the system once a while and figure out that after installing something, avast or some other crappy program have also been installed without my knowledge(may be I checked the mark, I don't know, has happened multiple times). We programmers just need something that is simple, powerful and doesn't interfere with our work and Linux just does that.

Wtf does Torvalds have to do LM

@aggelalex nothing. It is a joke. A joooooke :D when you fuck things up you gotta blame somebody

Last time I saw someone getting into emergency mode was because he dun goofed up on his fstab, guy rebooted despite explicitly having been told (by yours truly) that he put this fstab in an inconsistent state. Can't blame the system for user error really...

@dontbeevil It's so funny that when a rant is about linux, there are people commenting that When it's abount windows, windows sucks without even know what's about

Blame the kernel for something that was fucked up in userland 👌

@electrineer simple, reason is because complaining about something along the lines of a fucked up fstab (that was the previous guy's problem at least), which he fucked up himself and then blaming Linux for it would be like me screwing up my registry and then blaming Windows for it.

I won't say that I'm a Windows expert, but I do tend to know what I cause myself and what's random shit pulled by the system.

Oh, btw.. fun fact, I was ranting all about systemd's little fuckups earlier today just the same ☺️

Of course, helpful error messages and wikis would definitely help in Windows too...

- have you tried turning it off and on again
- buy new hardware, your hardware is shit
- get proper drivers you idiot, your drivers suck
- sfc /scannow
- reinstall and quietly weep

Aren't always viable solutions, you know... At least Linux does offer that. Troubleshooting steps. I do understand that that's a relatively novel concept for Windows users though ¯\_(ツ)_/¯

@dontbeevil If only the Event Viewer actually gave *helpful* logs! I visited its logs many times to try to troubleshoot why Windows decided to give a BSOD, only to be left with the same old cryptic hex codes that get presented at the BSOD itself, which lead nowhere. Now if Windows actually would pass a good *reason* why it craps itself, other than "something in ntfs.sys", or "memory management" or vague shit like that, that would surely help! You know what error messages in Linux tend to look like? This option in this file here I [this here service] was unable to parse, please fix it because I'm choking on it. That's what an error message *should* look like! Tell you what, when Windows starts doing *that*, maybe I'll start hating it less and people will start supporting the users posting Windows rants with helpful insights too!!!

And before you go, there's minidumps and full memory dumps, yes those exist in Linux too as core dumps, and I never check them. Users shouldn't have to care about those. Whatever a program does, I don't care. There's a debug interface for these programs to dump the crux of the issue into, they should be using it. If Windows decides to crap itself due to bad RAM, a memory location which it tried to write to and shat itself on would be helpful. Error correction by blacklisting that memory address and writing to another location even more so. If Windows decides to crap itself due to hanging on disk activity, mark the process as uninterruptible sleep and maybe fork into a new one. There's so many things that Windows could learn from the Linux ecosystem. But I digress. Error-wise, conciseness is key. Won't help average Windows user, but you can bet your ass that it'll help those who are competent enough to actually diagnose their own system. And no Windows currently isn't (properly) providing such interfaces as far as I can tell, and believe me I've looked far into it. If you do know of the interfaces that don't involve the above meaningless "magic sfc bullets" please let me know. I'm dying to learn about one that'd actually provide me some meaningful diagnostics.