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