[mypointofview]

I backed up my system to a Sandbox partition (another partition on my drive to which I backed up using SuperDuper's sandbox feature "Shared users and applications"). I then started up from that Sandbox partition and updated the OS (using a standalone combo updater). I wanted to explore if there are any problems for me because of the OS upgrade.

I discovered an incompatibility of OS X 10.4.10 with FruitMenu (*). I therefore did not upgrade the MacOS on my main partition and went back to that original partition continuing on 10.4.8. The Sandbox feature of SuperDuper is therefore useful.

However, as it turned out later, the problem with the OS update was only on the sandbox partition! I found out because I later ran the OS update on a full featured backup of my system, on a mirror of my main drive. The said problem did not exist anymore.

I conclude that there is something very particular (and strange) happening when running a System via Aliases (or Symbolic Links ?) where the home folder is accessed via an Alias.

I know it would be easy to blame Unsanity in this case - but their software works FINE with SuperDuper! (when not on a Sandbox partition).

The effect which I discovered defeats the whole purpose of Sandbox and makes me wonder: What if also other glitches which I could discover (running from Sandbox) only happen on Sandbox but are fine when running in standard mode ?


-Martin

(*) When accessing an empty folder from FruitMenu, Finder crashes. Normally a grayed out item would show in the sub menu (I think saying "empty folder"), but FruitMenu seems to have problems finding anything and causes Finder to crash. The problem should be able to be reproduced.