| ca99f49b |
1 | --- MANUAL.orig 2002-05-21 15:41:21.000000000 +0200 |
| 2 | +++ MANUAL 2005-05-14 19:23:14.676771648 +0200 |
| 3 | @@ -83,11 +83,11 @@ |
| 4 | can do with this one is creating SFV files, check single files against their |
| 5 | CRC listed in a SFV, check all files listed in a SFV and count the number |
| 6 | of existing / missing files. And if you're pissed off one day and don't want |
| 7 | -to use pdSFV anymore, you don't need to worry about compatibility with other |
| 8 | -programs. pdSFV can read them all and is pretty flexible in the files it |
| 9 | +to use BSDSFV anymore, you don't need to worry about compatibility with other |
| 10 | +programs. BSDSFV can read them all and is pretty flexible in the files it |
| 11 | creates. |
| 12 | |
| 13 | -I've included the full source for pdSFV/Unix and I tried to keep its routines |
| 14 | +I've included the full source for BSDSFV/Unix and I tried to keep its routines |
| 15 | as simple as possible and easy to read. I want to encourage any skilled |
| 16 | and interested programmer out there to do his own SFV utility, since there |
| 17 | is nothing worse than depending on a single or just a few persons concerning |
| 18 | @@ -140,8 +140,8 @@ |
| 19 | |
| 20 | |
| 21 | |
| 22 | -2. Using pdSFV |
| 23 | --------------- |
| 24 | +2. Using BSDSFV |
| 25 | +--------------- |
| 26 | |
| 27 | The stuff you got here is raw meat. It's one of my quick&dirty productions |
| 28 | and surely not lamer-proof. If handled improperly, it'll prolly segfault |
| 29 | @@ -150,11 +150,11 @@ |
| 30 | let the ppl have it. |
| 31 | |
| 32 | Before you can use it, you have to compile the source. To do so, issue the |
| 33 | -following command after unpacking pdsfv.c to your directory: |
| 34 | +following command after unpacking bsdsfv.c to your directory: |
| 35 | |
| 36 | -gcc -o pdsfv pdsfv.c |
| 37 | +gcc -o bsdsfv bsdsfv.c |
| 38 | |
| 39 | -(if you don't have gcc installed, try "cc -o pdsfv pdsfv.c"). I've |
| 40 | +(if you don't have gcc installed, try "cc -o bsdsfv bsdsfv.c"). I've |
| 41 | tested it under several Linux installations and the following Unixes: |
| 42 | |
| 43 | HP-UX B.10.20 A 9000/720 |
| 44 | @@ -170,11 +170,11 @@ |
| 45 | and have the compiler's error and warning messages handy. |
| 46 | |
| 47 | |
| 48 | -Try a "./pdsfv" to check out whether it worked that far. You should get |
| 49 | +Try a "./bsdsfv" to check out whether it worked that far. You should get |
| 50 | something similar to: |
| 51 | |
| 52 | === |
| 53 | -Usage: ./pdsfv [mode | option] <sfv-filename> <filename(s)> |
| 54 | +Usage: ./bsdsfv [mode | option] <sfv-filename> <filename(s)> |
| 55 | |
| 56 | Possible modes: -c : create SFV file |
| 57 | -t : test single file(s) (multiple filenames possible) |
| 58 | @@ -194,17 +194,17 @@ |
| 59 | CREATING SFV FILES |
| 60 | ------------------ |
| 61 | |
| 62 | -We need to use "pdsfv -c mysfvname.sfv filenames.*" basically to do so. Let's |
| 63 | +We need to use "bsdsfv -c mysfvname.sfv filenames.*" basically to do so. Let's |
| 64 | say we have some files myrls.rar, myrls.r00, myrls.r01, myrls.r02 which we |
| 65 | want to get listed in myrls.sfv ... |
| 66 | |
| 67 | We then could use |
| 68 | |
| 69 | -pdsfv -c myrls.sfv myrls.rar myrls.r00 myrls.r01 myrls.r02 |
| 70 | +bsdsfv -c myrls.sfv myrls.rar myrls.r00 myrls.r01 myrls.r02 |
| 71 | |
| 72 | or shorter: |
| 73 | |
| 74 | -pdsfv -c myrls.sfv myrls.r* |
| 75 | +bsdsfv -c myrls.sfv myrls.r* |
| 76 | |
| 77 | We will get an output like this: |
| 78 | |
| 79 | @@ -222,7 +222,7 @@ |
| 80 | Let's have a look at the SFV file created: |
| 81 | |
| 82 | --- |
| 83 | -; Generated by pdSFV/Unix on Thu Oct 21 19:26:48 1999 |
| 84 | +; Generated by BSDSFV/Unix on Thu Oct 21 19:26:48 1999 |
| 85 | ; |
| 86 | myrls.r00 4C27B20A |
| 87 | myrls.r01 3BB960FA |
| 88 | @@ -240,7 +240,7 @@ |
| 89 | SFV file by using the -l command line option. Let's say your bannerfile |
| 90 | is /home/lamer/mygroup.nfo, then you would use: |
| 91 | |
| 92 | -pdsfv -c myrls.sfv -l /home/lamer/mygroup.nfo myrls.r* |
| 93 | +bsdsfv -c myrls.sfv -l /home/lamer/mygroup.nfo myrls.r* |
| 94 | |
| 95 | to create the SFV file. You will get this confirmation: |
| 96 | |
| 97 | @@ -255,10 +255,10 @@ |
| 98 | Adding "all" files |
| 99 | ------------------ |
| 100 | |
| 101 | -If called without the -a command line switch, pdSFV only adds *.r?? and *.0?? |
| 102 | +If called without the -a command line switch, BSDSFV only adds *.r?? and *.0?? |
| 103 | files to the SFV. If you do a |
| 104 | |
| 105 | -pdsfv -c myrls.sfv -a myrls.r* myrls.nfo |
| 106 | +bsdsfv -c myrls.sfv -a myrls.r* myrls.nfo |
| 107 | |
| 108 | even myrls.nfo's CRC will be stored in the SFV file. Please note that this is |
| 109 | generally a bad idea to do for various reasons. That's why it's not default and |
| 110 | @@ -275,13 +275,13 @@ |
| 111 | new version of them out which support SFV files created by other tools, you |
| 112 | can switch to compatibility mode by using -w ... |
| 113 | |
| 114 | -pdsfv -c myrls.sfv -w myrls.r* |
| 115 | +bsdsfv -c myrls.sfv -w myrls.r* |
| 116 | |
| 117 | will then generate something like: |
| 118 | |
| 119 | ; Generated by WIN-SFV32 v1.5 on Thu Oct 21 19:38:23 1999 |
| 120 | instead of |
| 121 | -; Generated by pdSFV/Unix on Thu Oct 21 19:38:23 1999 |
| 122 | +; Generated by BSDSFV/Unix on Thu Oct 21 19:38:23 1999 |
| 123 | |
| 124 | You'll get the confirmation: |
| 125 | |
| 126 | @@ -301,13 +301,13 @@ |
| 127 | Examples: |
| 128 | |
| 129 | --- |
| 130 | -pdsfv -t myrls.sfv myrls.rar |
| 131 | +bsdsfv -t myrls.sfv myrls.rar |
| 132 | |
| 133 | Testing myrls.rar ... local = 0xD782FE65, listed = 0xD782FE65 - OK |
| 134 | |
| 135 | 1 file(s) tested - 1 OK - 0 bad... |
| 136 | --- |
| 137 | -pdsfv -t myrls.sfv myrls.rar myrls.r00 |
| 138 | +bsdsfv -t myrls.sfv myrls.rar myrls.r00 |
| 139 | |
| 140 | Testing myrls.rar ... local = 0xD782FE65, listed = 0xD782FE65 - OK |
| 141 | Testing myrls.r00 ... local = 0x8208D936, listed = 0x4C27B20A - BAD |
| 142 | @@ -319,9 +319,9 @@ |
| 143 | one or more of the tested files were bad. You can use this in your |
| 144 | upload check / zipscript stuff. |
| 145 | |
| 146 | -For glFTPd users: if you modify your zipscript to use pdSFV instead of |
| 147 | +For glFTPd users: if you modify your zipscript to use BSDSFV instead of |
| 148 | the sfv_check that comes with glFTPd, note that you need command line |
| 149 | -parameters with pdSFV and not just a single filename. Replace |
| 150 | +parameters with BSDSFV and not just a single filename. Replace |
| 151 | |
| 152 | cd $2 |
| 153 | /bin/sfv_check $1 |
| 154 | @@ -329,7 +329,7 @@ |
| 155 | with |
| 156 | |
| 157 | cd $2 |
| 158 | -/bin/pdsfv -t *.[sS][fF][vV] $1 |
| 159 | +/bin/bsdsfv -t *.[sS][fF][vV] $1 |
| 160 | |
| 161 | to get it working! |
| 162 | |
| 163 | @@ -341,7 +341,7 @@ |
| 164 | Use -T to test all the files listed in the sfv file! |
| 165 | |
| 166 | --- |
| 167 | -pdsfv -T myrls.sfv |
| 168 | +bsdsfv -T myrls.sfv |
| 169 | |
| 170 | Processing complete check of myrls.sfv ... |
| 171 | Testing myrls.r00 ... listed = 0x4C27B20A ... local = 0x8208D936 ... BAD |
| 172 | @@ -362,7 +362,7 @@ |
| 173 | ---------------------- |
| 174 | |
| 175 | --- |
| 176 | -pdsfv -m myrls.sfv |
| 177 | +bsdsfv -m myrls.sfv |
| 178 | |
| 179 | Performing completion check... |
| 180 | [total files listed] [local files] [missing files] |
| 181 | @@ -378,7 +378,7 @@ |
| 182 | To get the number of files existing locally (3 in our example), you |
| 183 | could use some shit like: |
| 184 | |
| 185 | -NUMLOCAL=`pdsfv -m myrls.sfv | tail -n 2 | head -n 1` |
| 186 | +NUMLOCAL=`bsdsfv -m myrls.sfv | tail -n 2 | head -n 1` |
| 187 | echo "$NUMLOCAL files of this release have arrived yet!" |
| 188 | |
| 189 | If you're a funny shellscripter you surely can use this somehow. Just |
projects / packages / bsdsfv.git / blame