Wheelman [PT]
03-04-2004, 02:52
Não é só cá nesta terrinha à beira do mar abuseirada que temos serviços ao cliente, que só podem ser considerados de fertilizante para couves.
Podem dar uma espreitadela nisto e comparar.
Sudhian (http://www.sudhian.com/showdocs.cfm?aid=419)
Reboot. Yeah, you heard right, reboot. You have no idea how many times I’ve heard that before. I’ll call up some computer store, my ISP, my web hosting provider, or any number of other computer assistance groups to report a problem and the first thing they ask me is “Have you rebooted recently?” Since when does reboot fix 98% of problems? Oh sure, on Microsoft Windows it might fix some issues, but the vast majority of issues, at least 95% of them don’t require a reboot to solve them. Yet this seems to be the answer I hear most often when trying to fix a problem or diagnose it. Or if I’m helping someone else, they’ll ask me “Do you want me to reboot? I hear that fixes everything.” What is the big mystique with rebooting? I know at times it’s useful for clearing some memory issues, reloading drivers, or with Linux/BSD it’s very useful and required should you decide to rebuild the source tree and kernel or make certain network changes. But in the majority of cases, a good set of tools and the right knowledge will help you resolve almost any issue. Take for example someone having a hard drive issue. I can see you wanting to boot into dos mode with windows or single user mode with Linux/BSD in order to scan the drive without any issues or concerns of interference from the OS in the process to try to help find and detect disk issues. But let’s say your browser is set to work offline. How can rebooting fix that? It can’t, not unless there’s some trick during the reboot that will magically restore it to being in online mode.
Ok, I realize I’m being a bit sarcastic on some of my descriptions, but it’s true. Good old fashioned diagnostic detective work will help you find the source of your issue every time and fashion an effective solution for repairing it. Take for example my main computer at work. It runs FreeBSD 4.8 with KDE 3.1 as the window manager. For those who don’t understand the world of Linux/Unix, FreeBSD is a Unix derivative written for the x86 processor (Intel, AMD, etc.) based off of Berkley BSD, a descendent of AT&T UNIX, one of the very first versions of Unix. My FreeBSD Workstation has been up 148 days consecutively and was only rebooted last time to add a second hard drive and upgrade the kernel to version 4.8 since it had been running 4.6 prior to that. I’ve only restarted Xwindows (the graphical shell upon which KDE operates) twice in that time to allow for some upgrades to be performed. Oh sure, I’ve had my fair share of issues. Programs crashing, apps not upgrading properly or running incorrectly. That’s not unusual. Everyone has those. If you say you don’t, you’re just lying to yourself. Take for example a recent issue I had. On FreeBSD there is an application called “Port Upgrade” that greatly simplifies upgrading all of your programs to the latest versions and handles all the messy work for you. One problem. If the upgrade goes awry you have to manually install the app and do it by hand. Well, that’s exactly what happened to me. During one of my upgrades the installer kept failing. Had the strangest error I had ever seen and I certainly didn’t know how to fix it at the time. Did I reboot? Oh heavens no. I actually took the time, researched the issue, then tested several different solutions that were presented to me and eventually found one that worked. The app successfully built and was eventually upgraded after that.
It’s simple things like this that can be the big deciding factor in solving an issue that may occur on your system. If all else fails and you absolutely positively have to reboot, then by all means do so. But if it can be avoided in any way, always seek that route first. Because the best answer isn’t always the right answer. But in the end you will be ever so much happier.
------
Now isn't that precious...
Podem dar uma espreitadela nisto e comparar.
Sudhian (http://www.sudhian.com/showdocs.cfm?aid=419)
Reboot. Yeah, you heard right, reboot. You have no idea how many times I’ve heard that before. I’ll call up some computer store, my ISP, my web hosting provider, or any number of other computer assistance groups to report a problem and the first thing they ask me is “Have you rebooted recently?” Since when does reboot fix 98% of problems? Oh sure, on Microsoft Windows it might fix some issues, but the vast majority of issues, at least 95% of them don’t require a reboot to solve them. Yet this seems to be the answer I hear most often when trying to fix a problem or diagnose it. Or if I’m helping someone else, they’ll ask me “Do you want me to reboot? I hear that fixes everything.” What is the big mystique with rebooting? I know at times it’s useful for clearing some memory issues, reloading drivers, or with Linux/BSD it’s very useful and required should you decide to rebuild the source tree and kernel or make certain network changes. But in the majority of cases, a good set of tools and the right knowledge will help you resolve almost any issue. Take for example someone having a hard drive issue. I can see you wanting to boot into dos mode with windows or single user mode with Linux/BSD in order to scan the drive without any issues or concerns of interference from the OS in the process to try to help find and detect disk issues. But let’s say your browser is set to work offline. How can rebooting fix that? It can’t, not unless there’s some trick during the reboot that will magically restore it to being in online mode.
Ok, I realize I’m being a bit sarcastic on some of my descriptions, but it’s true. Good old fashioned diagnostic detective work will help you find the source of your issue every time and fashion an effective solution for repairing it. Take for example my main computer at work. It runs FreeBSD 4.8 with KDE 3.1 as the window manager. For those who don’t understand the world of Linux/Unix, FreeBSD is a Unix derivative written for the x86 processor (Intel, AMD, etc.) based off of Berkley BSD, a descendent of AT&T UNIX, one of the very first versions of Unix. My FreeBSD Workstation has been up 148 days consecutively and was only rebooted last time to add a second hard drive and upgrade the kernel to version 4.8 since it had been running 4.6 prior to that. I’ve only restarted Xwindows (the graphical shell upon which KDE operates) twice in that time to allow for some upgrades to be performed. Oh sure, I’ve had my fair share of issues. Programs crashing, apps not upgrading properly or running incorrectly. That’s not unusual. Everyone has those. If you say you don’t, you’re just lying to yourself. Take for example a recent issue I had. On FreeBSD there is an application called “Port Upgrade” that greatly simplifies upgrading all of your programs to the latest versions and handles all the messy work for you. One problem. If the upgrade goes awry you have to manually install the app and do it by hand. Well, that’s exactly what happened to me. During one of my upgrades the installer kept failing. Had the strangest error I had ever seen and I certainly didn’t know how to fix it at the time. Did I reboot? Oh heavens no. I actually took the time, researched the issue, then tested several different solutions that were presented to me and eventually found one that worked. The app successfully built and was eventually upgraded after that.
It’s simple things like this that can be the big deciding factor in solving an issue that may occur on your system. If all else fails and you absolutely positively have to reboot, then by all means do so. But if it can be avoided in any way, always seek that route first. Because the best answer isn’t always the right answer. But in the end you will be ever so much happier.
------
Now isn't that precious...