]>
Commit | Line | Data |
---|---|---|
1c736b78 | 1 | $Id: CHANGES,v 1.194 2002/09/02 12:20:26 stelian Exp $ |
d86089d1 SP |
2 | |
3 | Changes between versions 0.4b31 and 0.4b32 (released ?????????????) | |
4 | =================================================================== | |
5 | ||
6 | 1. Changed dump to use fcntl(F_SETLK) style locking instead | |
7 | of flock() when locking the dumpdates file. With the old | |
8 | locking scheme, a local user having read rights on the | |
9 | dumpdates file could be able to do a Denial of Service attack | |
10 | on dump. In order to lock the dumpdates file with the new | |
11 | scheme, the user would need to have write access on the file. | |
12 | Thanks to Richard Johnson <Richard.Johnson3@ey.com> for | |
13 | reporting the bug (originally a bugtraq post). | |
ba3af39e | 14 | |
2f562f4e SP |
15 | 2. Fixed interactive 'ls' which caused spurious errors warnings |
16 | about 'undefined filetypes' detected. Thanks to Jorgen Ostling | |
17 | <jorgen_ostling@users.sourceforge.net> for reporting this | |
18 | bug. | |
19 | ||
1c736b78 SP |
20 | 3. Fixed dump's estimate when dealing with sparse inodes. |
21 | ||
cbc7fd6a | 22 | Changes between versions 0.4b30 and 0.4b31 (released July 30, 2002) |
ba3af39e SP |
23 | =================================================================== |
24 | ||
25 | 1. Fixed rmt open flags transmission (GNU's symbolic syntax over | |
26 | rmt) which I broke in 0.4b29. Thanks to Eros Albertazzi | |
27 | <eros@lamel.bo.cnr.it> for reporting the bug. | |
35952b8f | 28 | |
4095abc0 SP |
29 | Changes between versions 0.4b29 and 0.4b30 (released July 25, 2002) |
30 | =================================================================== | |
aa1b1e7f SP |
31 | |
32 | 1. Made dump print out the ext2 logical block number in case of a read | |
33 | error, which can be given as an argument to debugfs' ncheck command, | |
34 | in order to find out the affected inode. Added note about this | |
35 | usage in dump's man page. | |
ed7c25a3 SP |
36 | |
37 | 2. Fixed a problem in restore when reading tapes written on big | |
38 | endian machines with very old versions of dump. The patch was | |
39 | contributed by George Helffrich <george@geology.bristol.ac.uk>. | |
f75cc889 SP |
40 | |
41 | 3. Fixed the tape length calculation when using large tapes | |
42 | and compression. Thanks to Georg Lippold | |
43 | <g_lippold@sourceforge.net> for reporting the bug. | |
a9c5ed48 SP |
44 | |
45 | 4. Added a new set of examples in dump_on_cd_2 directory, based | |
46 | on dump_on_cd examples but somewhat enhanced, supporting DVD | |
47 | media, and localized in english and german. Thanks to | |
48 | Georg Lippold <g_lippold@sourceforge.net> for the new scripts. | |
49 | ||
9ca70cf6 SP |
50 | 5. Made dump save 32 bit UID/GID. Internally, this was achieved |
51 | by switching from the old BSD inode format to the new BSD | |
52 | inode format, which means that the tape format was changed. | |
53 | However, since all restore versions out there should | |
54 | transparently support both inode formats, the change should | |
55 | have no side effects. Thanks to John Yu <jky@cs.bu.edu> for | |
56 | reporting the bug. | |
a18d5997 SP |
57 | |
58 | 6. Fixed a lot of warnings in the code shown when compiling | |
59 | with 'gcc -W'. Thanks to Matthias Andree | |
60 | <matthias.andree@stud.uni-dortmund.de> for reporting this. | |
61 | ||
2a2e321d SP |
62 | 7. Fixed a small markup bug in the dump man page. Thanks to |
63 | Eric S. Raymond <esr@minx.thyrsus.com> for submitting the | |
64 | patch. | |
65 | ||
153f9a83 SP |
66 | 8. Rewrote entirely the man pages using the tmac.an macro |
67 | package (Linux man page format) instead of the original BSD | |
68 | format. They should be now cleaner and easier to modify. | |
69 | ||
cf88ef4c SP |
70 | Changes between versions 0.4b28 and 0.4b29 (released June 8, 2002) |
71 | ================================================================== | |
d24dc8af SP |
72 | |
73 | 1. Fixed a problem in the rmt ioctl command, where ioctl's issued from | |
74 | non Linux clients were misinterpreted. The description of the problem | |
75 | (incompatible numbering in Linux mtio opcodes) is documented at | |
76 | ftp://ftp.fokus.gmd.de/pub/unix/star/README.mtio . Thanks to | |
77 |