From: Kern Sibbald Date: Tue, 23 Oct 2007 09:12:51 +0000 (+0000) Subject: Update X-Git-Tag: Release-3.0.0~2355 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=c57a29d1c4c38dcfbaafef7942546c484a9e30ba;p=bacula%2Fdocs Update --- diff --git a/docs/developers/version.tex b/docs/developers/version.tex index 89963dfc..ec5c037a 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -2.2.4 (14 September 2007) +2.2.5 (09 October 2007) diff --git a/docs/home-page/images/feed-icon-14x14.png b/docs/home-page/images/feed-icon-14x14.png new file mode 100644 index 00000000..b3c949d2 Binary files /dev/null and b/docs/home-page/images/feed-icon-14x14.png differ diff --git a/docs/home-page/images/feed-icon-28x28.png b/docs/home-page/images/feed-icon-28x28.png new file mode 100644 index 00000000..d64c669c Binary files /dev/null and b/docs/home-page/images/feed-icon-28x28.png differ diff --git a/docs/home-page/news.txt b/docs/home-page/news.txt index be1f6742..099a8a50 100644 --- a/docs/home-page/news.txt +++ b/docs/home-page/news.txt @@ -1,3 +1,20 @@ +Kern;;;2007/19/11;;15:25 +Bacula version 2.2.5 source tar files as well as the Win32 +binaries are available in the Bacula release area of Source Forge. + +This release is an important bug fix upgrade to version 2.2.4, +and we recommend that all users upgrade as soon as possible. + +Despite the fact that the Release Notes are rather short, the bug +fixes represent quite a lot of work: + +Version 2.2.5 is a major bug fix release to version 2.2.4 +- It fixes the following bugs: #961, 962, 963, 969, 968, 960, + 964, (possibly 935 and 903), 953, 953, 967, 966, 965, 954, + 957, 908, 958, and 955. +- It also improves listing performance problems in bat pointed + out by Chris Howells. +;;; Kern;;;2007/9/29;;;20:30 I have found and fixed a serious data loss bug in Bacula. diff --git a/docs/home-page/pages/bugs.php b/docs/home-page/pages/bugs.php index 57b6bd00..0e0de729 100644 --- a/docs/home-page/pages/bugs.php +++ b/docs/home-page/pages/bugs.php @@ -20,31 +20,40 @@ http://bugs.bacula.org

-To view the bug reports, you can login as user anonymous -and password anonymous. +To view the bug reports, you can login as user anonymous and +password anonymous. The advantage of actually being subscribed +is that you will be notified by email of any serious bugs and their +resolution. -To submit bug reports, you must create an account. You must also use -a browser running a US ASCII code page or UTF-8. Some users running -Win32 IE with Windows Eastern European code pages have experienced -problems interfacing with the system. +To submit bug reports, you must create an account. You must also use a +browser running a US ASCII code page or UTF-8. Some users running Win32 +IE with Windows Eastern European code pages have experienced problems +interfacing with the system.

Most Bacula problems are questions of support, so if you are not sure if a problem you are having is a bug, see the support page -on this site for links to the email lists. +on this site for links to the email lists. However, once you have +determined that a problem is a bug, you must either submit a bug +report to the bugs database or send an email to the bacula-devel +list, otherwise it is possible that the developers will never know +about your bug and thus it will not get fixed. -You should expect two things to be slightly different in our -Bugs handling than many other Open Source projects. First, we unfortunately -cannot supply support via that bugs database, and second, we close -bugs very quickly to avoid being overwhelmed. Please don't take this -personally. If you want to add a note to the bug report after it -is closed, you can do so without reopening the bug. If after everything -considered, you are convinced there is a bug and you have new information, -you can always reopen the bug report. +You should expect two things to be slightly different in our Bugs +handling than many other Open Source projects. First, we unfortunately +cannot give support or handle feature requests via the bugs database, +and second, we close bugs very quickly to avoid being overwhelmed. +Please don't take this personally. If you want to add a note to the bug +report after it is closed, you can do so by reopening the bug, adding a +bug note, then closing the bug report again, or for really simple +matters, you can send an email to the bacula-devel email list. If a +developer closes a bug report and after everything considered, you are +convinced there really *is* a bug and you have new information, you can +always reopen the bug report.

Information Needed in a Bug Report

For us to respond to a bug report, we normally need the following -as the minimum information, which you can enter into the appropriate +as the minimum information, which you should enter into the appropriate fields of the bug reporting system: -The first two of these items can be fulfilled by sending -us a copy of your config.out file, which is in the -main Bacula source directory after you have done -your ./configure. +The first two of these items can be fulfilled by sending us a copy of +your config.out file, which is in the main Bacula source +directory after you have done your ./configure. +

In addition, we will sometimes need a copy of your Bacula -configuration files (especially bacula-dir.conf). If you -think it is a configuration problem, please don't hesitate -to send them if necessary. +configuration files (especially bacula-dir.conf). If you think it is a +configuration problem, please don't hesitate to send them if +necessary. diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex index 89963dfc..ec5c037a 100644 --- a/docs/manual-de/version.tex +++ b/docs/manual-de/version.tex @@ -1 +1 @@ -2.2.4 (14 September 2007) +2.2.5 (09 October 2007) diff --git a/docs/manual/catmaintenance.tex b/docs/manual/catmaintenance.tex index 2fd11477..eeb36b8b 100644 --- a/docs/manual/catmaintenance.tex +++ b/docs/manual/catmaintenance.tex @@ -622,15 +622,15 @@ database backup, but it will be more work and take longer. \index[general]{Backing Up Your Bacula Database - Security Considerations } \index[general]{Database!Backing Up Your Bacula Database - Security Considerations } -We provide make_catalog_backup as an example of what can be used to backup +We provide make\_catalog\_backup as an example of what can be used to backup your Bacula database. We expect you to take security precautions relevant -to your situation. make_catalog_backup is designed to take a password on +to your situation. make\_catalog\_backup is designed to take a password on the command line. This is fine on machines with only trusted users. It is not acceptable on machines without trusted users. Most database systems provide a alternative method, which does not place the password on the command line. -The make_catalog_backup contains some warnings about how to use it. Please +The make\_catalog\_backup script contains some warnings about how to use it. Please read those tips. To help you get started, we know PostgreSQL has a password file, diff --git a/docs/manual/tips.tex b/docs/manual/tips.tex index d3d81659..18a89aa9 100644 --- a/docs/manual/tips.tex +++ b/docs/manual/tips.tex @@ -602,7 +602,7 @@ setup procedure leaves the database open to anyone. At a minimum, you should assign the user {\bf bacula} a userid and add it to your Director's configuration file in the appropriate Catalog resource. -If you use the make_catalog_backup script provided by Bacula, remember that +If you use the make\_catalog\_backup script provided by Bacula, remember that you should take care when supplying passwords on the command line. Read the \ilink{BackingUpBaculaSecurityConsiderations}{Backing Up Your Bacula Database - Security Considerations } for more information.