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