-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eric Spakman wrote:
>>> I'm not sure if it's obvious if >>> backup fails that the above entry can be the fault, if a note is added >>> in the leaf.cfg file that the first entry is the backup device in the >>> PKGPATH >>> it could be clearer. But I'm still not sure what to do... >> >> In alpine, you have to specify where to commit: >> >> lbu commit floppy lbu commit usb >> >> where the target needs to exist in /etc/fstab and be mounted in /media/*. >> If no target is specifide, lbu will try to use $LBU_MEDIA. >> > That is also possible in the config system from Bering-uClibc, it's not > that difficult to parse LRPKGPATH and ask which device to backup to and > when it fails defaulting to the first device in the list. I think I will > implement something like that. Note that there is a big difference between the backup failing, and the mount -rw of the backup media failing, so you could make sensible error messages for both cases. Note that with the possible myriad of read-only devices (including write-protected floppies and USB sticks, not to mention the many possible CD-ROM device IDs), I don't think there is a clean way to 'extract' any read-only devices from the PKGPATH list. I'd personally just make a sensible error message (ie: Can't mount <backupdev> read-write...perhaps it's a CD-ROM or write protected?). - -- Charles Steinkuehler [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEjc9XLywbqEHdNFwRAlpEAKDmo1pREEnXjtA22yusOWwYNYlfKgCg01/m VJsDJugHY5M10WOUfmiKKQs= =aQbH -----END PGP SIGNATURE----- _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
