The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Funny you should be advocating for Debian. I've just installed 10 in a new VM, and its GUI-based updater ("Software Center", I think?) insists I'm offline and it can't get anything. Yet I'm browsing the web and other systems within my LAN.
I've used plenty of versions before that, and have used plenty more alternative distributions (see below - this is from my Hyper-V host running nothing but Linux VMs)...yet this is the first time I've encountered this, and I frankly I don't know what to do about it.
I worked on a product that automated data centers. It ran under that flaky, unreliable, constantly crashing, BSOD producing OS called Windows. It ran for nearly 4 years without being powered off, shut down or rebooted even once. Then the machine was upgraded to a newer version of Windows and continued without issue until I left the company quite a bit later.
We also had to deal with AS/400s, various Unix and Linux machines and they were, relatively speaking, constantly hanging up or giving problems. In fact, we used our software - running under Windows - to report when these other machines became unresponsive.
This was a few years ago but I still haven't seen a BSOD except just one about five years ago when some memory hardware failed.
Sorry, but I don't intend to join your hate-speech club!
- I would love to change the world, but they won’t give me the source code.
I had an old Dell 6520 that lasted me for 5+ years. Then one day it started to BSOD on me at random intervals. the BSOD messages were all different. I checked on the "usual" places for answers the BSOD message but no help. I finally decided to run a memory test, (MemTest86[^]) and low and behold, I had some bad memory. Replaced the memory modules and all was good.
My preferred solution is a kernel dump and WinDbg. The far most crashes I've diagnosed myself stem from faulty third-party drivers, a couple are extremely specific in being unspecific which indicates hardware failure. I remember one I've seen which was impossible to nail down at first, but dude finally admitted overclocking but couldn't grasp the causal connection between overclocking and kernel panics himself.
Most BSoD events are now hidden from the user, as ms has followed apple's example of freezing the state of the monitor (apple shows a screenshot) whilst frantically killing and restarting stuff in the background.
The only way to see that anything happened is by checking the error log -- but even that only works sometimes, because the error log always seems to be one of the first things that stop working,
Personally, I'd rather get blue screens; who knows how much worse they make things by trying to hide errors?
I wanna be a eunuchs developer! Pass me a bread knife!
So ... a drop down, or set of radio buttons (drop down allows for more flexibility in future) and a tiny bit of code. What's the problem?
Sounds like a very nice little feature that is simple to implement and makes the user's life a load easier ...
Sent from my Amstrad PC 1640 Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!