mdoc: Reorder manpage sections to keep them consistent.

* Keep CAVEATS and BUGS sections at the end of the pages.
* EXIT STATUS section should come after ENVIRONMENT.

Found-with: mandoc -Tlint
Revi

mdoc: Reorder manpage sections to keep them consistent.

* Keep CAVEATS and BUGS sections at the end of the pages.
* EXIT STATUS section should come after ENVIRONMENT.

Found-with: mandoc -Tlint
Reviewed-by: Sacha Wildner <swildner@>

show more ...

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.

jscan: Fix SYNOPSIS and sync usage()

Fix typos, mostly effect -> affect.

Miscellaneous mdoc fixes.

Fix typo.

Next round of fixing all kinds of spelling mistakes.

Another round of spelling fixes in manpages, messages, readmes etc.

Fix typos.

Remove trailing whitespace.

Remove redundant .Pp macros right before .El, .Sh and .Ss.

* Only use two digits for DragonFly version numbers referenced from the
man pages.

* Adjust mdoc.local accordingly.[1]

[1]Submitted-by: Francis Gudin <fgudin@nerim.net>

Rework and expand the algorithms in JSCAN, part 3/?.

* Have the debug dump print out raw record transaction id's.
* Fix a number of bugs in the prefix set code (the files were being
strtoul'd in b

Rework and expand the algorithms in JSCAN, part 3/?.

* Have the debug dump print out raw record transaction id's.
* Fix a number of bugs in the prefix set code (the files were being
strtoul'd in base 10 rather then base 16).
* Make multiple commands on the command line work (e.g. -w and -m together).
* Fix a few jseek() bugs.
* Add '-f' which operates like tail -f and allows a batch operation on e.g.
a prefix file set to poll for more data.

Still TODO: ACK protocol, raw output (-o/-O) protocol, temporary mode for
record files (-W), and many other things.

show more ...

Rework and expand the algorithms in JSCAN, part 2/?.

* Implement session tracking so multiple output commands can be independantly
tracked. However, currently only one output command may be speci

Rework and expand the algorithms in JSCAN, part 2/?.

* Implement session tracking so multiple output commands can be independantly
tracked. However, currently only one output command may be specified
(e.g. -w or -m, not both, yet)
* The session code now updates transaction id files, giving us a general
restart capability on the userland side.
* Prefix set record mode (-w) should now work, including journal restarts.
* Running a mirror (-m) on an active prefix set should now operate properly
in batch mode.

Many things are still not working yet.

show more ...

Rework and expand the algorithms in JSCAN, part 1/2. Implement a new
infrastructure in the userland jscan program to create a framework for
supporting the following:

* Pipe-throughs (without storin

Rework and expand the algorithms in JSCAN, part 1/2. Implement a new
infrastructure in the userland jscan program to create a framework for
supporting the following:

* Pipe-throughs (without storing data in a buffering file).
* File-based buffering
* Streamed replication of journaled data.
* Sequenced output files limited to a specific size (to match against
backup media)
* Transaction id tracking to support journal restarts and resynchronization.
This is needed to make off-site and networked backups reliable.
* Decoupled journal operations. e.g. (once finished) we will be able to run
a jscan in realtime to record journal data, and another one in batch to
take that data and use it to maintain a mirror or to send it to another
machine in a restartable and resynchronizable manner.
* Infrastructure to be able to scan a journal forwards or backwards by
an arbitrary number of raw records and maintain a mirror in both
the forwards (redo) and backwards (undo) direction based on that ability.
* Infrastructure that will aid in the preferred backup methodology of
maintaining a real time mirror and UNDO/REDO journal on a 100% full
backup partition such that one is able to free space on the partition
simply by removing the oldest journaling file.
* Infrastructure that will make it easier to solve the overlapping
meta-transaction problem illustrated below:

current synchronization point
V
[ ][ ][ ][ ][ ][ ][ ][ ][ ][ ][ ][ ] <= Raw records
A <= meta transaction A
B B B B <= meta transaction B
C C C <= meta transaction C
D D <= meta transaction D
E E <= meta transaction E


As you can see, the point at which a journal is 'broken' could
be right smack in the middle of several meta transactions at
once, due to the fact that meta transactions are laid out as
their records can be generated and multiple processes could be
modifying the filesystem at the same time.

If we are attempting to mirror this data, only transactions A and E
will have been completed and issued to the mirror. If the journal
is broken at the sychnronization point and then restarted, in
order to pick up where we left off we have to scan existing
journal records all the way back to the first 'B' in order to
recover transactions B and C, then continue recording the journal
from the synchronization point until those transactions are complete
and can be issued to the mirror. The difficulty here is that we
have to carefully track exactly what needs to be synchronized.
In recovering transaction 'B' and 'C' we do not want to reissue
transaction E, for example, which had already been completed prior to
the break.

The problem exists in both the forwards and reverse direction, and
we need to be able to go in both directions to control the 'snapshot'
view the mirror is presenting to us.

NOTE: this is just part 1/2. This code and the new options are
NON WORKING at the moment.

show more ...

Clean up manual page.

Remove trailing blank space characters. mdoc(7) explicitly recommends doing
so lest troff might get confused.

Add an option and test implementation for the full-duplex ack protocol.

Major continuing work on jscan, the userland backend for the journaling
system.

* Fix bugs in the stream demultiplexing code. Only the first stream header
is supposed to be passed to the virtuali

Major continuing work on jscan, the userland backend for the journaling
system.

* Fix bugs in the stream demultiplexing code. Only the first stream header
is supposed to be passed to the virtualized stream code. We were passing
the stream header and trailer for each meta record and the extra meta-data
really confused the virtualized stream scanning code.

* Add support for unknown nesting record sizes. This occurs when the
nesting record in the virtual stream is too large to fit in the kernel's
in-memory journal FIFO. This allows us to arbitrarily push and pop
elements of a transaction without having to know the size of the completed
transaction in advance.

* Use a 64 bit integer to calculate the completed transaction size. Note
however that currently the stream reconstruction code uses malloc so
there are serious limits to what it can reconstruct.

* Implement (partial) support for mirroring. Only basic file and directory
creation, write, remove, and rename is currently decoded.

The TODO list is long and varied. We need to use mmap() instead of malloc()
to reference journal data. We need to finish implementing mirror mode. We
need a catch-up or restart mode for the mirror. We need raw journal data
logging, we need stream ackknowledgements, and a thousand other things.

This example will maintain a mirror of /usr in /usr_mirror in real time.
Again, remember that there is a lot more work to do.... the mirroring isn't
perfect by a long shot. We don't do symlinks for example, yet, and there
are many other issues.

# Warning: do not ^Z mountctl!
cpdup /usr /usr_mirror
cd /usr_mirror
mountctl -a /usr:test | jscan -m stdin
[does not return]
[to terminate, type 'mountctl -d test' in another shell window]

show more ...

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 reada

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.

show more ...

Fix some more the the typos.

Fix various mdoc issues in various manual pages.