> > > Packages will be backed up to whatever disk is in the > > > drive - make sure you put the appropriate disk in the > > > boot drive before backing up. > > > I have a small request that the backup scripts write to > > the drive from which the package was loaded. Would that > > be a major rewrite? > > Not a major rewrite, but a major project nonetheless. > > You have to add the following capabilities to the system: > > * Tracking where files came from - including storing data, additions, > deletions, and everything else - a new database really. MySQL anyone?
How about a flat text file per-package? > * Unique identifiers for disks - including checking for the right one > and error handling for the case when it isn't. > > This would be a big project to get right, requires a database with > full database accessability, and identifiers for disks that are > guaranteed to be right. What's more, what if you can't back the > package up to the right disk but want to back up to a new disk - more > functions. I've got this functionality in my backup scripts for Dachstein already (and it was a fairly major re-write). The system "remembers" where the package was loaded from, and defaults to backing up to the same location. You can also manually change the backup destination, if desired. The default backup destination menu is populated with the devices from PKGPATH= and BOOT= (which are assumed to be places you'd like to store packages :-), but you can type in alternate device names manually... Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
