Jump to content

Search the Community: Showing results for tags 'Terminal'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 7 results

  1. Hello! I am making an automation script for installing Clover onto a drive's EFI partition. For editing the stock config.plist i use PlistBuddy (located in /usr/libexec/PlistBuddy), and the following command causes issues: /usr/libexec/PlistBuddy -c "Add :KernelAndKextPatches:KextsToPatch:0:Find data ixnUEQ==" $config I tried replacing ixnUEQ== with other bases, e.g. 8b19d411 or 10001011 00011001 11010100 00010001 but none yields the desired result, which is: <data> ixnEUQ== </data> Do you have any suggestion as to what I could do instead? Any help would be appreciated. Thank you! EDIT: Solved it. See post 3.
  2. Having problems emptying my trash can after delete about 12GB of junk I had copied from my brother Windows PC hard drive. I was backing up his data so I could completely wipe his PC. After I finished copying back his data to his computer, I just went and dragged the entire HD image to the trash (oops). I have delete large video files and multiple DVD images before in my Mac, but for some reason the trash did not empty this time. I tried Secure empty trash which usually takes care of stubborn deletes. And even after a reboot it still shows I have my trash can filled. I also tried: rm -rf ~/.Trash/* It is not emptying the trash can. Both with and without the "sudo". Any ideas on what to do? I recently upgraded the 10.7.5 supplemental without problems. TIA Currently running OS X 10.7.5 / OS X 10.6.8 / Ubuntu Studio 12.04 / Windows XP Boots to Lion with Chamaleon, 3 internal HD (OSs) & 1 external HD (data)
  3. Mountain Lion USB Installer Creator Creates a USB installer for OS X Mountain Lion. Must be run as root. User is required to supply the path to InstallESD.dmg or have Install OS X Mountain Lion.app sitting in /Applications. Default kernel is vanilla, use '-c amd' to install AnV RC4 amd_kernel as mach_kernel. You can modify the kit or use '-k <path>' to customize the installer: - Chameleon can be updated by replacing the files in Chameleon/i386. - /Extra is copied over from Chameleon/Extra, so files added or changed there will be copied to the new system for you. - Extensions get copied to /System/Library/Extensions from the Extensions folder. - Launch daemons are installed from LaunchDaemons to /Library/LaunchDaemons. - Custom actions can be executed at the end of the installation by modifying the bash script postinstall.sh. The script is sourced by bless, so the environment includes the log function and various useful variables. See the script for more information. - If you use the option to install an AMD kernel, you can replace amd_kernel in the kit and it will get installed as mach_kernel on the installer and the installed system. That way you can use some other legacy kernel instead of the stock default. - usr gets copied to /usr on the installer, but not the installed system. This can still be useful if you want to use a utility in Terminal that isn't available on the installer by default. - The whole kit gets copied to /opt/kit on the installer. Again, probably only useful to advanced users. The '-y' option is great when you don't want to sit around watching for any prompts that might pop up (also for scripts) The '-v' option gives lots of nice progress reporting while copying files, for those that get paranoid when a utility sits with no output for a while. Give your USB volume a fancy custom label with the '-l' option. Ozlog is some ridiculous display of jumping through hoops to monitor the bless hijack on the installer, and probably doesn't deserve to be included with this utility. It may be useful to someone, but consider these options seriously advanced. It should be harmless, but is generally useless. If you want to use it, run `netcat -l 1234' on the host specified by '-a' to see the log. It is only used when bless is called, at the very end of the install process. Check out the log function at the top of usr/sbin/bless for an example of how to use the installer side. So, why would you want to monitor bless? Bless is what screws up some other installer utilities and causes them to say "Installation Failed" at the end, even though the system is still installed successfully. If you look in the kit at usr/sbin/, you'll see that there is a bash script there called bless. This script is the bless hijack, and it tricks the installer into succeeding! It also installs Chameleon, /Extra, ensures the amd_kernel replaces mach_kernel, copies over kexts, etc. This script replaces the stock bless and therefore gets called at the end of the installation. If you had something special you wanted your installer to do, you could put it in kit/ and modify bless to call your script or whatever else you can imagine would be neat. Bonus tip: You can use the following command to create a blank dmg. hdiutil create -size 5g -format UDWR -attach installer.dmg The output will list a device (like /dev/disk1) that you can use as the argument to this utility. Then you'll have a .dmg you can keep, and restore to a USB drive whenever you need it, instead of having to rebuild it with this program. hack:~ oz$ sudo ./mlusbcreator Usage: mlusbcreator [-h] mlusbcreator [-vy] [-k KIT] [-e ESD] [-l LABEL] [-c amd|intel] [-o -a ADDRESS [-p PORT]] target Options: -h, --help show this help message and exit -v, --verbose display more info when copying files -y, --yes automatically answer yes to all questions (useful for scripting) -k KIT, --kit=KIT custom path to the hack kit (default: ./kit) -e ESD, --esd=ESD custom path to InstallESD.dmg (default: /Applications/Install OS X Mountain Lion.app/SharedSupport/InstallESD.dmg) -l LABEL, --label=LABEL custom label for the USB volume (default: Mountain Lion USB Installer) -o, --ozlogd enable remote logging of bless hijack, requires -a and -p -a ADDRESS, --address=ADDRESS ip address to send log messages to -p PORT, --port=PORT custom port to sent log messages to (default: 1234) -c CPU, --cpu=CPU explicitly set cpu type of target system (default: intel) Brought to you by oz and SS01 Example usage: hack:~ oz$ sudo ./mlusbcreator -y --verbose --esd=InstallESD.dmg --cpu=amd /dev/disk1 Get the latest version at http://oz.freqlabs.com/osx86/mlusb.zip
  4. My system is not capable of booting after installing 10.9.2. I have documented my successful installation process for updating up to 10.9.1 here. Once I attempt to boot into 10.9.2, it automatically reboots, no kernel panic nor indication of the cause. I'm also using the latest FakeSMC v6.0.1364. So far, all of my remedies I have done haven't worked. First, using the USB installer, I replaced the vanilla mach_kernel with the patched version in Terminal using the following code and rebooted: cp /mach_kernel "/Volumes/NameOfOSXDisk/mach_kernel" Next I removed all of the native graphic kexts restored after 10.9.2 and transfered them into another folder in Terminal using the following code and rebooted -f: diskutil list diskutil mount /dev/diskXsY mkdir /Volumes/ NameOfOSXDisk /backup cd /Volumes/NameOfOSXDisk/System/Library/Extensions mv AppleIntelHD* AppleIntelSNB* AMDRadeon* ATI* GeForce* NVDA* "/Volumes/NameOfOSXDisk/backup" Next I placed the NullCPUPowerManagement.kext back into E/E and rebooted -f: fsck -fy mount -uw / cd System/Library/Extensions mv /NullCPUPowerManagement.kext "/Volumes/NameOfOSXDisk/Extra/Extensions" Next I replaced the AICPM kext with a patched version on an additional USB stick in Terminal using the following code and rebooted -f: cd /Volumes ls cd NAMEOFOSXDISK cd System/Library/Extensions ls rm -rf /Volumes/NAMEOFOSXDISK/System/Library/Extensions/AppleIntelCPUPowerManagement.kext cp -R /Volumes/USBSTICK/AppleIntelCPUPowerManagement.kext /Volumes/NAMEOFOSXDISK/System/Library/Extensions exit Next I replaced the AppleRTC.kext with a patched version on an additional USB stick in Terminal using the following code and rebooted -f: cd /Volumes ls cd NAMEOFOSXDISK cd System/Library/Extensions ls rm -rf /Volumes/NAMEOFOSXDISK/System/Library/Extensions/AppleRTC.kext cp -R /Volumes/USBSTICK/AppleRTC.kext /Volumes/NAMEOFOSXDISK/System/Library/Extensions exit After attempting all of these remedies at no avail, I was forced to revert back to 10.9.1. I can not seem to successfully boot into 10.9.2 for the life of me. Am I missing anything? If anybody has this similar problem on a Haswell system and has figured out a fix to it, I would gladly appreciate you letting me know. Thanks
  5. p.H

    What is Terminal ?

    By LordPum Original Post ( Italian ) : http://www.insanelymac.com/forum/topic/222809-terminale-cose/ Things about the terminal ? We may have seen the word "terminal" many times. But not everyone knows what the terminal really is. First of all, it is an application located in /Applications/Utilities. The use of terminal is derived from UNIX which allows you to control the machine only through the command line. In fact, the terminal is present in OS X because OS X itself is based on UNIX. The usefulness of terminal lies in the fact that many operations can be performed much faster with the terminal and it allows us to use administrator privileges, as may be required. EXAMPLE: If you want to delete a file from the recycle bin(Or Trash in OS X), but you are told that the file is protected and continuing expunging could do harm to your system. But you're sure that deleting this file won't cause you trouble though system warns. You can try with the terminal. rm insanely.txt is deleting the file insanely.txt What if you have lots of files which you want to eliminate? You can also use terminal in the following way: cd .Trash sudo rm -dfri *.* After each line, you should press "Enter". The command rm means eliminate, while sudo means that you want to delete as root, the administrator of the computer. You will be prompted for the password every first time you use the sudo command. Option "-dfri" is needed for this: - the r is used to delete the subdirectories of the directories in the trash - the d is used to remove the files in the directory in the trash - the f is used to force the cancellation or ignored if the file is protected or "apparently "used by some processes - the i is used to ask you to confirm the deletion of the files. Do not use if you are going to delete many files, but it could be useful in the case where you are unsure of what the rm command would delete. At last, *. * indicates the file to be deleted. In this case it represents all files in the folder. For more information: http://www.insanelymac.com/forum/index.php?showtopic=225608
  6. Hi! I sometimes use Steam for games on my Hackintosh, but I partitioned my disk as Mac OS Extended (Case-sensitive, Journaled) which is incompatible with Steam. Instead of creating a whole new partition table for a small application, you can create a disk image of a case-insensitive format and run Steam from there. These Terminal commands will create this disk image. If you do not create a separate SteamApps folder, replace 500m (on row 26) with a byte size that can fit your games aswell, eg 40g. #!/bin/bash mkdir -p /Applications/Steam.app/Contents/Resources mkdir -p /Applications/Steam.app/Contents/MacOS plist=/Applications/Steam.app/Contents/Info.plist /usr/libexec/PlistBuddy -c "Add CFBundleExecutable string 'Steam'" $plist /usr/libexec/PlistBuddy -c "Add CFBundleInfoDictionaryVersion string '1.0'" $plist /usr/libexec/PlistBuddy -c "Add CFBundlePackageType string 'APPL'" $plist /usr/libexec/PlistBuddy -c "Add CFBundleSignature string '????'" $plist /usr/libexec/PlistBuddy -c "Add CFBundleVersion string '1.0'" $plist /usr/libexec/PlistBuddy -c "Add CFBundleIconFile string 'steam.icns'" $plist bin=/Applications/Steam.app/Contents/MacOS/Steam echo '#!/bin/bash' > $bin echo 'hdiutil detach /Volumes/Steam' >> $bin echo 'if [ != /Volumes/Steam ]' >> $bin echo ' then hdiutil detach -force /Volumes/Steam' >> $bin echo 'fi' >> $bin echo '' >> $bin echo 'hdiutil attach -noverify -nobrowse /Applications/Steam.app/Contents/Resources/Steam.dmg' >> $bin echo '/Volumes/Steam/Steam.app/Contents/MacOS/steam.sh' >> $bin echo '' >> $bin echo 'hdiutil detach /Volumes/Steam' >> $bin echo 'if [ -e /Volumes/Steam ]' >> $bin echo ' then hdiutil detach -force /Volumes/Steam' >> $bin echo 'fi' >> $bin chmod +x /Applications/Steam.app/Contents/MacOS/Steam hdiutil create -size 500m -fs "Journaled HFS+" -volname Steam /Applications/Steam.app/Contents/Resources/Steam.dmg hdiutil attach -noverify -nobrowse /Applications/Steam.app/Contents/Resources/Steam.dmg mkdir -p /Volumes/Steam/Steam ln -s /Volumes/Steam/Steam $HOME/Library/Application\ Support/Steam curl http://media.steampowered.com/client/installer/steam.dmg -o $TMPDIR/steam.dmg hdiutil attach -noverify -nobrowse $TMPDIR/steam.dmg cp -RX /Volumes/Steam\ 1/Steam.app /Volumes/Steam/ cp -X /Volumes/Steam\ 1/Steam.app/Contents/Resources/steam.icns /Applications/Steam.app/Contents/Resources/ chmod +x /Volumes/Steam/Steam.app/Contents/MacOS/steam.sh rm $TMPDIR/steam.dmg hdiutil detach /Volumes/Steam if [ -e /Volumes/Steam ] then hdiutil detach -force /Volumes/Steam fi hdiutil detach /Volumes/Steam\ 1 if [ -e /Volumes/Steam\ 1 ] then hdiutil detach -force /Volumes/Steam\ 1 fi When you are prompted to accept a license, just press Q, Y and ↵, in chronological order. After running all the commands, reboot and start Steam from the application in /Applications. You may have to create a firewall exception, by opening System Preferences, Security & Privacy, Firewall and Firewall Options…
  7. Rampage Dev

    How To Run MemTest Under Mac OS X

    about: The following guide will show you how to run MemTest under Mac OS X. This will allow you to debug if you have bad ram or a bad over-clock. Originally Posted on here. Guide: Part 1: Installation 1. Download MemTest for Mac here 2. Go to your Downloads folder and locate the following package: 3. Run the MemTest Installer: 4. When the install is complete close the installer Part 2: Running MemTest 1. Open Terminal: 3. The following screen should appear: 4. Type in the following into terminal: memtest all 2 Or memtest all 5. Then press Enter 6. The following screen should appear: 7. Now wait for the results as this my take a few hours to running depending on the amount of ram you are using