|
|
1.1 root 1: .\" @(MHWARNING)
2: .TH BBTAR 8 "April 22, 1986" MH [mh.6]
3: .UC 6
4: .SH NAME
5: bbtar \- generate the names of archive files to be put to tape
6: .SH SYNOPSIS
7: .in +.5i
8: .ti -.5i
9: @(BBHOME)/bbtar
10: \%[private] \%[public]
11: .in -.5i
12: .SH DESCRIPTION
13: The \fIbbtar\fR program reads the BBoards database and produces on its
14: standard output the names of BBoards archives which should be put to tape,
15: for direct use in a \fItar\fR\0(1) command.
16:
17: If the argument `private' is given,
18: only private BBoards are considered.
19: If the argument `public' is given,
20: only public BBoards are considered.
21: This lets the BBoards administrator write two tapes,
22: one for general read\-access (the public BBoards),
23: and one for restricted access.
24: The default is all BBoards
25:
26: For example:
27:
28: .nf
29: .in +.5i
30: cd archive # change to the archive directory
31: tar cv `bbtar private` # save all private BBoard archives
32: .in -.5i
33: .fi
34:
35: After the archives have been saved to tape,
36: they are usually removed.
37: The archives are then filled again,
38: usually automatically by cron jobs which run \fIbbexp\fR\0(8).
39: .Fi
40: ^@(BBHOME)/BBoards~^BBoards database
41: .Pr
42: None
43: .Sa
44: bboards(5), bbexp(8)
45: .De
46: None
47: .Co
48: None
49: .En
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.