First cut of the jscan utility. This will become the core utility for
authorMatthew Dillon <dillon@dragonflybsd.org>
Mon, 7 Mar 2005 02:38:28 +0000 (02:38 +0000)
committerMatthew Dillon <dillon@dragonflybsd.org>
Mon, 7 Mar 2005 02:38:28 +0000 (02:38 +0000)
commitce5e5ac4c90e9b2b818374657408b15978bc06db
tree18f7457689951031995da7e8b5a893b138fdfc84
parent6348892b197761d3d860b2fb5977adef05f566f7
First cut of the jscan utility.  This will become the core utility for
scanning journaling files (e.g. as created by mountctl).  The utility is
currently able to dump a journaling file in human readable format forwards
or backwards.  It will eventually be capable of tracking and mirroring,
undo, security audits, partial restores, sanity checks, and other operations.

Most of the scanning infrastructure is in as of this commit, but the code
currently tries to cache the entire transaction into memory which will
fail for large (e.g. multi gigabyte) transactions.  The API's are abstracted
with the intent of being able to page out or do on-the-fly mmaping of the
underlying data in the future rather then copying it into memory.
sbin/Makefile
sbin/jscan/Makefile [new file with mode: 0644]
sbin/jscan/dump_debug.c [new file with mode: 0644]
sbin/jscan/jfile.c [new file with mode: 0644]
sbin/jscan/jscan.8 [new file with mode: 0644]
sbin/jscan/jscan.c [new file with mode: 0644]
sbin/jscan/jscan.h [new file with mode: 0644]
sbin/jscan/jstream.c [new file with mode: 0644]
sbin/jscan/subs.c [new file with mode: 0644]