Post by: Paddy on May 27, 2008, 07:15:29 AM
Probably worth bookmarking the Apple Knowledge Base article (and I've added it to our list of Apple Links at TS too!!) referred to, but comments from readers of the article are also useful.
Post by: sandyman on May 27, 2008, 11:34:37 AM
QUOTE(Paddy @ May 27 2008, 01:15 PM) <{POST_SNAPBACK}>
http://www.macworld.com/article/133593/200...bugsnfixes.html
Probably worth bookmarking the Apple Knowledge Base article (and I've added it to our list of Apple Links at TS too!!) referred to, but comments from readers of the article are also useful.
Probably worth bookmarking the Apple Knowledge Base article (and I've added it to our list of Apple Links at TS too!!) referred to, but comments from readers of the article are also useful.
When the going gets tough there's nothing to beat the Terminal
Sandy puts on his asbestos overcoat and awaits the flames
Sandy
Post by: Gregg on May 27, 2008, 12:07:02 PM
Post by: Xairbusdriver on May 28, 2008, 10:18:51 AM
And then, the reason many people shun Terminal are the words of one of the posters, "sorry, the last command should be"! Assuming the poster made the corrections immediately after posting the erroneous one and everyone reads all the following posts, no problems should occur. But we all know what "assuming" does to the best of plans...I would very much appreciate people suggesting Terminal fixes completely explain what each part of every command means. Plus, they should explain which ones are possibly dangerous and how to correct those kinds of errors. Finally, I wish no on would publish Terminal commands that aren't going to be displayed in mono-spaced fonts and especially when lines of text end up running off the edge of the text box display.
While I very much appreciate these knowledgeable people offering ways to correct problems that Apple chooses to ignore or fix, a little more understanding of how the 'regular' user sees and uses their help would be great!