Well, you may not have realized this, but MacOSX is in fact a Unix OS. The very elaborate graphical interface that is built on top of it makes accessing the Unix base superfluous for most purposes and most users will never need to be aware of the Unix underpinnings.
With early MacOSX versions Apple didn't bother to get a UNIX certification because there were too many deviations from Unix inherited from Steve Jobs' NeXTSTEP/OPENSTEP OS and too many special provisions to enable the transition from MacOS on PCC to finally MacOSX on Intel, but since version 10.5 (Leopard), MacOSX is certified UNIX 03.
Important to realize when working in the command line interface with classic MacOS files and early MacOSX files, is that resource fork and data fork of those files (in fact two files acting in MacOS/MacOSX as one single file) must be kept linked together. Where applicable, special commands were designed for working with such older Mac files. That issue does not exist anymore with modern MacOSX files. Modern MacOSX files only have a data fork and you are probably aware of the fact that an application.app is not a file but a special directory. That is now also true for newer generations of some Mac document formats.
See:Mac OS X Leopard receives UNIX 03 certificationMac OS X UNIX Tutorial for Beginners
I am no Unix specialist. I only learned myself a few tricks. I do use Terminal occasionally to do something that cannot be done easily in the GUI, and I used Terminal to build a couple of SheepShaver and BasiliskII builds that are posted here in E-Maculation forum.
Nice thing to know about the Terminal application: It supports entering paths by drag and drop of files or folders from the Finder. Type "cd " drag the folder into the Terminal window, hit enter, and you are there.
And BTW: Check out Bwana, a very convenient way to read the man pages in your web browser: http://www.bruji.com/bwana/
Now about your damaged disk image. Searching the web I found this possible way to get the image mounted. When we succeed in mounting the volume, it can probably be accessed by DiskWarrior.
- Again make a copy of the image file and change the extension to .dmg
- Launch Terminal
hdiutil attach -noverify -nomount
- Add a space (!)
, drag the image file into Terminal window to enter the path to the file, and hit enter
- If successful (hopefully), enter:
- Find in the list the image (now probably by its volume name) and note the identifier, which is diskN, where N is a number.
diskutil mountDisk /dev/diskN
(replacing N by the number found above).
- If Terminal reports: "Volume(s) mounted successfully" (which will probably not be evident in the Finder), you can launch DiskWarrior. In DiskWarrior main window it should be possible to choose from the popup menu the image volume to be rebuild.
Edit: If successful, DiskWarrior will again mount the volume. This time it will be visible in the Finder. Unmount it before using it again in SheepShaver.