{"id":333,"date":"2020-08-18T19:23:47","date_gmt":"2020-08-18T20:23:47","guid":{"rendered":"http:\/\/www.linux-tutorial.info\/?page_id=77"},"modified":"2020-08-22T19:26:19","modified_gmt":"2020-08-22T20:26:19","slug":"this-is-the-page-title-toplevel-166","status":"publish","type":"page","link":"http:\/\/www.linux-tutorial.info\/?page_id=333","title":{"rendered":"Solving Problems"},"content":{"rendered":"\n<title>Solving Problems<\/title>\n<p>\nUsing &#8220;Solving Problems&#8221; as the title for this chapter was a very conscious\ndecision. I intentionally avoided calling it &#8220;Troubleshooting&#8221; for several\nreasons. First, troubleshooting has always seemed to me to be the process by\nwhich we look for the causes of problems. Although that seems like a noble task,\nso often finding the cause of the problem doesn&#8217;t necessarily mean finding the\nmeans to correct it or understanding the problem.\n<\/p>\n<p>\nThe next\nreason is that so often I find books in which the troubleshooting section is\njust a list of problems and canned solutions. I find this comparable to the\nsign &#8220;In case of fire, break glass.&#8221; When you break the glass an alarm goes off\nand the fire department comes and puts out your fire. You may never know what\nreally caused the problem nor what you can do to solve similar problems in\nthe future.\n<\/p>\n<p>\nThe troubleshooting sections that I find most annoying\nlist 100 problems and 100 solutions, but I usually have problem 101. Often I\ncan find something that is similar to my situation, and, with enough digging\nthrough the manuals and poking and prodding the system, I eventually come up\nwith the answer. Even if the answer is spelled out, it&#8217;s usually a list of steps\nto follow to correct the problem. There are no details about what caused the\nproblem in the first place or what the listed steps are actually doing.\n<\/p>\n<p>\nNot all problems are alike, and not all problems can be approached in the\nexact same manner. However, there are some basic issues that are common to every\nproblem and there are basics steps you can take, no matter what the cause.\n<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Solving Problems Using &#8220;Solving Problems&#8221; as the title for this chapter was a very conscious decision. I intentionally avoided calling it &#8220;Troubleshooting&#8221; for several reasons. First, troubleshooting has always seemed to me to be the process by which we look &hellip; <a href=\"http:\/\/www.linux-tutorial.info\/?page_id=333\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-333","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages\/333","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=333"}],"version-history":[{"count":1,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages\/333\/revisions"}],"predecessor-version":[{"id":707,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages\/333\/revisions\/707"}],"wp:attachment":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=333"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}