Checked in rev246

[larkost]

There are three main changes in revision246, which I just checked in:

1) A new tool to create the BaseOS images from installer disks. The tool lives in AddOns/InstaUp2Date/importDisk.py, and I am pretty happy with it. For the moment most people will probably want to use the -l/–legacy flag because otherwise it will create images with a new style of name and in a new folder (later updates will handle getting those tool up to speed). If you have only one installer disk mounted you just have to use the -a/–automatic flag and it will process it it for you. Take a look at the -h/–help option for more. A couple of examples:
[code]/path/to/importDisk.py –automatic –legacy[/code]
[code]/path/to/importDisk.py /path/to/installerDVD[/code]
[code]/path/to/importDisk.py[/code]
The last form will ask you a few questions.

2) I rewrote the checksum.py code. If you are checksumming a single file you will get same results, but now with a progress meter (-d/–disable-progress option to get rid of this, there are also a couple of more options there). I also have added the beginnings of some code to work on copying the files you are working on. I plan on making InstaUp2Date use this code very soon (hopefully tonight).

A very important note on this though: I discovered that there were a couple of nasty holes in the way I was checksumming folders: symlinks were checksummed as their target files, broken symlinks were skipped, empty folders ignored, and you could change file’s names without changing the checksums. All of these go against the whole point of having checksums, so I consider those some serious bugs. In order to fix them I had to make the new version come up with different checksums for folders. Single files still have the same checksums, but folders will all be different. Sorry about that. In case someone is wondering, I do not checksum file permissions or extended attributes. I thought it over for a while, but since we will sometimes be operating on .dmgs without their permissions enabled I can’t be sure that this is actually a problem.

3) I have added a step in to do a “fix permissions” run on the disk image. I am really curious what this will actually change (since we should be exactly on the BOM files), but there have now been a couple of reports that it does fix some things, so I am putting it in.

PS… It is sad, but the motivation behind the first item is that I am making a nice screencast of the InstaDMG/InstaUp2Date and was unhappy with the part where I used Disk Utility to make the OS image. So I wrote a full-fledged tool to handle this case. *sigh*… I am a geek…

[larkost]

Ok , rev147 has InstaUp2Date using the new checksumming code. The only difference (other than for folders) right now is that you get a progress meter while it checksums things.

[knowmad]

cause no one else has said it:
Thank You!

[Author]

Posts