jake123 Posted December 23, 2007 Share Posted December 23, 2007 I am unable to "chown" any file... can anyone help me figure out why? Zeke:~ Zeke$ sudo su WARNING: Improper use of the sudo command could lead to data loss or the deletion of important system files. Please double-check your typing when using sudo. Type "man sudo" for more information. To proceed, enter your password, or type Ctrl-C to abort. Password: Zeke:~ Zeke$ cd desktop warrens-xps-m1330:desktop Zeke$ chown -R 0:0 NVinjetGo.kext chown: NVinjetGo.kext: No such file or directory Zeke:desktop Warren$ chown -R 0:0 NVinjectGo.kext chown: NVinjectGo.kext/Contents/Info.plist: Operation not permitted chown: NVinjectGo.kext/Contents/MacOS/NVinjectGo: Operation not permitted chown: NVinjectGo.kext/Contents/MacOS: Operation not permitted chown: NVinjectGo.kext/Contents/Resources/Info.plist: Operation not permitted chown: NVinjectGo.kext/Contents/Resources/InfoPlist.strings: Operation not permitted chown: NVinjectGo.kext/Contents/Resources: Operation not permitted chown: NVinjectGo.kext/Contents: Operation not permitted chown: NVinjectGo.kext: Operation not permitted Zeke:desktop Zeke$ Thank you Link to comment Share on other sites More sharing options...
Dense Posted December 23, 2007 Share Posted December 23, 2007 Incorrect use of the sudo command. sudo -s That will then work. Link to comment Share on other sites More sharing options...
socal swimmer Posted December 23, 2007 Share Posted December 23, 2007 why would you chown something on your desktop? and why chown -R 0:0? isnt it usually root:wheel, in the extensions folder? yea sudo -s is better. Link to comment Share on other sites More sharing options...
onemanstrash Posted January 5, 2008 Share Posted January 5, 2008 why would you chown something on your desktop? and why chown -R 0:0? isnt it usually root:wheel, in the extensions folder? yea sudo -s is better. Root is uid 0, and wheel is guid 0. So say says a friend. In other words they are the same. So it's easier to use 0:0 for me cause it's less letters. Link to comment Share on other sites More sharing options...
westwaerts Posted January 5, 2008 Share Posted January 5, 2008 I am unable to "chown" any file... can anyone help me figure out why? Zeke:~ Zeke$ sudo su WARNING: Improper use of the sudo command could lead to data loss or the deletion of important system files. Please double-check your typing when using sudo. Type "man sudo" for more information. To proceed, enter your password, or type Ctrl-C to abort. Password: Zeke:~ Zeke$ cd desktop warrens-xps-m1330:desktop Zeke$ chown -R 0:0 NVinjetGo.kext chown: NVinjetGo.kext: No such file or directory Zeke:desktop Warren$ chown -R 0:0 NVinjectGo.kext chown: NVinjectGo.kext/Contents/Info.plist: Operation not permitted chown: NVinjectGo.kext/Contents/MacOS/NVinjectGo: Operation not permitted chown: NVinjectGo.kext/Contents/MacOS: Operation not permitted chown: NVinjectGo.kext/Contents/Resources/Info.plist: Operation not permitted chown: NVinjectGo.kext/Contents/Resources/InfoPlist.strings: Operation not permitted chown: NVinjectGo.kext/Contents/Resources: Operation not permitted chown: NVinjectGo.kext/Contents: Operation not permitted chown: NVinjectGo.kext: Operation not permitted Zeke:desktop Zeke$ Thank you My best way to avoid much work in terminal, is to copy the desired kext, change permissions in the infowindow, edit it, and then use kexthelper.app to reinstall it. by the way in Terminal the file paths needs to be specified ( the path you typed, means that nvinjectgo kext file is on your desktop) Link to comment Share on other sites More sharing options...
Recommended Posts