Originally posted by Quackdoc
View Post
systemd 255 Released With A "Blue Screen of Death" For Linux Systems
Collapse
X
-
Originally posted by Weasel View PostI like systemd-boot a lot because of its simplicity (and how bug ridden GRUB is in comparison).
But I really, really cannot understand why it's part of systemd when it has nothing to do with it. You don't even need to have systemd installed for it to work (I mean, it's obvious, the system isn't even "up" at that point during boot).
That's the problem here.
Just call it "simple boot manager" and make it completely separate project and that's it.
Comment
-
-
Originally posted by jacob View Post
You know what the complete saying is?
Jack of all trades, master of none, is often better than master of one.
'Jack of all trades, master of none', or 'Jack of all trades, good at none' goes back to the early 1700's.
Comment
-
-
Originally posted by sophisticles View PostMS never said it was "more stressful" to the average user, but they are correct that to the average user the cryptic stop codes are meaningless.
Comment
-
-
Wtf is wrong with the current black and white panic and oops screens, how is systemd-bsod an improvement other than just hurr durr colors equal better brand identity. Are distros going to start invoking systemd-bsod when unrecovable gpu or xorg freezes/lockups occur?
OT: Its funny how in my whole previous life of using windows it was fleetingly rare for gpu crashes to require a complete reboot - unlike on linux where its next to unheard of for gpus to recover from crashes.
Other than all that the much bigger headache for linux newcomers is the issue of booting into blinking cursor and/or a black screen and the tens of reasons that could have caused it. People (other than me) arent going to spend ten minutes (not to mention hours) googling for why their system is stuck on boot when they can just quickly install windows again.
Comment
-
-
Originally posted by F.Ultra View PostIt's only a resolver, it cannot cause slowdowns of your network traffic.
Lol, a resolver can't slow network traffic <wipes tears>. Classic. Dude! Todays programs tend to requery domain names like 500 times a second coz they suck so much. Of course a bad resolver will slow traffic. Not only that, it can literally brick your system for seconds coz most of those crappy programs will block on it too!
Comment
-
Comment