> However, you didn't account for ALL of the possibilities:
Granted, but it does what I need...
> 1. User backs up a package - to the right medium (/dev/fd0u1440 for
> instance), but the WRONG disk (oops). Then what?
>
> 2. User backs up a package - to the right medium, but a NEW
> (different) disk. Then what?
Then we put up a big flashing error that says: Luser Malfunction! Please
get a new user. :)
> To do this right, I'd think you'd need an identifier for each and
> every disk, and a routine to refuse writing to a disk that didn't
> match - as well as the ability to write to a NEW disk.
>
> Another thing: Define The Problem. I don't see backing up to this
> disk or that a problem. What Problem does all this extra code solve?
The problem solved is administration on a system with multiple package
sources, and the same package existing in more than one place (my CD based
distos). Once you boot off CD, configure, and backup a package, the system
"remembers" where your backup lives, loads that data on the next reboot, and
sets that location as the default backup destination (although this can be
manually changed, if desired).
Why does this exist?
It makes my life administering a bunch of CD-ROM booting firewalls a lot
easer...it works for me, YMMV.
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
