]>
Commit | Line | Data |
---|---|---|
1 | $Id: CHANGES,v 1.25 1999/12/06 21:37:47 tiniou Exp $ | |
2 | ||
3 | Changes between versions 0.4b11 and 0.4b12 (released ????????????????) | |
4 | ====================================================================== | |
5 | ||
6 | 1. Small fix in the dump man page. Thanks to Thorsten Kukuk | |
7 | <kukuk@suse.de> for submitting the patch. | |
8 | ||
9 | Changes between versions 0.4b10 and 0.4b11 (released December 5, 1999) | |
10 | ====================================================================== | |
11 | ||
12 | 1. Added a '--enable-kerberos' to configure. | |
13 | ||
14 | 2. Added a 'S' option to dump which determines the amount of space | |
15 | that is needed to perform the dump without actually doint it, similar | |
16 | to the Sun's ufsdump 'S' option. Patch contributed by Rob Cermak | |
17 | <cermak@ahab.rutgers.edu>. | |
18 | ||
19 | 3. Added a 'M' multi-volume option to dump and restore which enables | |
20 | dumping to multiple files (useful when dumping to an ext2 | |
21 | partition to make several dump files in order to bypass the 2GB | |
22 | file size limitation). The 'f' argument is treated as a prefix and | |
23 | the output files will be named <prefix>001, <prefix>002 etc. With | |
24 | the 'M' flag, restore automatically selects the right file without | |
25 | asking to enter a new tape each time. | |
26 | ||
27 | 4. Fixed a memory leak which was causing dump to grow very big | |
28 | (270MB when dumping a 10GB filesystem...). Thanks to Zaphod | |
29 | Beeblebrox <zaphod@netrider.org.au> for reporting the bug. | |
30 | ||
31 | Changes between versions 0.4b9 and 0.4b10 (released November 21, 1999) | |
32 | ====================================================================== | |
33 | ||
34 | 1. Make configure test if the system glob routines support | |
35 | extended syntax (ALTDIRFUNC). If not, use the internal glob | |
36 | routines instead of system ones. Thanks to Bernhard Sadlowski | |
37 | <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug | |
38 | and helping me resolve this and other minor libc5 compiling | |
39 | glitches. | |
40 | ||
41 | 2. Fix a problem when dumping a ext2fs with the 'filetype' | |
42 | feature enabled. Thanks to Patrick J. LoPresti | |
43 | <patl@cag.lcs.mit.edu> for reporting the bug and to | |
44 | Theodore Y. Ts'o <tytso@mit.edu> for providing the patch. | |
45 | ||
46 | 3. Made the nodump flag work on directories. A directory which | |
47 | has the nodump flag gets never dumped, regardless of its | |
48 | contents. | |
49 | ||
50 | 4. Integrate a patch from Jeremy Fitzhardinge <jeremy@goop.org> | |
51 | which allows dump on an active ext3 filesystem. However, this | |
52 | is a "quick and dirty" patch which enables backup of an ext3 | |
53 | filesystem through the ext2 compatibility (by ignoring the | |
54 | NEEDS_RECOVERY bit). The journal file is not recognized and | |
55 | it is dumped (it should not). | |
56 | ||
57 | 5. Test the superblock compatibility flags when dumping, in order | |
58 | to be sure that we know how to deal with specific features. | |
59 | ||
60 | Changes between versions 0.4b8 and 0.4b9 (released November 5, 1999) | |
61 | ==================================================================== | |
62 | ||
63 | 1. Use lchown instead of chown, fixing a possible security problem | |
64 | when restoring symlinks (a malicious user could use this | |
65 | to deliberately corrupt the ownership of important system files). | |
66 | Thanks to Chris Siebenmann <cks@utcc.utoronto.ca> for detecting | |
67 | this and providing the patch. | |
68 | ||
69 | Changes between versions 0.4b7 and 0.4b8 (released November 3, 1999) | |
70 | ==================================================================== | |
71 | ||
72 | 1. Put dump sources under CVS, added Id tags in all files so | |
73 | one can use 'ident' on binary files. | |
74 | ||
75 | 2. Added the dump/restore version in the usage text so one can | |
76 | easily verify the version he is using. | |
77 | ||
78 | 3. Small patch from Nuno Oliveira <nuno@eq.uc.pt> which fixes | |
79 | a va_start/va_end problem on linux-ppc (always call va_start | |
80 | va_end in pairs each time we use a vararg function). | |
81 | ||
82 | 4. Added again the DT_* constants because old libc does not | |
83 | contain them :(. Thanks to Eric Maisonobe <virnet@nat.fr> | |
84 | for submitting the bug report. | |
85 | ||
86 | 5. Use ext2fs_llseek instead of llseek. With recent e2fsprogs | |
87 | this should enable dumping big (huge) filesystems. | |
88 | ||
89 | 6. Added the RSH environment variable in order to be able to | |
90 | use a rsh replacement like ssh when doing remote backups (and | |
91 | bypass the security limitations of rcmd). Now you can do remote | |
92 | backups without being root (or making dump setuid root). | |
93 | ||
94 | 7. Modified again the way dumpdates works. For incremental dumps, | |
95 | we need to read dumpdates even if we are not using 'u' option. | |
96 | Thanks to Bdale Garbee <bdale@gag.com> for his ideas on how | |
97 | this should work. | |
98 | ||
99 | Changes between versions 0.4b6 and 0.4b7 (released October 8, 1999) | |
100 | =================================================================== | |
101 | ||
102 | 1. Removed the 'k' flag from the restore 'about' text if kerberos | |
103 | was not compiled in. | |
104 | ||
105 | 2. Prototyped (f)setflags from e2fsprogs and corrected the calls | |
106 | to them (fsetflags takes a char*, setflags an open fd!). | |
107 | ||
108 | 3. (f)setflags is called only if the flags aren't empty. If the | |
109 | file is a special file, a warning is printed, because changing | |
110 | flags implies opening the device. Normally, a special file | |
111 | should not have any flag... (Debian bug #29775, patch provided | |
112 | by Abhijit Dasgupta <abhijit@ans.net>). | |
113 | ||
114 | 4. Made possible to dump a file system not mentioned in /etc/fstab. | |
115 | (Debian bug #11904, patch provided by Eirik Fuller <eirik@netcom.com>). | |
116 | ||
117 | 5. Changed the default behaviour to not create dumpdates | |
118 | unless 'u' option is specified. Removed the old "debian-patch" | |
119 | which provided the same thing. (Debian bug #38136, #33818). | |
120 | ||
121 | 6. Removed all those dump*announce, since they were getting old... | |
122 | ||
123 | 7. Added warning messages if dumpdates does not exist and | |
124 | when an inferior level dump does not exist (except for a level 0 | |
125 | dump). | |
126 | ||
127 | 8. Debugged the glob calls in interactive mode: restore used a | |
128 | dirent struct which was different from the /usr/include/dirent.h | |
129 | one (this used to work, is it a glibc2 change?), so none of the | |
130 | compat glob (which used /usr/include/dirent.h) or the system glob | |
131 | worked. Restore use now the system dirent (and the system | |
132 | DT_* constants), which are compatible with BSD ones. | |
133 | ||
134 | 9. Added a configure flag (--with-dumpdatespath) to specify | |
135 | the location of dumpdates file. By default, it is | |
136 | /etc/dumpdates. | |
137 | ||
138 | 10. Added the "AUTHOR" and "AVAILABILITY" sections and | |
139 | included the current date/version in man pages. | |
140 | ||
141 | 11. Corrected the estimation of remaining time when | |
142 | the operator doesn't change the tapes quickly enough. This | |
143 | was an old bug, I thought I corrected it, and discovered | |
144 | that in fact it was corrected in two different places, so | |
145 | the results canceled each other... | |
146 | ||
147 | Changes between versions 0.4b5 and 0.4b6 (released October 1, 1999) | |
148 | =================================================================== | |
149 | ||
150 | 1. Integrated multiple patches from RedHat, Debian and SuSE: | |
151 | ||
152 | - tweak dump/itime.c to not try to read dumpdates if the 'u' option | |
153 | isn't specified. | |
154 | - several fixes in the man pages. | |
155 | - update the default tape device to /dev/st0. | |
156 | - many updates for Linux Alpha (byte ordering, size_t etc). | |
157 | - buffer overruns. | |
158 | - use environment variable for TMPDIR (instead of /tmp). | |
159 | - use sigjmp_buf instead of jmp_buf (RedHat bug #3260). | |
160 | - workaround egcs bug (RedHat bugs #4281 and #2989). | |
161 | - wire $(OPT) throughout Makefile's. | |
162 | ||
163 | 2. Upgrade the dump revision to 1, making possible to dump filesystems | |
164 | made with e2fsprogs-1.15 or newer. Nothing seems to break... | |
165 | ||
166 | 3. Fix some compile warnings, prototype all functions. | |
167 | ||
168 | 4. Use glibc err/glob instead of internal compatibility | |
169 | routines (only if available). | |
170 | ||
171 | 5. Fix a compile error on Linux 2.2.7 / libc5 (5.4.44) (patch provided | |
172 | by Bernhard Sadlowski <sadlowsk@mathematik.uni-bielefeld.de>). | |
173 | ||
174 | Changes between versions 0.4b4 and 0.4b5 (released September 22, 1999) | |
175 | ====================================================================== | |
176 | ||
177 | 1. Integrated the changes from FreeBSD-3.1-RELEASE | |
178 | (mostly bug fixes, buffer overruns, dump has now an "automatic | |
179 | tape length calculation" flag, dump/restore can use kerberos now | |
180 | (this is NOT tested), use environment variables for TAPE and | |
181 | RMT etc.). | |
182 | ||
183 | 2. Integrated three RedHat patches ("glibc", "kernel" and "bread" patches) | |
184 | ||
185 | 3. Corrected a bug in restore when using 'C' option with multi-volumes | |
186 | tapes (files splited accros two tapes give "size changed" errors | |
187 | when comparing). | |
188 | ||
189 | 4. Corrected the long standing bug when dumping multiple tapes. | |
190 | This works for me, needs further testing. | |
191 | ||
192 | Changes between versions 0.4b3 and 0.4b4 (released January 17, 1997) | |
193 | ==================================================================== | |
194 | ||
195 | 1. Dump now runs correctly on kernels 2.1.x | |
196 | Fix made by Gerald Peters <gapeters@worldnet.att.net> | |
197 | ||
198 | Changes between versions 0.4b2 and 0.4b3 | |
199 | ======================================== | |
200 | ||
201 | 1. Use realpath() if available | |
202 | ||
203 | 2. Report statistics | |
204 | ||
205 | Changes between versions 0.4b1 and 0.4b2 | |
206 | ======================================== | |
207 | ||
208 | 1. Fixed the bug fix from Greg Lutz (I had made a mistake when integrating | |
209 | the patch) | |
210 | ||
211 | 2. Fixed restore to make it able to read FreeBSD 2.x dumps again | |
212 | ||
213 | 3. Fixed configure.in to correctly handle --enable-rmt | |
214 | ||
215 | Changes between versions 0.3 and 0.4b1 | |
216 | ====================================== | |
217 | ||
218 | 1. Integrated the changes from 4.4BSD-Lite2 | |
219 | ||
220 | 2. Integrated the patches from Debian and Red Hat | |
221 | ||
222 | 3. Portability changes: use the __u32, __u16, __s32, and __s16 types | |
223 | ||
224 | 4. Changed dump to use the Ext2fs library to get block addresses. This | |
225 | should solve the endianness problem on SparcLinux. | |
226 | ||
227 | 5. Created a configure.in file (shamelessly stolen from the e2fsprogs | |
228 | distribution's one) to use autoconf | |
229 | ||
230 | 6. Fixed a few minor bugs | |
231 | ||
232 | Changes between versions 0.2e and 0.2f | |
233 | ====================================== | |
234 | ||
235 | 1. Added the creation of named pipes (fifos) in restore. | |
236 | ||
237 | 2. Added the -N flag in the restore manual page. | |
238 | ||
239 | 3. Added the file kernel.patch which contains the llseek() optimization | |
240 | patch for 1.2.x kernels. | |
241 | ||
242 | 4. Fixed a bug in the restoration of symbolic links: owner and group were | |
243 | not restored. | |
244 | ||
245 | 5. Integrated some changes from FreeBSD 2.2. | |
246 | ||
247 | 6. Added a call to ftruncate() after restoring each file to restore | |
248 | correctly files ending by a hole. | |
249 | ||
250 | Changes between versions 0.2d and 0.2e | |
251 | ====================================== | |
252 | ||
253 | 1. Fixed a bug in the "set owner/mode" process. Every file was restored | |
254 | with owner = root (0) and group = root/wheel/whatever (0). | |
255 | ||
256 | Changes between versions 0.2c and 0.2d | |
257 | ====================================== | |
258 | ||
259 | 1. Dump is now able to backup 2GB+ filesystems. | |
260 | ||
261 | 2. Dump and restore can now be linked as static binaries. | |
262 | ||
263 | Changes between versions 0.2b and 0.2c | |
264 | ====================================== | |
265 | ||
266 | 1. Fixed a bug when dumping ``slow'' (i.e. normal) symbolic links. | |
267 | ||
268 | Changes between versions 0.2a and 0.2b | |
269 | ====================================== | |
270 | ||
271 | 1. Really fixed the bug that I should have corrected in 0.2a. | |
272 | ||
273 | 2. Enabled optimization again. | |
274 | ||
275 | Changes between versions 0.2 and 0.2a | |
276 | ===================================== | |
277 | ||
278 | 1. Disabled the optimization during compilation. | |
279 | ||
280 | Changes between versions 0.1 and 0.2 | |
281 | ==================================== | |
282 | ||
283 | 1. Fixed a bug in fstab.c which caused a null pointer to be stored in | |
284 | the fs_type field (actually, I modified the file fstab.c to make it | |
285 | use the mntent functions). | |
286 | ||
287 | 2. Dump and restore now use a 4.3 BSD compatible dump format. Backups | |
288 | made by dump should be readable by the BSD restore and backups made | |
289 | by the BSD dump should be readable by restore. Unfortunately, this | |
290 | means that the dump format has changed between version 0.1 and version | |
291 | 0.2 :-( | |
292 | ||
293 | 3. Dump is now able to backup a subtree, it is no longer limited to whole | |
294 | filesystems like the BSD version. | |
295 | ||
296 | 4. Dump now uses ext2_llseek() so it is able to backup filesystems bigger | |
297 | than 2 GB. | |
298 | ||
299 | Changes between versions 0.0 and 0.1 | |
300 | ==================================== | |
301 | ||
302 | 1. Now create links rdump and rrestore during the `make install' step. | |
303 | ||
304 | 2. Linux port specific bugs added to the manual pages | |
305 | ||
306 | 3. Incorrect estimation of the number of tapes blocks fixed when doing | |
307 | incremental backups. | |
308 | ||
309 | 4. Better ls-like format in restore in interactive mode. |