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