notes regarding files within the debs I retrieved tonight from
http://distro.ibiblio.org/refracta/files/Testing/refracta2usb-0.9.5.deb 2014-Feb-21
/usr/share/doc/refracta2usb/readme.refracta2usb.txt
conf file within this deb indicates version is
9.0.4vs outdated readme.refracta2usb.txt still states
refracta2usb v.07-=-
help_r2u.txt states
refracta2usb version: 9.0.5 (hmm, packaged within a deb named 0.9.5)
Several months ago, I had suggested merging the documentation into a (one) single helpfile.
This time 'round, I'm second-guessing that suggestion.
Instead, I think users would be better served by providing multiple .desktop files in the package
(to display in the DE menu immediately following, alphabetically, the refracta2usb launcher)
and
by placing a boilerplate block of comment lines atop each of the multiple files
which likely need the user's attention (or congfiguration tweaks) prior to initial
refracta2usb operation
# ==== THESE MERIT YOUR ATTENTION
# ==== PRIOR TO PERFORMING refracta2usb OPERATION:
# /usr/share/doc/refracta2usb/readme.refracta2usb.txt
# /usr/share/doc/refracta2usb/help_r2utxt
# /usr/lib/refracta2usb/r2u_exclude.list
# ==== ALSO (POSSIBLY, OPTIONALLY)
# /usr/lib/refracta2usb/patch-live-initrd/readme.txt
# /usr/lib/refracta2usb/examples/live.cfg
# /usr/lib/refracta2usb/syslinux/menu.cfg
BTW, the left-side indenting along with less than 80 column line
length creates a difficult reading experience. The long strings within
the documentation representing paths don't fit this imposed
constraint anyhow, so why expect/demand the user
slurp 700+ lines of chunky documentation through a straw?
====================
file:
/usr/lib/refracta2usb/r2u_exclude.liststill states
refracta2usb 0.7(if nothing has changed since, maybe this is proper/correct?)
====================
As is, it's difficult/impossible to follow the link (
http://www.ibiblio.org/refracta ) at
https://github.com/fsmithred/refractaand find one's way to
http://distro.ibiblio.org/refracta/files/Testing/^--- suggest the github page should provide links to both
and, optionally, cite the github url within the Testing/readme.txt document
==========================
Reiterating something else I mentioned months ago:
For refracta2usb, the exclude list is MUCH more sparse than the default list provided for refractasnapshot.
If, as dzz pointed out, it's advisable to to exclude the file containing "
machineID" when performing a snapshot...
...surely it's equally important to consider such details during refracta2usb configuration
refracta2usb.conf
# This only gets used in mkusbcrypt if you copy /home from the running live system instead of from an iso file.
excludes_file="/usr/lib/refracta2usb/r2u_exclude.list"
Above, I've added bolding.
Point of confusion: "This only gets used (in mkusbcrypt) if..."
Without mkusbcrypt in the operation, the exclude file isn't referenced regardless of other variable factors?