Charles Steinkuehler wrote: >
[ snip ] > > 2) WRT the backup and readonly, Charles was suggesting that he will > default > > the backup location to be adjusted if the files are loaded from a r/o > drive. > > Have you considered the case (that I use all the time) where some files in > > question are loaded from a write protected floppy but when it comes to > > backing up, it's just a matter of popping out the floppy, write enabling > > then popping it back in. If the backup location is altered because the > > floppy booted write protected (read only), that would screw me up (or > > require me to boot with write protection off)! > > So far, the only reliable way I've been able to test for RO vs RW is to > check /proc/mounts, and I'm not real anxious to add even more reliance on > the /proc directory (which is not guaranteed to remain stable from one > kernel version to the next). If I do implement this functionality, the > backup location for a package would default to the boot= device if all > located packages were on RO devices, and boot= *should* be writable storage > area, even if it isn't writable when booting. Why not simply *read* it from a file? Then, we could configure the file to our liking and be done with it -- unless, of course, during a particular backup where we can also select an alternative? Remember, you are already doing this for *.bktype . . . -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
