#Techtool pro 5.0.6 update#Įither wait for the public source trees to update and rebuild it (likely early tomorrow), or use this one. The bash these steps will install works on 10.4 all the way to 10.9 on 32-bit Intel, 64-bit Intel and PowerPC. In a Terminal.app window, verify that you have a vulnerable system so that you can see what that looks like (the command is all one line):Įnv x='() ' bash -c foo.WARNING AGAIN: If you are not comfortable with the Terminal, get someone to help you! The idea is to replace your system bash - yes, you can use Homebrew, Tigerbrew, MacPorts, etc., to get an updated copy, but your built-in bash is still vulnerable unless you replace it. License GPLv3+: GNU GPL version 3 or later GNU bash, version 4.3.27(3)-release (powerpc-apple-darwin8.11.0)Ĭopyright (C) 2013 Free Software Foundation, Inc. This is free software you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.Įver since I bought my first macbook pro which was 2006 and it might have been running 10.3 back then, the operating system has had more or less problems waking from sleep. There are all of the permutations of sleep selected from the menu vs sleep by closing the lid, go to sleep with it plugged in or not, wake up plugged in or not, knock the plug out while it's asleep, etc. And of course I've got my machine set so that only the display sleeps if it's plugged in. It has been really quite good since about 10.6.6. But I am certainly willing to believe that the machine and/or display goes to sleep and/or wakes up via shell script, and I may be hitting some funk there. While I have had kernel panics, I've also had the machine mostly just go to sleep and not wake up. I pretty much always boot into single user mode and run fsck after a crash, and the only time I got an fsck error was when I had to crash the machine after I copied in the new binaries and hit "shut down" and it hung at the white screen for about 10 minutes. Yesterday I couldn't get it to wake up, so I mashed the button, booted into single-user mode and used applejack to run fsck (there's a shell script), then restarted, logged in, and it kernel panic'd as the desktop started to load. Restarted, fsck, restarted, and it's been up since. Last night when I went to bed I put it to sleep via the menu, and it woke up this morning without the slightest problem - no problems today.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |