i noticed few days ago. trying set development system yosemite when stumbled upon file named "[" i'd never seen before. turns out it's copy of unix "test" command.
during little sidetrack, noticed when tried read or infe on "[" file os report "input/output error." assumed there bad block on drive because if is, that's message command line. rebooted mountain lion volume, use base os , used scannerz test hard drive. scannerz found nothing wrong - nothing!
@ point had stopped because else answered "[", drive looked ok, , thought oddity. last night returned trying set partition development , once again, i'm getting input/output errors, on that's on yosemite. mounted mountain lion partition.
wrote little program super user level authentication , wasn't allowed open file on yosemite partition read it. it's entire drive has been "blocked off" access.
i'm not security guy, , hadn't put lot of time looking @ yosemite's underlying features. these being caused resource fork settings , can changed easily?
right it's sort of pia trying deal thing.
is yosemite partition using corestorage? encrypted?
diskutil list
diskutil cs list
ds
Forums Macs macOS OS X Yosemite (10.10)
- iPhone
- Mac OS & System Software
- iPad
- Apple Watch
- Notebooks
- iTunes
- Apple ID
- iCloud
- Desktop Computers
- Apple Music
- Professional Applications
- iPod
- iWork
- Apple TV
- iLife
- Wireless
Comments
Post a Comment