From: Kern S. <ke...@si...> - 2002-05-08 10:26:15
|
Hello, I had hoped to release Bacula 1.19 at the beginning of this week, but it is turning out to be a much more major release than I had thought. This is primarily due to the Catalog database changes that are necessary to properly implement automatic removal of database records (prunning) and automatic recycling of Volume (tapes). It is mostly all implemented, but I need more time to test all these changes before "springing" them on you. One of the consequences of the changes is that the database format has changed. If any of you really want to keep your Catalog database, please inform me now so I can document the procedures to do so, which are fairly complicated. Otherwise, I am going to assume that everyone is willing to delete any prior Catalog database and start fresh. Note, SQLite users have no choice but starting over as it does not support the SQL ALTER command. If all goes as planned, I should have the new code acceptably tested and stabilized by the beginning of next week. Best regards, Kern |
From: Kern S. <ke...@si...> - 2006-05-03 10:30:46
|
Hello, The 1.38.x stream: The currently released Bacula version 1.38.8 seems to be quite stable with no major "show stopper" bugs reported, so I have not been planning to make an additional release until version 1.40.0 (see below). However, if you have been following the list, you know that the license released with the Win32 version of Bacula is totally incorrect. As a consequence, I have now prepared version 1.38.9 for release, mainly to correct the license problem. It does, however, have a number of bug fixes. I'll send a separate email on that with the details in a couple of days when it is released. All the code is in the CVS with the tag Release-1_38_9, and at this point, I don't expect anything to change between now and the release. The development stream (1.39.x): Work is progressing at a very good rate on version 1.39. There have been quite a number of submissions, with some important new features, and corrections of some major problems. A few are: handling more than 260 character file/path names in Win32; efficiently handling large numbers of hard links; *finally* fixing the reload command (I think); a solution for the daylight savings time change twice a year; data encryption; migration, and many others ... All the above projects are complete with the exception of the Migration project, which is currently still on my original schedule -- first cut working by end of April, completed version by mid June. That said, the Migration project is going a bit slower than I hoped mainly because of the increasing number of contributions by others. I'm not in the least complaining as long term, I expect contributions to make up over 90% of Bacula code development. Also, I have recently fixed (or received fixes) for a large number of bugs, many have been there a long time, but I always give bugs a very high priority. Schedule for next release: I had originally expected to release version 1.40.0 in July, but I hadn't counted on an up coming vacation that I will be taking from 7 May to 31 May. During the first two weeks of this "vacation" I don't expect to be doing any programming as I will be in an intensive Spanish course in Madrid, which leaves no spare time (non-stop Spanish 8am to 10pm). For the 11 days following the course, my wife and I will be staying in Madrid doing the normal tourist thing with occasional day trips to nearby towns. This means that the release of 1.40.0 will be pushed at least one month later than I had planned -- into August, or perhaps September. -- Best regards, Kern ("> /\ V_V |
From: Kern S. <ke...@si...> - 2007-02-04 09:29:41
|
Hello, Sorry, this is much longer than I had planned. If you have large FileSets, please read at least the last 3 or 4 paragraphs. I would like to say that I am relatively happy with release 2.0.x. As with every major release, there are always "teething" problems in the first few versions, but my feeling is that this release has had fewer and far less serious bugs than previous versions. In case you are not aware, version 2.0.2 is the most recent release. I now have a few more bug fixes in the CVS, but I don't consider them serious enough to make an additional release just for them. As you probably know, my two personal topics for the next release are: 1. Bacula GUI, now going by the user preferred name "bat". 2. Performance improvements. 1. GUI bat is progressing nicely, but a bit slower than I expected due to item #2 (see below). It now communicates with the Director, and the GUI interface is all defined using designer (GUI layout program) forms. Though my implementation is not very elegant, I've also managed to implement the console and a dummy restore "page" with designer in separate subdirectories. The restore page does nothing, but it does put up an interface that Eric sent me, which is the same as the brestore GUI. Having the pages implemented with designer and in separate subdirectories will vastly simplify adding new pages (i.e. functionality) and allowing multiple developers to work at the same time. I'm currently adding code to obtain the default values from Bacula (jobs, pools, storage, ...) so that it can display dialogs similar to the gnome console, where the dialog "knows" which jobs can be selected, ... 2. Performance I have planed on implementing the following things: - Immediate disconnect of the FD from the SD after sending all files to the SD. This will permit Laptops to send the data, then disconnect, even if there is spooling or attribute insertion to be done. This is now implemented in the CVS. - Database performance improvements in several different areas, the most important being faster insertion of attributes. Eric and Marc are working on this, and have submitted a working patch that is not yet integrated, but that gives significant speed improvements especially for PostgreSQL Another area is faster pruning, for which I have a patch, but it is not yet tested. - Transmitting attributes to the Director in a separate thread while spooling/despooling the data. This remains to be started. - Improving the performance of building the in-memory restore tree. You probably don't know that in 2005 (yea two years ago), I wrote a red-black binary tree class for Bacula with the intention of using it for the in-memory restore tree file lists. I completed the code, but never integrated it into the tree routines (if I remember correctly, this was because the tree traversal routines were hand crafted linked lists) Since then, I have converted the tree lists to be Bacula dlist classes, (doubly linked list) with a "fake" binary sort, which improved performance significantly. The red-back binary trees remained unused awaiting integration. An amazing thing recently happened. Rudolf Cejka, being hit by directories with lots of files, implemented AA binary tree routines that he calls tlist to replace the Bacula dlist routines in the restore code. It turns out that AA trees are a simplified form of red-black trees that give similar performance, but not quite as consistent as red-black trees (AA trees remain better balanced than rb trees, but that costs a bit more but speeds up searches). Rudolf needed to make only trivial changes to something like 5 lines of code to integrate his tlist routines. I would like to integrate his tlist code since AA tree handling is much simpler than RB trees. However, while we are working out the licensing issues, I corrected one bug that Rudolf found in my RB tree routines, and one other minor design change and integrated them in the CVS HEAD. Last night I did some performance testing with the new RB binary tree code in restore. I was hoping for a 10 times improvement. My test was rather stupid -- I created a directory containing two subdirectories, one has 419,549 files (with simple names like a.0 - a.9999, ab.xx ...) and the second directory has the same number of files with the same names. This is not really representative of what one would have on most systems (though it may simulate certain mailbox directories). So the two subdirectories have approx 840,000 files. I then backed up the directory containing the two subdirectories (SQLite2 DB) with a full save and did a restore, but stopped the process once all data was loaded into the in-memory tree. I.e. restore 5 (current) 1 (select client) quit (quit after in-memory tree is built) Now the amazing part: For Bacula 2.0.2, which uses the dlist routines, it took 58 minutes to load the in-memory tree (including the time for SQLite to lookup the records). For Bacula 2.1.2, which used my rblist routines, it took 10.05 seconds to load the in-memory tree. A speed up 513 times. I certainly expected an improvement, but not that much. At this point, I would appreciate it if some of you could pull down the CVS code (if you have problems with that let me know, and I will post a .tar.gz file to my web site) and test it with some large number of files to restore using real data. Several of you have FileSets of over 1,000,000 files, and I will be very interested to see what this code produces. I look forward to your feedback. If the code proves stable (it passes all my file based regression scripts), I will probably release it in 2.0.3 or 2.0.4. Many thanks to Rudolf for showing me how simple it was to integrate the RB tree code. Best regards, Kern |
From: Kern S. <ke...@si...> - 2007-04-25 16:13:23
|
Hello, The feedback and response to my request for help in officially "supporting" FreeBSD, Solaris, and Win32 has been 99% positive. We have now found regression testers for FreeBSD and Solaris, and have an offer of equipment for Solaris, which will help a lot, though there are still details ($) of transport to work out, which is normal. I appreciate this kind of positive "lets get the job done" attitude. We still need to find developers that want to resolve bugs for those systems, but since both FreeBSD and Solaris are normally bug free, this shouldn't be too hard, and I can fill in in the mean time. Win32 support is still an open question. I have now posted an updated chapter in the Developer's Guide on the web site that explains how to setup regression testing. Doing so does not really require any developer skills and some of you who are running production systems, might want to run the regression scripts yourself before each update if you build Bacula in house. The Regression chapter is far from complete, but it is a good start, and I will be happy to accept feedback on it. === Version 2.1.8 (current development) is now quite stable, and within the next week, I will be releasing a beta version for testing by early adopters. This code has a good number of *very* important new peformance features, and so I am most likely going to release it quite soon, despite the fact that it doesn't have a lot of the "little" features that I would like to see added. The major features are: - First cut of bat (Bacula Administration Tool) - Red/Black restore in memory tree (500 times faster loading). - Much faster insertion of attributes (somewhere around 10 times). - The Regex Where code to allow easier relocation of restored files. - Socket level heartbeat (untested). - posix_fadvise() use in the FD to improve performance. - Simpler locking in the SD in the reservation system. - Much improved Volume reservation code that should eliminate most conflicts experienced in multiple drive autochangers. - Detection of file size/date change during backup if enabled. - New Recycle Pool feature. - Efficient implementation of very large include/exclude lists. Best regards, Kern |
From: Kern S. <ke...@si...> - 2007-06-04 12:46:57
|
Hello, I've been more or less "gone" for the last two to three weeks doing intensive debugging and algorithm enhancing in Bacula, so have not been active on the email lists. For the most part, the heavy debugging is now complete. Here is a brief summary of how version 2.1.10 has progressed to where it is today. - Fought two kernel bugs, one that rendered gdb useless. - Had two UPS batteries go dead. - Knocked several old bugs in the PostgreSQL driver that clobbered memory, and caused seg faults. Several of these bugs appeared in only one in 20 executions of a particular regression script -- hard to debug. - Added several new algorithms to the multi-drive autochanger algorithm. Hopefully, most if not all of the past problems will now be behind us. - Implement new reservations system debugging code that permits much easier detection of conflicts. - Fought a lot with PostgreSQL (I won't go into the details here ...). - Figured out how to speed up SQLite3 by 30 times (increases probability of database corruption on sudden power failures). - Implemented new smartalloc double buffer free detection (trapped a PostgreSQL driver bug). - A bunch of bug fixes (mostly old bugs). - In the foray, it appears that code that I previously added to switch drives during restore now works, which means that Bacula can now restore data written to multiple devices (different MediaTypes). This needs testing and confirmation. - If the above code works well, it will mean that shortly, we can eliminate the need for Bacula to move tapes from one autochanger drive to another during backups ... :-) While I was "gone", Dirk was also "gone" on vacation. At least that is what he said -- however, during his vacation, he has added an impressive number of new features to bat :-) I recommend that anyone who is using version 2.1.10 test version 2.1.12, which is now in the SVN. Although it has undergone very extensive testing, a bit more is necessary to ensure that recent enhancements to the ./configure process have not broken something on Solaris or FreeBSD. Unless something really unexpected turns up, I will be releasing 2.1.12 for BETA testing later this week. Best regards, Kern |
From: Dirk B. <dba...@sc...> - 2007-06-04 16:11:14
|
On Mon, 2007-06-04 at 14:46 +0200, Kern Sibbald wrote: > Hello, > > While I was "gone", Dirk was also "gone" on vacation. At least that is what > he said -- however, during his vacation, he has added an impressive number of > new features to bat :-) It was a vacation where I had lots of time to work on the project, but only dialup! for short time periods to update/commit and check mail. Got a bunch done. I think I have it so that a user can run "almost" all console commands graphically from context. Just want to complete what we previously discussed with "update volumes from pool". I'll get more complete information to you on that soon. Looking at what to do next there was the bRestore interface and the ability to graph in a fashion similar to the web based interfaces. I did not want to tackle graphing while not connected to the internet. I also was not familiar with how bRestore worked from in interface perspective. So I decided to work on something that would allow users to view the versions available for files. This is now commited. I wrote it intendeding for it to become an alternate way to restore. Right now it only works as a browser. Dirk |
From: Kern S. <ke...@si...> - 2007-06-04 18:57:23
|
On Monday 04 June 2007 17:37, Dirk Bartley wrote: > On Mon, 2007-06-04 at 14:46 +0200, Kern Sibbald wrote: > > Hello, > > > > > While I was "gone", Dirk was also "gone" on vacation. At least that is what > > he said -- however, during his vacation, he has added an impressive number of > > new features to bat :-) > > It was a vacation where I had lots of time to work on the project, Nice. > but only dialup! for short time periods to update/commit and check mail. Painful -- I have the same problem when I travel, in addition over here in Europe, it is *very* expensive. > > Got a bunch done. I think I have it so that a user can run "almost" all > console commands graphically from context. Nice. > Just want to complete what > we previously discussed with "update volumes from pool". I'll get more > complete information to you on that soon. Yes, hopefully I will have a bit more time to finish what I was doing on bat. > > Looking at what to do next there was the bRestore interface and the > ability to graph in a fashion similar to the web based interfaces. I > did not want to tackle graphing while not connected to the internet. I > also was not familiar with how bRestore worked from in interface > perspective. I suspect that bRestore is a rather large project ... > > So I decided to work on something that would allow users to view the > versions available for files. Cool, great idea. > This is now commited. I saw the icon and got the window up, but couldn't get anything to appear in it. Is there some "trick" I need to know? > I wrote it > intendeding for it to become an alternate way to restore. I think a lot of people would love that. > Right now it only works as a browser. > > Dirk > Thanks for taking a vacation :-) Kern |
From: Kern S. <ke...@si...> - 2008-03-19 11:10:53
|
Hello, We would like to bring you up to date on a number of subjects: 1. Testimonials 2. Regression dashboard 3. Bugs and version 2.2.x 4. Development and the next version (probably 3.0.0) 5. Misc 1. Testimonials: As you can imagine having testimonials is an important aspect for spreading the use of Bacula. This is particularly the case now that Bacula is penetrating the enterprise market -- they want to see that it is used by other big companies. Recently Eric Bollengier (many thanks) enhanced the Testimonials page on our website to permit you to enter data about your organization for automatic publication on our web site. We encourage you to help the project the project by adding your testimonial. You can do so with the link at: www.bacula.org -> Testimonials, then click on the "Add your testimonial" link, and you will be presented with a page to fill out. You must fill in enough data so that we can identify you, but you will have the option of what is published. When you do send off your info for publishing, we will review it prior to putting it on the site. Since it is in all Bacula user's interest to have a good set of testimonials to encourage new users, please take the time to send us yours :-) 2. Regression dashboard: With Dan Languille's insistence and Frank Sweetser's coding effort, we now have a Bacula Regression dashboard, which is a sort of summary of all the regression tests run every day. You can see the dashboard by going to the following link: http://regress.bacula.org:8081/Bacula/Dashboard/ where you will see the tests run during the current day. To see the results for previous days, click on the little << symbol just next to the Nightly title. The Nightly tests are tests run by "beta" testers generally on a regular daily basis. For the moment we have no Continuous tests (kicked off after an SVN commit), nor do we have any Weekly tests. The Experimental test area is generally used by developers prior to doing a commit. By clicking on various places on the screen, you can drill down and often see the exact reason for a warning or a test failure. For the moment, these tests apply only to the next Bacula version (2.3.12 and later). It has not been back ported to the 2.2.x release. At some point, we will probably have regular testing of production releases. Submitting tests is open to everyone, so if you have hardware that is not being used, particularly platforms that we are not testing, or hardware with a tape drive, we would be happy to help you set up a test environment (rather trivial). To start, read the Regress chapter of the Developer's manual, then checkout the "regress" part of the Bacula SVN and read the README.ctest file for more details. I would particularly like to see some Solaris testing. 3. Bugs and version 2.2.x There are a number of bugs open on version 2.2.8, and I have been working on them (sharing time with development). Despite a lot of work, I still have not found a definitive solution to the SD race condition bug #1053, simply because I am not able to reproduce it here. However, most the other bugs have resolutions. Due to the fact that bug #1038 (Memory leak in Win32 FD) is relatively serious (currently resolved), we will be releasing a bug release update 2.2.9 in the next week or two. 4. Development and the next version (probably 3.0.0) Development on the next Bacula version is progressing nicely. Unless something unexpected comes up, we are planning the following major features: - Accurate restoration of renamed/deleted files (project #1) - Implement Catalog directive for Pool resource in Director (project #4) - Imply Copy jobs (partial implementation of project #8). - Better control over Job execution (project #18) - Operate on all pools with update command (project #20) - Add Plug-ins to the FileSet Include statements (project #12) - Restructuring the manual into a number of smaller manuals. - Continue to improve Bat - Continue to improve bweb All the above projects are in an advanced state. If we didn't also have bugs to worry about, we could probably add a few more projects, but that is unlikely at this point. We hope to have all the work complete, stabilized and tested for release in June. However, keep in mind that we don't get paid for doing this so, it will be released when it is ready and solid rather than by a fixed schedule :-) 5. Misc I would like to thank UKFast.net for hosting our web site. Having the full control that they have given us over our machine allowed Eric to implement his Testimonial page, and we have found their up time and service excellent. It is particularly comforting to know that they are backing up our server as part of their service using Bacula :-) Best regards, Kern |
From: Kern S. <ke...@si...> - 2008-10-02 12:33:45
|
Hello, I would like to give you a status of where the Bacula project is as I see it and where we are going. Current release: The current production release is 2.4.2, and it seems quite stable. There are a few patches against it, so we will be releasing a bug fix 2.4.3 update shortly that has all those patches integrated. Development version: Our development version 2.5.x (to be released as 3.0.0) is progressing quite nicely. We are documenting the features that we have added, testing them, and in a few cases, completing the implementation. The feature set is probably the most important of any release to date, and if you are interested, please take a look at our preliminary documentation at: http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html If all goes as planned, we will release a beta version of 2.5.x in the next week or so, and the final release will be made around the end of the year. 2.5.x is proving quite stable, but some of the new features as expected need a bit more fine tuning. Fortunately, we already have a few beta testers (including myself) who are using the new features (Accurate backup, Copy, plugins, ...) and are reporting back to us. Good news: As most of you know, I have been the only full time developer working on Bacula since the beginning. However, we now have a second person, Eric Bollengier, who since the beginning of October is dedicated to the Bacula project. I am really pleased with this, and you probably already know that Eric has already made very significant contributions of code in the past, starting in early 2003 and has implemented a substantial number of the new features in version 2.5.x. Welcome aboard Eric! :-) More good news: You have probably read some of my previous emails about creating a professional services company to be able to satisfy the needs of enterprises and thus accellerate the acceptance of Bacula in the commercial world. It has taken an enormous effort, and as I mentioned, it has temporarily diverted about 50% of my energies from the Bacula project for the last six months, but I believe the final benefits will far outweight the temporary costs. For example, having Eric dedicated to the Bacula project was made possible by the existence of this new company. Creating the company has been two years in the making, and now this professional services company is now a reality, and I will be officially announcing it next week, and I think you will be pleased how we have structured it. Best regards, Kern |
From: Hemant S. <hj...@ya...> - 2008-10-02 15:39:35
|
Kern, When you add these features to the on-line documentation, it would be nice if there was a tag (maybe in the left margin) that provided the version of bacula that supported that option. From reading this userlist I have noticed that many users install whatever is available in the software repository, which are old versions, and there are few users who stay one version behind for stability. When they read the documentation it is not clear whether a given option is supported in their version of bacula. Thanks. Hemant Shah E-mail: hj...@ya... --- On Thu, 10/2/08, Kern Sibbald <ke...@si...> wrote: > From: Kern Sibbald <ke...@si...> > Subject: [Bacula-users] Bacula Status > To: "bacula-users" <bac...@li...> > Cc: "bacula-devel" <bac...@li...>, bac...@li... > Date: Thursday, October 2, 2008, 6:49 AM > Hello, > > I would like to give you a status of where the Bacula > project is as I see it > and where we are going. > > Current release: > > The current production release is 2.4.2, and it seems quite > stable. There are > a few patches against it, so we will be releasing a bug fix > 2.4.3 update > shortly that has all those patches integrated. > > > Development version: > > Our development version 2.5.x (to be released as 3.0.0) is > progressing quite > nicely. We are documenting the features that we have > added, testing them, > and in a few cases, completing the implementation. The > feature set is > probably the most important of any release to date, and if > you are > interested, please take a look at our preliminary > documentation at: > > http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html > > If all goes as planned, we will release a beta version of > 2.5.x in the next > week or so, and the final release will be made around the > end of the year. > 2.5.x is proving quite stable, but some of the new features > as expected need > a bit more fine tuning. Fortunately, we already have a few > beta testers > (including myself) who are using the new features (Accurate > backup, Copy, > plugins, ...) and are reporting back to us. > > Good news: > > As most of you know, I have been the only full time > developer working on > Bacula since the beginning. However, we now have a second > person, Eric > Bollengier, who since the beginning of October is > dedicated to the Bacula > project. I am really pleased with this, and you probably > already know that > Eric has already made very significant contributions of > code in the past, > starting in early 2003 and has implemented a substantial > number of the new > features in version 2.5.x. > Welcome aboard Eric! :-) > > More good news: > > You have probably read some of my previous emails about > creating a > professional services company to be able to satisfy the > needs of enterprises > and thus accellerate the acceptance of Bacula in the > commercial world. It > has taken an enormous effort, and as I mentioned, it has > temporarily diverted > about 50% of my energies from the Bacula project for the > last six months, but > I believe the final benefits will far outweight the > temporary costs. For > example, having Eric dedicated to the Bacula project was > made possible by the > existence of this new company. Creating the company has > been two years in > the making, and now this professional services company is > now a reality, and > I will be officially announcing it next week, and I think > you will be pleased > how we have structured it. > > Best regards, > > Kern > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move > Developer's challenge > Build the coolest Linux based applications with Moblin SDK > & win great prizes > Grand prize is a trip for two to an Open Source event > anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Bacula-users mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-users |
From: Dan L. <da...@la...> - 2008-10-02 16:50:48
|
On Oct 2, 2008, at 11:39 AM, Hemant Shah wrote: > Kern, > > When you add these features to the on-line documentation, it would > be nice if there was a tag (maybe in the left margin) that provided > the version of bacula that supported that option. The online documentation is available in two forms: The dev version The released version > From reading this userlist I have noticed that many users install > whatever is available in the software repository, which are old > versions, and there are few users who stay one version behind for > stability. When they read the documentation it is not clear whether > a given option is supported in their version of bacula. I disagree with your conclusion regarding who is running what. I think most people use whatever is released, not what is in the repository. What you are seeing on the list are people who are very active with Bacula. There are far many more users than are on this list, let alone are posting to the lst. The documentation for previous releases is available at installation time (or should be; packages that do otherwise are defective IMNSHO) . In addition. documentation can be downloaded from the website at any time. I would like to have all released documentation online in HTML format. We lack resources (people) to do that. Join the documentation mailing list if you are interested. -- Dan Langille http://langille.org/ |
From: Hemant S. <hj...@ya...> - 2008-10-02 17:15:33
|
--- On Thu, 10/2/08, Dan Langille <da...@la...> wrote: > From: Dan Langille <da...@la...> > Subject: Re: [Bacula-devel] [Bacula-users] Bacula Status > To: hj...@ya... > Cc: "bacula-users" <bac...@li...>, "Kern Sibbald" <ke...@si...>, "bacula-devel" <bac...@li...>, bac...@li... > Date: Thursday, October 2, 2008, 11:50 AM > On Oct 2, 2008, at 11:39 AM, Hemant Shah wrote: > > > Kern, > > > > When you add these features to the on-line > documentation, it would > > be nice if there was a tag (maybe in the left margin) > that provided > > the version of bacula that supported that option. > > The online documentation is available in two forms: > > The dev version > The released version > > > > From reading this userlist I have noticed that many > users install > > whatever is available in the software repository, > which are old > > versions, and there are few users who stay one version > behind for > > stability. When they read the documentation it is not > clear whether > > a given option is supported in their version of > bacula. > > > I disagree with your conclusion regarding who is running > what. I > think most people use whatever is released, not what is in > the > repository. > > What you are seeing on the list are people who are very > active with > Bacula. There are far many more users than are on this > list, let > alone are posting to the lst. > > The documentation for previous releases is available at > installation > time (or should be; packages that do otherwise are > defective > IMNSHO) . In addition. documentation can be downloaded > from the > website at any time. Yes, it can be downloaded anytime, but I am suggesting that a version number tag could be added to the documentation while the new features are added to the documentation, so it does not take lots of additional effort. > > I would like to have all released documentation online in > HTML > format. We lack resources (people) to do that. Join the > documentation mailing list if you are interested. > > -- > Dan Langille > http://langille.org/ Hemant Shah E-mail: hj...@ya... |
From: Dan L. <da...@la...> - 2008-10-02 17:33:40
|
On Oct 2, 2008, at 1:15 PM, Hemant Shah wrote: > Yes, it can be downloaded anytime, but I am suggesting that a > version number tag could be added to the documentation while the new > features are added to the documentation, so it does not take lots of > additional effort. It is a good idea. I know it has been done sometimes. The documentation project could always use additional resources to ensure such things are always done. -- Dan Langille http://langille.org/ |
From: Kern S. <ke...@si...> - 2008-10-02 19:43:31
|
On Thursday 02 October 2008 19:15:24 Hemant Shah wrote: > --- On Thu, 10/2/08, Dan Langille <da...@la...> wrote: > > From: Dan Langille <da...@la...> > > Subject: Re: [Bacula-devel] [Bacula-users] Bacula Status > > To: hj...@ya... > > Cc: "bacula-users" <bac...@li...>, "Kern Sibbald" > > <ke...@si...>, "bacula-devel" <bac...@li...>, > > bac...@li... Date: Thursday, October 2, 2008, > > 11:50 AM > > > > On Oct 2, 2008, at 11:39 AM, Hemant Shah wrote: > > > Kern, > > > > > > When you add these features to the on-line > > > > documentation, it would > > > > > be nice if there was a tag (maybe in the left margin) > > > > that provided > > > > > the version of bacula that supported that option. > > > > The online documentation is available in two forms: > > > > The dev version > > The released version > > > > > From reading this userlist I have noticed that many > > > > users install > > > > > whatever is available in the software repository, > > > > which are old > > > > > versions, and there are few users who stay one version > > > > behind for > > > > > stability. When they read the documentation it is not > > > > clear whether > > > > > a given option is supported in their version of > > > > bacula. > > > > > > I disagree with your conclusion regarding who is running > > what. I > > think most people use whatever is released, not what is in > > the > > repository. > > > > What you are seeing on the list are people who are very > > active with > > Bacula. There are far many more users than are on this > > list, let > > alone are posting to the lst. > > > > The documentation for previous releases is available at > > installation > > time (or should be; packages that do otherwise are > > defective > > IMNSHO) . In addition. documentation can be downloaded > > from the > > website at any time. > > Yes, it can be downloaded anytime, but I am suggesting that a version > number tag could be added to the documentation while the new features are > added to the documentation, so it does not take lots of additional effort. If you look at the very first page of the document, there is a version tag as well as the document date. Maybe you want more than that, but at least it is there ... > > > I would like to have all released documentation online in > > HTML > > format. We lack resources (people) to do that. Join the > > documentation mailing list if you are interested. > > > > -- > > Dan Langille > > http://langille.org/ > > Hemant Shah > E-mail: hj...@ya... > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge Build the coolest Linux based applications with Moblin SDK & win > great prizes Grand prize is a trip for two to an Open Source event anywhere > in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Bacula-devel mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-devel |
From: Kern S. <ke...@si...> - 2008-10-02 19:42:19
|
On Thursday 02 October 2008 18:50:36 Dan Langille wrote: > On Oct 2, 2008, at 11:39 AM, Hemant Shah wrote: > > Kern, > > > > When you add these features to the on-line documentation, it would > > be nice if there was a tag (maybe in the left margin) that provided > > the version of bacula that supported that option. > > The online documentation is available in two forms: > > The dev version > The released version > > > From reading this userlist I have noticed that many users install > > whatever is available in the software repository, which are old > > versions, and there are few users who stay one version behind for > > stability. When they read the documentation it is not clear whether > > a given option is supported in their version of bacula. > > I disagree with your conclusion regarding who is running what. I > think most people use whatever is released, not what is in the > repository. > > What you are seeing on the list are people who are very active with > Bacula. There are far many more users than are on this list, let > alone are posting to the lst. > > The documentation for previous releases is available at installation > time (or should be; packages that do otherwise are defective > IMNSHO) . In addition. documentation can be downloaded from the > website at any time. > > I would like to have all released documentation online in HTML > format. Yes, I would too, and it is a planned project. > We lack resources (people) to do that. Join the > documentation mailing list if you are interested. The bottleneck is probably me since several people have offered to help, but with the new professional services effort, I am running at 150% so certain things are *unfortunately* either on hold or *very* slow. Hopefully that is temporary -- already as I mentioned, we now have more programming resouces (Eric) :-) :-) |
From: Kern S. <ke...@si...> - 2008-10-02 19:39:11
|
On Thursday 02 October 2008 17:39:25 Hemant Shah wrote: > Kern, > > When you add these features to the on-line documentation, it would be > nice if there was a tag (maybe in the left margin) that provided the > version of bacula that supported that option. > > From reading this userlist I have noticed that many users install > whatever is available in the software repository, which are old versions, > and there are few users who stay one version behind for stability. When > they read the documentation it is not clear whether a given option is > supported in their version of bacula. Adding a tag in the left margin is too hard to get correct and means a lot of maintenance at least at this point with the limited manpower we have. However, we hope to soon have multiple versions of the manual on the web site so that you can consult the manual that corresponds to your version. Regards, Kern > > Thanks. > > Hemant Shah > E-mail: hj...@ya... > > --- On Thu, 10/2/08, Kern Sibbald <ke...@si...> wrote: > > From: Kern Sibbald <ke...@si...> > > Subject: [Bacula-users] Bacula Status > > To: "bacula-users" <bac...@li...> > > Cc: "bacula-devel" <bac...@li...>, > > bac...@li... Date: Thursday, October 2, 2008, > > 6:49 AM > > Hello, > > > > I would like to give you a status of where the Bacula > > project is as I see it > > and where we are going. > > > > Current release: > > > > The current production release is 2.4.2, and it seems quite > > stable. There are > > a few patches against it, so we will be releasing a bug fix > > 2.4.3 update > > shortly that has all those patches integrated. > > > > > > Development version: > > > > Our development version 2.5.x (to be released as 3.0.0) is > > progressing quite > > nicely. We are documenting the features that we have > > added, testing them, > > and in a few cases, completing the implementation. The > > feature set is > > probably the most important of any release to date, and if > > you are > > interested, please take a look at our preliminary > > documentation at: > > > > http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html > > > > If all goes as planned, we will release a beta version of > > 2.5.x in the next > > week or so, and the final release will be made around the > > end of the year. > > 2.5.x is proving quite stable, but some of the new features > > as expected need > > a bit more fine tuning. Fortunately, we already have a few > > beta testers > > (including myself) who are using the new features (Accurate > > backup, Copy, > > plugins, ...) and are reporting back to us. > > > > Good news: > > > > As most of you know, I have been the only full time > > developer working on > > Bacula since the beginning. However, we now have a second > > person, Eric > > Bollengier, who since the beginning of October is > > dedicated to the Bacula > > project. I am really pleased with this, and you probably > > already know that > > Eric has already made very significant contributions of > > code in the past, > > starting in early 2003 and has implemented a substantial > > number of the new > > features in version 2.5.x. > > Welcome aboard Eric! :-) > > > > More good news: > > > > You have probably read some of my previous emails about > > creating a > > professional services company to be able to satisfy the > > needs of enterprises > > and thus accellerate the acceptance of Bacula in the > > commercial world. It > > has taken an enormous effort, and as I mentioned, it has > > temporarily diverted > > about 50% of my energies from the Bacula project for the > > last six months, but > > I believe the final benefits will far outweight the > > temporary costs. For > > example, having Eric dedicated to the Bacula project was > > made possible by the > > existence of this new company. Creating the company has > > been two years in > > the making, and now this professional services company is > > now a reality, and > > I will be officially announcing it next week, and I think > > you will be pleased > > how we have structured it. > > > > Best regards, > > > > Kern > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move > > Developer's challenge > > Build the coolest Linux based applications with Moblin SDK > > & win great prizes > > Grand prize is a trip for two to an Open Source event > > anywhere in the world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Bacula-users mailing list > > Bac...@li... > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge Build the coolest Linux based applications with Moblin SDK & win > great prizes Grand prize is a trip for two to an Open Source event anywhere > in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Bacula-devel mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-devel |
From: Hemant S. <hj...@ya...> - 2008-10-03 00:46:34
|
--- On Thu, 10/2/08, Kern Sibbald <ke...@si...> wrote: > From: Kern Sibbald <ke...@si...> > Subject: Re: [Bacula-devel] [Bacula-users] Bacula Status > To: bac...@li..., hj...@ya... > Cc: "bacula-users" <bac...@li...>, bac...@li... > Date: Thursday, October 2, 2008, 2:37 PM > On Thursday 02 October 2008 17:39:25 Hemant Shah wrote: > > Kern, > > > > When you add these features to the on-line > documentation, it would be > > nice if there was a tag (maybe in the left margin) > that provided the > > version of bacula that supported that option. > > > > From reading this userlist I have noticed that many > users install > > whatever is available in the software repository, > which are old versions, > > and there are few users who stay one version behind > for stability. When > > they read the documentation it is not clear whether a > given option is > > supported in their version of bacula. > > Adding a tag in the left margin is too hard to get correct > and means a lot of > maintenance at least at this point with the limited > manpower we have. > > However, we hope to soon have multiple versions of the > manual on the web site > so that you can consult the manual that corresponds to your > version. > I am not sure how the manual is generated, maybe adding version in paranthesis after the option would be easy: e.g. IgnoreDir (V3.0.0) This way you only have to maintain one manual and if someone is reading a manual and is using older version, he/she can easily make a decision whether he/she should upgrade to the new version in order to use the new option. > Regards, > > Kern > > > > > Thanks. > > > > Hemant Shah > > E-mail: hj...@ya... > > > > --- On Thu, 10/2/08, Kern Sibbald > <ke...@si...> wrote: > > > From: Kern Sibbald <ke...@si...> > > > Subject: [Bacula-users] Bacula Status > > > To: "bacula-users" > <bac...@li...> > > > Cc: "bacula-devel" > <bac...@li...>, > > > bac...@li... Date: > Thursday, October 2, 2008, > > > 6:49 AM > > > Hello, > > > > > > I would like to give you a status of where the > Bacula > > > project is as I see it > > > and where we are going. > > > > > > Current release: > > > > > > The current production release is 2.4.2, and it > seems quite > > > stable. There are > > > a few patches against it, so we will be releasing > a bug fix > > > 2.4.3 update > > > shortly that has all those patches integrated. > > > > > > > > > Development version: > > > > > > Our development version 2.5.x (to be released as > 3.0.0) is > > > progressing quite > > > nicely. We are documenting the features that we > have > > > added, testing them, > > > and in a few cases, completing the > implementation. The > > > feature set is > > > probably the most important of any release to > date, and if > > > you are > > > interested, please take a look at our preliminary > > > documentation at: > > > > > > > http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html > > > > > > If all goes as planned, we will release a beta > version of > > > 2.5.x in the next > > > week or so, and the final release will be made > around the > > > end of the year. > > > 2.5.x is proving quite stable, but some of the > new features > > > as expected need > > > a bit more fine tuning. Fortunately, we already > have a few > > > beta testers > > > (including myself) who are using the new features > (Accurate > > > backup, Copy, > > > plugins, ...) and are reporting back to us. > > > > > > Good news: > > > > > > As most of you know, I have been the only full > time > > > developer working on > > > Bacula since the beginning. However, we now have > a second > > > person, Eric > > > Bollengier, who since the beginning of October > is > > > dedicated to the Bacula > > > project. I am really pleased with this, and you > probably > > > already know that > > > Eric has already made very significant > contributions of > > > code in the past, > > > starting in early 2003 and has implemented a > substantial > > > number of the new > > > features in version 2.5.x. > > > Welcome aboard Eric! :-) > > > > > > More good news: > > > > > > You have probably read some of my previous emails > about > > > creating a > > > professional services company to be able to > satisfy the > > > needs of enterprises > > > and thus accellerate the acceptance of Bacula in > the > > > commercial world. It > > > has taken an enormous effort, and as I mentioned, > it has > > > temporarily diverted > > > about 50% of my energies from the Bacula project > for the > > > last six months, but > > > I believe the final benefits will far outweight > the > > > temporary costs. For > > > example, having Eric dedicated to the Bacula > project was > > > made possible by the > > > existence of this new company. Creating the > company has > > > been two years in > > > the making, and now this professional services > company is > > > now a reality, and > > > I will be officially announcing it next week, and > I think > > > you will be pleased > > > how we have structured it. > > > > > > Best regards, > > > > > > Kern > > > > > > > ------------------------------------------------------------------------- > > > This SF.Net email is sponsored by the Moblin Your > Move > > > Developer's challenge > > > Build the coolest Linux based applications with > Moblin SDK > > > & win great prizes > > > Grand prize is a trip for two to an Open Source > event > > > anywhere in the world > > > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > > _______________________________________________ > > > Bacula-users mailing list > > > Bac...@li... > > > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move > Developer's > > challenge Build the coolest Linux based applications > with Moblin SDK & win > > great prizes Grand prize is a trip for two to an Open > Source event anywhere > > in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Bacula-devel mailing list > > Bac...@li... > > > https://lists.sourceforge.net/lists/listinfo/bacula-devel Hemant Shah E-mail: hj...@ya... |
From: Kern S. <ke...@si...> - 2008-10-03 06:03:13
|
On Friday 03 October 2008 02:46:25 Hemant Shah wrote: > --- On Thu, 10/2/08, Kern Sibbald <ke...@si...> wrote: > > From: Kern Sibbald <ke...@si...> > > Subject: Re: [Bacula-devel] [Bacula-users] Bacula Status > > To: bac...@li..., hj...@ya... > > Cc: "bacula-users" <bac...@li...>, > > bac...@li... Date: Thursday, October 2, 2008, > > 2:37 PM > > > > On Thursday 02 October 2008 17:39:25 Hemant Shah wrote: > > > Kern, > > > > > > When you add these features to the on-line > > > > documentation, it would be > > > > > nice if there was a tag (maybe in the left margin) > > > > that provided the > > > > > version of bacula that supported that option. > > > > > > From reading this userlist I have noticed that many > > > > users install > > > > > whatever is available in the software repository, > > > > which are old versions, > > > > > and there are few users who stay one version behind > > > > for stability. When > > > > > they read the documentation it is not clear whether a > > > > given option is > > > > > supported in their version of bacula. > > > > Adding a tag in the left margin is too hard to get correct > > and means a lot of > > maintenance at least at this point with the limited > > manpower we have. > > > > However, we hope to soon have multiple versions of the > > manual on the web site > > so that you can consult the manual that corresponds to your > > version. > > I am not sure how the manual is generated, maybe adding version in > paranthesis after the option would be easy: > > e.g. IgnoreDir (V3.0.0) > > This way you only have to maintain one manual and if someone is reading a > manual and is using older version, he/she can easily make a decision > whether he/she should upgrade to the new version in order to use the new > option. I am sorry, but we are not going to do it that way because of the amount of work involved, and the "messiness" it would cause. I am sorry, I just don't have the time to go into a detailed explanation. Each version of the manual is separate, and it is already hard enough to keep that up to date, and mixing them is a mess -- we have already put version numbers in the text, and in my opinion it is not a good idea. The things that we will do: - we have a project to put all versions of the manual up on the web site, so it will be much easier to find your version. - I'll look at putting the version on the top of each page. - We have made a new chapter (much more work) that explicitly lists and describes the new features in the next version. If the final work is not too much (it will not be easy), we will continue this. Kern > > > Regards, > > > > Kern > > > > > Thanks. > > > > > > Hemant Shah > > > E-mail: hj...@ya... > > > > > > --- On Thu, 10/2/08, Kern Sibbald > > > > <ke...@si...> wrote: > > > > From: Kern Sibbald <ke...@si...> > > > > Subject: [Bacula-users] Bacula Status > > > > To: "bacula-users" > > > > <bac...@li...> > > > > > > Cc: "bacula-devel" > > > > <bac...@li...>, > > > > > > bac...@li... Date: > > > > Thursday, October 2, 2008, > > > > > > 6:49 AM > > > > Hello, > > > > > > > > I would like to give you a status of where the > > > > Bacula > > > > > > project is as I see it > > > > and where we are going. > > > > > > > > Current release: > > > > > > > > The current production release is 2.4.2, and it > > > > seems quite > > > > > > stable. There are > > > > a few patches against it, so we will be releasing > > > > a bug fix > > > > > > 2.4.3 update > > > > shortly that has all those patches integrated. > > > > > > > > > > > > Development version: > > > > > > > > Our development version 2.5.x (to be released as > > > > 3.0.0) is > > > > > > progressing quite > > > > nicely. We are documenting the features that we > > > > have > > > > > > added, testing them, > > > > and in a few cases, completing the > > > > implementation. The > > > > > > feature set is > > > > probably the most important of any release to > > > > date, and if > > > > > > you are > > > > interested, please take a look at our preliminary > > > > documentation at: > > > > http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html > > > > > > If all goes as planned, we will release a beta > > > > version of > > > > > > 2.5.x in the next > > > > week or so, and the final release will be made > > > > around the > > > > > > end of the year. > > > > 2.5.x is proving quite stable, but some of the > > > > new features > > > > > > as expected need > > > > a bit more fine tuning. Fortunately, we already > > > > have a few > > > > > > beta testers > > > > (including myself) who are using the new features > > > > (Accurate > > > > > > backup, Copy, > > > > plugins, ...) and are reporting back to us. > > > > > > > > Good news: > > > > > > > > As most of you know, I have been the only full > > > > time > > > > > > developer working on > > > > Bacula since the beginning. However, we now have > > > > a second > > > > > > person, Eric > > > > Bollengier, who since the beginning of October > > > > is > > > > > > dedicated to the Bacula > > > > project. I am really pleased with this, and you > > > > probably > > > > > > already know that > > > > Eric has already made very significant > > > > contributions of > > > > > > code in the past, > > > > starting in early 2003 and has implemented a > > > > substantial > > > > > > number of the new > > > > features in version 2.5.x. > > > > Welcome aboard Eric! :-) > > > > > > > > More good news: > > > > > > > > You have probably read some of my previous emails > > > > about > > > > > > creating a > > > > professional services company to be able to > > > > satisfy the > > > > > > needs of enterprises > > > > and thus accellerate the acceptance of Bacula in > > > > the > > > > > > commercial world. It > > > > has taken an enormous effort, and as I mentioned, > > > > it has > > > > > > temporarily diverted > > > > about 50% of my energies from the Bacula project > > > > for the > > > > > > last six months, but > > > > I believe the final benefits will far outweight > > > > the > > > > > > temporary costs. For > > > > example, having Eric dedicated to the Bacula > > > > project was > > > > > > made possible by the > > > > existence of this new company. Creating the > > > > company has > > > > > > been two years in > > > > the making, and now this professional services > > > > company is > > > > > > now a reality, and > > > > I will be officially announcing it next week, and > > > > I think > > > > > > you will be pleased > > > > how we have structured it. > > > > > > > > Best regards, > > > > > > > > Kern > > > > ------------------------------------------------------------------------- > > > > > > This SF.Net email is sponsored by the Moblin Your > > > > Move > > > > > > Developer's challenge > > > > Build the coolest Linux based applications with > > > > Moblin SDK > > > > > > & win great prizes > > > > Grand prize is a trip for two to an Open Source > > > > event > > > > > > anywhere in the world > > > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > > > > > _______________________________________________ > > > > Bacula-users mailing list > > > > Bac...@li... > > > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > > > ------------------------------------------------------------------------- > > > > > This SF.Net email is sponsored by the Moblin Your Move > > > > Developer's > > > > > challenge Build the coolest Linux based applications > > > > with Moblin SDK & win > > > > > great prizes Grand prize is a trip for two to an Open > > > > Source event anywhere > > > > > in the world > > > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > > > > _______________________________________________ > > > Bacula-devel mailing list > > > Bac...@li... > > > > https://lists.sourceforge.net/lists/listinfo/bacula-devel > > Hemant Shah > E-mail: hj...@ya... |
From: Dan L. <da...@la...> - 2008-10-03 03:16:49
|
On Oct 2, 2008, at 8:46 PM, Hemant Shah wrote: > > I am not sure how the manual is generated, maybe adding version in > paranthesis after the option would be easy: > > e.g. IgnoreDir (V3.0.0) > > This way you only have to maintain one manua In general, we maintain only the manual about to be released. We don't change manuals from previous releases. > l and if someone is reading a manual and is using older version, he/ > she can easily make a decision whether he/she should upgrade to the > new version in order to use the new > option. There are ReleaseNotes with each release. That is what you should be reading. Surely you don't expect someone to scan a 900 page document to find out of there's something for them? We put it all in one place. -- Dan Langille http://langille.org/ |
From: Marc S. <ma...@sc...> - 2008-10-02 19:22:17
|
* Kern Sibbald schrieb am 02.10.08 um 13:49 Uhr: > Hello, Hi Kern, this all sounds great! > > http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html Ignore Dir A note on whether this directive works recursive or not would be fine. (And I personally would find "Exclude Flag File" more intuitive as "Exclude" is the bacula terminology to to ignore files or directories...) -Marc -- 8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134 |
From: Dan L. <da...@la...> - 2008-10-02 21:07:05
|
On Oct 2, 2008, at 3:04 PM, Marc Schiffbauer wrote: > * Kern Sibbald schrieb am 02.10.08 um 13:49 Uhr: >> Hello, > > Hi Kern, > > this all sounds great! > >> >> http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html > > Ignore Dir > > A note on whether this directive works recursive or not > would be fine. Recursive? As in 'ignore this directory' but take all its children? Sorry, that's not an ignore. ;) Point taken though. It reduces the number of questions. But regardless, if people are so inclined, hunting down the text and supplying a patch helps a great deal. For example, in this case: en/concepts/newfeatures.tex And the diff would be: [dan@ducky:~/src/bacula-trunk/docs/manuals] $ svn di en/concepts/ newfeatures.texIndex: en/concepts/newfeatures.tex =================================================================== --- en/concepts/newfeatures.tex (revision 7683) +++ en/concepts/newfeatures.tex (working copy) @@ -296,6 +296,8 @@ /home/user/temp \end{verbatim} +NOTE: any subdirectories will also not be backed up. That is, the directive +is recursive. [dan@ducky:~/src/bacula-trunk/docs/manuals] $ Or something like that. > (And I personally would find "Exclude Flag File" more intuitive as > "Exclude" is the bacula terminology to to ignore files or > directories...) FWIW, you can name the file anything you want. -- Dan Langille http://langille.org/ |
From: Kern S. <ke...@si...> - 2008-10-03 05:55:38
|
On Thursday 02 October 2008 23:52:47 Dagan McGregor wrote: > > -----Original Message----- > > From: Hemant Shah [mailto:hj...@ya...] > > Sent: Friday, 3 October 2008 4:39 AM > > To: bacula-users; Kern Sibbald > > Cc: bacula-devel; bac...@li... > > Subject: Re: [Bacula-users] Bacula Status > > > > Kern, > > > > When you add these features to the on-line documentation, > > it would be nice if there was a tag (maybe in the left > > margin) that provided the version of bacula that supported > > that option. > > This sounds like something you would add to a Wiki page, rather than the > standard HTML documentation distribution. > > I think versioning the complete documentation for each release makes more > sense than having a single monolithic document that has version numbers > spread through it (which makes it appear messy and out-dated). > > Which mailing list is used for the Bacula documentation? I would be happy > to provide spare cycles looking through the documentation. bacula-docs. You must subscribe to email to it. https://lists.sourceforge.net/lists/listinfo/bacula-docs At the moment, the most important documents are the "development" ones. The monolithic old doc is now split into 7 documents (possibly 8 by release). See the bottom of the www.bacula.org -> Documentation page for links. Regards, Kern > > Cheers, > > Dagan McGregor > Landmark Technologies |
From: Marc S. <ma...@sc...> - 2008-10-03 17:19:22
|
* Dan Langille schrieb am 02.10.08 um 23:02 Uhr: Hi Dan, > > On Oct 2, 2008, at 3:04 PM, Marc Schiffbauer wrote: > > >Ignore Dir > > > >A note on whether this directive works recursive or not > >would be fine. > > Recursive? > > As in 'ignore this directory' but take all its children? > > Sorry, that's not an ignore. ;) Full ack, but just to be 100% sure ;) > > Point taken though. It reduces the number of questions. yes, thanks. > > But regardless, if people are so inclined, hunting down the text > and supplying a patch helps a great deal. Yes, I used to do that. Sorry that I did not this time. > > >(And I personally would find "Exclude Flag File" more intuitive as > >"Exclude" is the bacula terminology to to ignore files or > >directories...) > > > FWIW, you can name the file anything you want. I did not mean the value of the directive but the name of the directive itself. Everywhere in the FileSet in Bacula you use the word "Exclude" when dealing with files that will not be backed up. So I suggest to follow this terminology instead of introducing a synonym. I think this will increase usability. So I think Exclude Flag File = .no_backup would be more intuitive about what it does than Ignore Dir = .no_backup Also I think because of using the word 'Dir' many people would expect this to be a directory which will be ignored and will try something like this: Ignore Dir = /tmp will will be nonsense of course ;) -Marc -- 8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134 |
From: Dan L. <da...@la...> - 2008-10-03 19:15:50
|
On Oct 3, 2008, at 1:19 PM, Marc Schiffbauer wrote: > I did not mean the value of the directive but the name of the > directive itself. > > Everywhere in the FileSet in Bacula you use the word "Exclude" when > dealing with files that will not be backed up. So I suggest to > follow this terminology instead of introducing a synonym. > I think this will increase usability. > > So I think > > Exclude Flag File = .no_backup > > would be more intuitive about what it does than > > Ignore Dir = .no_backup > > > Also I think because of using the word 'Dir' many people would expect > this to be a directory which will be ignored and will try something > like this: > > Ignore Dir = /tmp > > will will be nonsense of course ;) I see what you mean. The directive is: Ignore Dir = <filename> So at a minimum, it should be Ignore Dir File = <filename> But having Dir and File together... no. Taking the example at: http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html # List of files to be backed up FileSet { Name = "MyFileSet" Include { Options { signature = MD5 } File = /home IgnoreDir = .excludeme } } Let's add an exclude option: # List of files to be backed up FileSet { Name = "MyFileSet" Include { Options { signature = MD5 } File = /home Exclude Flag File = .no_backup } Exclude { File = /proc File = /tmp File = /.journal File = /.fsck } } } Discussion commences from here. :) -- Dan Langille http://langille.org/ |
From: Marc S. <ma...@sc...> - 2008-10-04 12:51:16
|
* Dan Langille schrieb am 03.10.08 um 21:15 Uhr: > > > I see what you mean. The directive is: Ignore Dir = <filename> > > So at a minimum, it should be Ignore Dir File = <filename> > > But having Dir and File together... no. ACK > > Taking the example at: > http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html > > # List of files to be backed up > FileSet { > Name = "MyFileSet" > Include { > Options { > signature = MD5 > } > File = /home > IgnoreDir = .excludeme > } > } > > Let's add an exclude option: > > # List of files to be backed up > FileSet { > Name = "MyFileSet" > Include { > Options { > signature = MD5 > } > File = /home > Exclude Flag File = .no_backup > } > > Exclude { > File = /proc > File = /tmp > File = /.journal > File = /.fsck > } > } > } > > Discussion commences from here. :) Maybe "Control File" instead of "Flag File" is better? I am not 100% sure which is better, I prefer "Control File" ATM How about placing this directive into the Exclude{} section? Wouldn't that make more sense anyway? Maybe like that: # List of files to be backed up FileSet { Name = "MyFileSet" Include { Options { signature = MD5 } File = /home } Exclude { File = /proc File = /tmp File = /.journal File = /.fsck Control File = .NO_BACKUP } } I do not know how much effort it would take to change it so that this directive could be used just like WildDir or WildFile for example. It could be used for inclusion too then: With this fileset only every directory containing such a control file would be backed up. FileSet { Name = "MyFileSet" Include { Options { Control File = .DO_BACKUP } Options { Exclude = yes RegexFile = ".*" } File = /home } } Or even a combination of the two examples would be feasible: # List of files to be backed up FileSet { Name = "MyFileSet" Include { Options { signature = MD5 Control File = .DO_BACKUP } File = /home } Exclude { File = /proc File = /tmp File = /.journal File = /.fsck Control File = .NO_BACKUP } } Comments? -Marc -- 8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134 |