[Bacula-users] Bacula Status report - 30 August 2022
The topics for this Status Report are: 1. Bacula Release Status 2. Bacula Binaries 3. Windows Binaries 4. macOS Binaries 5. New Services === 1. Bacula Release Status The latest Bacula version 13.0.1 was released to Source Forge and to www.bacula.org. This version includes many enhancements to Baculum (the Web GUI interface to Bacula), new Storage Group support for the Dir and the SD, a Kubernetes plugin, a new Accurate option to update only meta data during an incremental backup job, external LDAP support for Console and many more. Note: The version 13.0.0 has a problem to start the Storage Daemon systemd service. 2. Bacula Binaries Thanks to the build support from Bacula Systems, we now have binaries for a number of popular distributions. If you need additional distributions, please notify us on the bacula-users email list. The release format is with standard packaging using debs rpms, ... that are specific to each system. However, unlike most Linux distributions, we install the Community Binaries into the directory /opt/bacula as recommended in the Bacula manual and as used by the Bacula Enterprise Edition. This Bacula file release standard is not uncommon and vastly simplifies installation, support, backup and recovery of Bacula itself. Basically, most of the release will be installed into /opt/bacula except for the few system files that must be placed in certain locations such as the start/stop scripts and the man text. To register and get access to Bacula pre-built binaries please go to www.bacula.org and on the main menu bar select Downloads -> Bacula Binary Package Download, then fill out the registration. Note, ultimately you will receive a special download link that will give you access to the binaries. Please keep that link for future access to the binary repository for updates and new releases. 3. Windows Binaries They can be found in www.bacula.org -> Downloads -> Windows Binaries 4. macOS Binaries New macOS packages can be found in www.bacula.org -> Downloads -> Deb, RPM and OSx Packages 5. Project Services Update Bacula.org server had a serious hardware issue in June. We have been able to recover most of the data, and we have moved the services to a new location. It is now hosted by Bacula Systems in a secured environment. We are in the process of converting and upgrading our different web services (cgit, mantis, cdash, wiki) to an on-premise gitlab ultimate instance. This will take a bit of time and I will keep you updated. If you have an account in Mantis, you will receive an activation email for the new Gitlab instance. Unfortunately, CDASH and the Wiki are still not available today - we anticipate these will be replaced by Gitlab. Indeed, the wiki has already been ported into GitLab. The archive of the Wiki is available on: https://web.archive.org/web/20220125230419/https://wiki.bacula.org/doku.php Thanks for using Bacula — be happy because there is much more to come! ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Status Report 9 December 2020
Thank you Kern for all your efforts over the years and welcome to the new role Eric. On 2020-12-10 07:32, Kern Sibbald wrote: Hello, I would like to discuss the following subjects: 1. Bacula Release Status 2. Next Major Bacula Version 3. New Bacula Project Manager === 1. Bacula Release Status The latest Bacula version 9.6.7 will be released shortly. This is a bug fix release that fixes a number of bugs especially the MySQL/MariaDB schema problems. It also has a MySQL/MariaDB retry on a write failure. 2. Next Major Bacula Version The next Major Bacula Version (release 11.0.0) will be made within a week or so. Although this release has been extensively tested, at this time until we get feedback from community testers, we consider it a Beta version. Due to increasing divergences of the Bacula Systems Enterprise and the Community versions, Eric Bollengier undertook a rather big project to make a "universal Bacula core code" version that includes both the Enterprise and Community code in a way that we can easily switch between the two versions, as well as much more easily backport new features to and from the Community version. The first version that contains this "universal Bacula code" is version 11.0.0. Some of the new features in this code are: - New catalog format giving improved performance - Automatic TLS PSK encrypted communications - Support for Client behind NAT - Continuous Data Protection (CDP) Plugin - Built-in Client scheduler - Global Director Autoprune directive - Events/Audit features - New Baculum features - Ask to mount/create volume when disk space is low - Simplification of the Windows FileSet with File=/ - Security enhancements for Restricted Consoles The following version to be released around June 2021 will contain: - Kubernetes Plugin - Generic Cloud Plugin So as you see many new things are coming, and they will keep coming because Bacula Systems is creating lots of new code and backporting it. 3. New Bacula Project Manager In January 2021, it will be 21 years that I (Kern) have worked on the Bacula project. Now it is time to leave the work to younger and enthusiastic new people. So effective with Bacula release 11.0.0, Eric Bollengier will replace me as the Bacula Project Manager. Eric has been working on Bacula since 2005 and with Bacula Systems since its creation in 2008. He is currently the most experienced and knowledgeable Bacula architect and programmer. Even though I am giving the project management responsibility to Eric, I will be around for at least a year to help out where and when I can. I must say that I am very proud to have worked with so many Bacula contributors and users, who are very friendly, kind, and knowledgeable. Thank you all for helping by using Bacula or contributing to it. Thanks for using Bacula -- be happy and stay safe. Kern ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula Status Report 9 December 2020
Hello, I would like to discuss the following subjects: 1. Bacula Release Status 2. Next Major Bacula Version 3. New Bacula Project Manager === 1. Bacula Release Status The latest Bacula version 9.6.7 will be released shortly. This is a bug fix release that fixes a number of bugs especially the MySQL/MariaDB schema problems. It also has a MySQL/MariaDB retry on a write failure. 2. Next Major Bacula Version The next Major Bacula Version (release 11.0.0) will be made within a week or so. Although this release has been extensively tested, at this time until we get feedback from community testers, we consider it a Beta version. Due to increasing divergences of the Bacula Systems Enterprise and the Community versions, Eric Bollengier undertook a rather big project to make a "universal Bacula core code" version that includes both the Enterprise and Community code in a way that we can easily switch between the two versions, as well as much more easily backport new features to and from the Community version. The first version that contains this "universal Bacula code" is version 11.0.0. Some of the new features in this code are: - New catalog format giving improved performance - Automatic TLS PSK encrypted communications - Support for Client behind NAT - Continuous Data Protection (CDP) Plugin - Built-in Client scheduler - Global Director Autoprune directive - Events/Audit features - New Baculum features - Ask to mount/create volume when disk space is low - Simplification of the Windows FileSet with File=/ - Security enhancements for Restricted Consoles The following version to be released around June 2021 will contain: - Kubernetes Plugin - Generic Cloud Plugin So as you see many new things are coming, and they will keep coming because Bacula Systems is creating lots of new code and backporting it. 3. New Bacula Project Manager In January 2021, it will be 21 years that I (Kern) have worked on the Bacula project. Now it is time to leave the work to younger and enthusiastic new people. So effective with Bacula release 11.0.0, Eric Bollengier will replace me as the Bacula Project Manager. Eric has been working on Bacula since 2005 and with Bacula Systems since its creation in 2008. He is currently the most experienced and knowledgeable Bacula architect and programmer. Even though I am giving the project management responsibility to Eric, I will be around for at least a year to help out where and when I can. I must say that I am very proud to have worked with so many Bacula contributors and users, who are very friendly, kind, and knowledgeable. Thank you all for helping by using Bacula or contributing to it. Thanks for using Bacula -- be happy and stay safe. Kern ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula Status Report -- 9 June 2018
Hello, It has been a while since the last status report, so it is now time. I would like to discuss the following subjects: 1. Bacula Release Status 2. Bacula Binaries (New) 3. Windows Binaries (more coming) 4. Next Bacula Version === 1. Bacula Release Status As probably know, the latest Bacula version 9.0.8 was released recently to Source Forge and will be released to www.bacula.org shortly. Mostly this release corrects some copyright oversights. However, since version 9.0.0, we have had several minor releases, so most of the minor annoyances, including a few long time bugs are behind us. Just the same there are quite a few additional fixes and many new features coming in the next release (see below). 2. Bacula Binaries We are pleased to announce that Bacula binaries have been built for a few of the most popular platforms. This is thanks to the build support from Bacula Systems. We will start with a small number most popular binaries and over time expand it to include a broader base of OS releases. In this release is the Aligned driver plugin for the Storage daemon, which permits Bacula to write an archive volume that is properly aligned so that it can bee deduplicated by filesystems such as ZFS and NetApp. Please note that the release format is with standard packaging using debs rpms, ... that are specific to each system. However, unlike most Linux distributions, we install the Community Binaries into the directory /opt/bacula as recommended in the Bacula manual and as used by the Bacula Enterprise Edition. This Bacula file release standard is not uncommon and vastly simplifies installation, support, backup and recovery of Bacula itself. Basically, most of the release will be installed into /opt/bacula except for the few system files that must be placed in certain locations such as the start/stop scripts and the man text. One change is that we ask you to register to get access to the binaries. This is very similar to signing up for the email lists. We have always been interested in who is using Bacula, and provided you supply correct information, this registration will help. You will be asked a few simple questions and also be given an opportunity to receive the Bacula Enterprise Newsletter. If you decline the newsletter, you will not be bothered. The advantage of getting the newsletter is you will be informed what is coming in the next Enterprise releases, which means that most of those features will follow into a subsequent community release. To register and get access to Bacula pre-built binaries please go to www.bacula.org and on the main menu bar select Downloads -> Bacula Binary Package Download, then fill out the registration. 3. Windows Binaries Since version 9.0.0, we have re-integrated the Windows File daemon source code, and built Windows Binaries packages. They can be found in www.bacula.org -> Downloads -> Binary Download Center. Version 9.0.8 binaries will be uploaded shortly. 4. Next Bacula Version We have begun working on the next version of Bacula. It may be released as version 9.2.0 or possibly 11.0.0. The major part of this new release consists of backporting more Bacula Enterprise features -- for example, getting the tray-monitor to build correctly as well as many performance improvements. Thanks for using Bacula — be happy. Kern -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula Status Report
Hello, The last Status Report was in February 2016, so this one is a bit overdue. That said, I would like to discuss the following subjects: 1. Bacula Release Status 2. Windows Binaries 3. Next Bacula Version 4. Bacula Forks 5. The Storage, Visualisation, Cloud (SVC) awards 2016 1. Bacula Release Status As probably know, the latest release of Bacula version 7.4.4 was released on 20 September 2016. Since version 7.4.0, we have had several minor releases, which are in general due to new MySQL and C++ software versions that created incompatibilities with Bacula. Hopefully all those are behind us. The MySQL problems were: 1. MySQL no longer accepts 0 for a DATETIME default (despite the act that 0 is a perfectly valid Unix time value). This was fixed by removing the DEFAULT for all DATETIME fields. 2. MySQL no longer releases the _r.so version of the library needed by Bacula since they now include the thread safe feature in the standard library. This was fixed by using more modern tools for detecting libraries. The C++ problems were that the new GCC 6.0 aggressive compiler behavior that elides (deletes) code written by the Bacula developers. There is no benefit to the new GCC aggressive optimization and it breaks a lot of programs including Bacula. This problem showed up on ArchLinux and Fedora 24. 2. Windows Binaries I have now rebuilt the Enterprise Windows binaries to be compatible with Bacula version 7.4.4. They are currently available in the ww.bacula.org "Download Center". If you want them for non-personal usage, please go to the Bacula Systems web site where you will find the binaries at a very reasonable price. As soon as possible we will be releasing Bacula binaries built for the most popular platforms, so I have decided to split the current Download Center page on www.bacula.org into a Source Download page and a Binaries Download page. Please take note of it, because I will move the Windows binaries from the current single download page into the binary download page. 3. Next Bacula Version I had expected to release the next major version of Bacula in October or November, but due to recent massive changes in the Storage Daemon architecture, it will take me until the March-June time frame to get everything properly integrated. This will be the first major step in a large rewrite of the Storage Daemon. The second step will come 6-9 months later (if all goes well). Basically this first major step has converted the Storage Daemon device drivers into a class based architecture, which allows us to easily and more reliably add new drivers, such as deduplication and cloud backup. 4. Bacula Forks Since Bacula is an Open Source project anyone can take the code and add to it or modify it as they like. However if they then redistribute it, they need to abide by the Open Source license. In the case of Bacula this is GPLv3. When someone forks Bacula, it is a sign that they like to code. However, in most cases (not all) forking, in my personal opinion, leads to duplication of effort, which is a pity since it is difficult to create a code base such as Bacula. We encourage people to contribute with patches, bug reports, ideas, and feature requests on our bugs site: http://bugs.bacula.org/ As you probably know there are several known forks of Bacula, but there are also least two others that have forked Bacula without any announcement. One is commercial, and the other seems to be a country sponsored fork. Concerning one of the known forks, in September there was a post from the the main Bareos developer and by far their most experienced developer announcing that he has quit the project. This announcement is not a surprise for me as I have been expecting it at some point, simply because it is very difficult or impossible to be the only senior developer for a project the size of Bacula and hence for this particular fork. This announcement reinforces the Bacula position as the world's most popular and most used Open Source backup software. Unfortunately for Bareos users, (in my personal opinion) it also puts a question mark on the future prospects for the project. A problem of this type is not a possibility for the Bacula project, because there are multiple senior developers and also Bacula Systems is constantly developing new code that is flowing back to the community version. Thus the Bacula project is assured of having a bright future ahead. 5. The SVC Awards 2016 Bacula has been nominated for the SVC awards. The award is based on the number of votes that the nominee receives. Unfortunately they accept only votes from buisnesses. So if you are a business (or other entity) and like Bacula, you might want to vote (hopefully for Bacula). To do so, please see: http://www.svcawards.com/ Note, the voting closes 11 November. Thanks for using Bacula — be happy. Kern --
[Bacula-users] Bacula Status Report -- 4 February 2016
Hello, I would like to discuss the following topics: 1. Bacula Release Status 2. Next Release 3. Vacation 1. Bacula Release Status As probably know, the latest release of Bacula version 7.4.0 was released on 16 January 2016. This will be a quite stable release because it is based on version 7.2.0 (very stable) plus a few Enterprise bug fixes and features, which are well tested. As always the new code has been very well tested on Linux, but there could be a few minor problems on other OS versions such as Solaris. 2. Next Version I expect that the next Bacula community version will be released in October or November, and as usual, it will have a number of backports from the Enterprise version as well as some new features that have been submitted (see bacula-devel list and bug reports) thanks to devoted community developers :-). There are also some new features that I have been working on and others I have planned. This next Bacula version will be more significant than the 7.4.0 release, if only because one of the submissions that was held back in the 7.4.0 release requires a database upgrade. In addition, if all works out as I plan, there will be a number of other nice new features. Finally I hope to finally fix some of the outstanding bug reports that are annoying to users, but have been on hold since it takes a large amount of time to duplicate those particular problems. 3. Vacation You may recall that last year I was away on vacation several months. Because Bacula Systems is doing very well with the means to hire new programmers, that permits me to do two things: 1. Take more vacation time -- this time in Australia, Bali, Micronesia, and Japan. 2. Be able to consistently devote far more time to developing features important for the community version, which I have been doing since December of last year and will continue to do indefinitely. When I have Internet and time, I will monitor the Bacula status and respond in case of a serious problem, while in my absence Eric Bollengier will be ensuring that the bacula.org site continues to function (it has been the target of several DoS attacks since the 7.4.0 release). Thanks for using Bacula -- be happy. Kern -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula Status Report (2 of 2)
Hello, This is the second half of the quarterly Bacula Status report. Unfortunately, certain short term aspects are not very positive for the project, yet the long term outlook is more promising than ever. If you prefer to start with the good news, skip further down to the section 2: 1. Short term not positive news: You have all certainly heard about the Bacula Systems lawsuit against Bareos for theft of proprietary software and unfair competition. In short, the theft of proprietary software is because on two occasions Bareos via a developer who had access to the proprietary Enterprise git repository allegedly stole the proprietary code written by Bacula Systems employees and put it into the Bareos source code. In the first case, it involved about 20 lines of code taken before they created Bareos and before Bacula Systems was aware of Bareos. The second case was some 400 lines of code written by myself only for the Enterprise version that was put into the Bareos source code under the name of a developer who never had legal access to the Bacula Enterprise proprietary source code. This was done *after* the Bareos lawyers had written to Bacula Systems that Bareos had destroyed all the Enterprise code. It was in fact this second theft of code despite Bareos' legal reassurances that directly lead to the lawsuit. The unfair competition suit is based on the allegation that DassIT (closely related to Bareos) as a Bacula Systems partner had sold a Bacula Enterprise contract to a customer, then later Bareos (same directors as DassIT) convinced that customer to switch to Bareos. The defense of Bareos in the lawsuit seems to be centered around several points -- the principle one being that Bacula Systems does not have the right to release a proprietary version. This is claimed principally by Marco van Weiringen who has unilaterally invalidate the Fiduciary License Agreement (FLA) that he signed with the Free Software Foundation Europe (FSFE) as well as one that he later signed with myself. It is my understanding that it is not possible to unilaterally invalidate FLA agreements (that is declare that they are null and void from the beginning), but this is what is claimed. The consequences of invalidating copyright transfer agreements, if successful, would be an enormous, unprecedented setback to all open source projects -- and it is my opinion that few are aware of the consequences should the Bareos challenge succeed. The open source world has much to lose here depending on the outcome of the lawsuit. As a precaution to protect the Bacula project, I have decided to remove all code written by Marco van Wieringen from the Bacula community code base. What does that mean? Well, normally during Christmas vacation, I sequester myself and write a lot of new code for Bacula (community) that is ultimately released around March of the following year. This year because of the above I have not been able to develop new code as in the past -- a real pity, but after 15 years of work on Bacula, any major threat to its continued viability however small gets my full attention. Hopefully in 3 or 4 months this work will be complete, and I can get on with implementing new features. 2. Longer term good news: The good news is that development for the Bacula Enterprise version is not impacted by the above, and many new developments and features have already come and will continue to come. As you probably know, the main reason I created Bacula Systems was to have a viable and reliable means of continuing and even accelerating advanced development for the community version, which is accomplished by Bacula Systems back porting Enterprise code to the community version. This will continue to be the case, and we have planned a number of projects that are sponsored by Bacula Systems. The will probably begin to appear in the community version between March and July of 2015. A few of these new features will be: 1. Free Enterprise Windows binaries with all the latest features for individual community members. 2. Bacula community binaries built and distributed by the project (actually a Bacula Systems employee) for supported platforms via bacula.org -- this will ensure that for the supported platforms, you can always have the latest binaries, which sometimes are not always available in official distributions. Supported platforms will start with those supported by Bacula Systems, then over time grow to include as many platforms as possible. 3. New automatic snapshot management functions for the community version. 4. The Enterprise Aligned Volume plugin (deduplication for zfs, btrfs, NetApp, ... deduping filesystems) available free for the community. 5. A number of other features that are automatically backported, included all the latest Enterprise bug fixes. So though Bacula community development for 2015 is starting a bit slow compared to past years, you should see that there a many really nice features coming. Thank to
[Bacula-users] Bacula Status Report (1 of 2)
Hello, This is the first half of the quarterly Bacula Status report; the second half will follow in a separate email. 1. If you like Bacula and you like helping people, you should be aware that since Bacula Systems is a growing company, there are two Bacula Systems support positions open. One is for the Eastern part of the United States and the second is in Eastern Europe (the hiring manager might also consider applications from Portugal). 2. The third position is in the RD department for doing IT/QA and builds. This position depending on your qualifications and experience could lead to a very nice career in the development of Bacula itself if you have C and C++ experience. For the details on each of these positions, please visit: http://www.baculasystems.com/company/careers 3. Many thanks to Dan Langille for pointing out on the users list that even if you are not technically able to contribute to the project, if you can build Bacula from source and run it, you can help by running nightly regression tests. Please see past posts by Dan on this subject. Running regression tests, helps us, the developers, find problems that are machine or platform related, and there always seem to be a number of them. Finally I hope you all had (and are still having) a very nice Holiday Season and I wish you all the best with peace and prosperity for 2015 and beyond. The second part of this status report will give you some idea where we are with Bacula development and where we are going. For all of you who have recently sent me emails -- many thanks. For those who haven't I would appreciate hearing from you. Best regards, Kern Bacula Project Manager -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula Status Report
Hello, I have posted a Bacula Status report to the www.bacula.org site. It discusses the following items: 1. Bacula Release Status 2. Windows Binaries 3. Bacula Enterprise 4. Vacation 5. Bareos The following is a link to the report. http://blog.bacula.org/bacula-status-report-30-august-2014/ Best regards, Kern -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula Status Report
Hello, The main purpose of this Status Report is to wish you a very good holiday season and a peaceful and prosperous 2014. Thanks for using Bacula, and thanks for sticking with it :-) I have recently been working on updating the web site to have a more modern look thanks to help from a Bacula community member as well as sponsorship of the graphics design part from Bacula Systems. The first beginnings of this can be seen on: http://blog.bacula.org Please note, that this is work in progress so that most of of the blog site is still empty. Over the next few weeks, I will add more blog material. We have scheduled the major part of the work to refresh the web site to be complete by mid-March 2014. I am currently working on the next Bacula version and what it will contain. Hopefully it will be ready and complete for March 2014. As soon as I am sure what features it will contain, I will start announcing them on the blog site -- hopefully by the end of January. Thanks for using Bacula. Best wishes for 2014, Kern -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Status Report
Hi Kern. Thank you for the information and here are some requests for more details :) On 25.11.2013 18:49, Kern Sibbald wrote: 2. The Bareos fork of Bacula: Unfortunately, despite the fact that Bareos hired one of the best German Open Source lawyers , there were a number of serious copyright violations with their code. I guess mixing copyright and open source into one sentence makes several people quite confused, so can you clarify what are the issues? Is it, for instance, that Bareos wants to change license of the source code, but copyright holder does not permit it? So as Bacula contributors and users, you would be within your rights to feel very upset with Bareos, because they never offered you the code they developed. I have understood that all of their code is in Github. Isn't it so? I assure that I will do all in my power to ensure that any worthwhile features that Bareos implements will be implemented in Bacula, and most likely better integrated and more robust, and where possible with even more functionality and growth potential. How would you do it? Would you port the features, possibly making the code better? Or would you just code the features from scratch? I'm sorry, but currently it seems there is some soap opera going on between these 2 projects and it is just sad to watch. I really do hope that it won't affect good ideas being spread between the 2 projects and also in the open etc. 3. Bacula Systems and the FSFE: There are a number of points in the agreement, but probably the most important of all is that Bacula Systems has now put in writing that it is an Open Source company (at its heart), as it has always proclaimed, and will contribute all the Enterprise code it creates to the Bacula Community code base within at most a 5 year period. So all the Bacula Enterprise features and plugins will ultimately be open sourced? Ie. we would see the delta plugin and vSphere plugin as open-source within 5 years counting from the point they were announced? Does it also mean that these features, by worst case scenario, in the open source version will always be 5 years behind the Enterprise version? Do you have any features in mind that you would make open sourced within the shorter time-frame? -- Silver -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Status Report
Hello, On 11/26/2013 11:17 AM, Silver Salonen wrote: Hi Kern. Thank you for the information and here are some requests for more details :) On 25.11.2013 18:49, Kern Sibbald wrote: 2. The Bareos fork of Bacula: Unfortunately, despite the fact that Bareos hired one of the best German Open Source lawyers , there were a number of serious copyright violations with their code. I guess mixing copyright and open source into one sentence makes several people quite confused, so can you clarify what are the issues? All code is licensed one way or another. Virtually all Open Source code also has a copyright (the GPL is a copyright with a license). I would not like to burden this list with copyright/license details, so I will do so in my blog in detail, and besides right now I am on vacation so please excuse me for not giving any more details at the moment. Is it, for instance, that Bareos wants to change license of the source code, but copyright holder does not permit it? Most of the problems were that they incorrectly added their copyrights where they legally could not. I can imagine they would like to change the license, but that is speculation on my part. What is not speculation is that they cannot change the copyright license. So as Bacula contributors and users, you would be within your rights to feel very upset with Bareos, because they never offered you the code they developed. I have understood that all of their code is in Github. Isn't it so? You will need to ask Bareos if all their code is on Github since I don't have access to their company. At least the main source code is there. I assure that I will do all in my power to ensure that any worthwhile features that Bareos implements will be implemented in Bacula, and most likely better integrated and more robust, and where possible with even more functionality and growth potential. How would you do it? Would you port the features, possibly making the code better? Or would you just code the features from scratch? To keep the Bacula FSFE copyright clean, we will probably need to code the features from scratch. However, one must realize that when coding a feature in Bacula, if two people do the same thing, there could be a substantial overlap of the code since one would naturally use a lot of the internal subroutines. I'm sorry, but currently it seems there is some soap opera going on between these 2 projects and it is just sad to watch. I really do hope that it won't affect good ideas being spread between the 2 projects and also in the open etc. What gives you the idea that there is a soap opera going on? And what do you find sad? Hopefully not something that I have done. Certainly, if Bareos has good ideas, we will be very interested in them as I have already stated just above. They will clearly directly take anything from Bacula that they consider useful. 3. Bacula Systems and the FSFE: There are a number of points in the agreement, but probably the most important of all is that Bacula Systems has now put in writing that it is an Open Source company (at its heart), as it has always proclaimed, and will contribute all the Enterprise code it creates to the Bacula Community code base within at most a 5 year period. So all the Bacula Enterprise features and plugins will ultimately be open sourced? Yes. Some such as our Oracle plugin will not be Open Sources since it uses the Oracle API which is proprietary. At the moment, this is the only exception I can think of though. Ie. we would see the delta plugin and vSphere plugin as open-source within 5 years counting from the point they were announced? The answer is yes, but with the nuance that the time period for code developed prior to the agreement starts as of the agreement. Does it also mean that these features, by worst case scenario, in the open source version will always be 5 years behind the Enterprise version? Yes. Do you have any features in mind that you would make open sourced within the shorter time-frame? Yes we will probably make many available well before the 5 year period (I would guess even most features). I have a number of features in mind that we are internally agreed on and others that we are considering. The official announcement on what they are will certainly be made at the Bacula Conference or possibly earlier. Best regards, Kern -- Silver -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351iu=/4140/ostg.clktrk___ Bacula-users mailing list Bacula-users@lists.sourceforge.net
Re: [Bacula-users] Bacula Status Report
Hello, my name is Maik Außendorf, I am a member of the Bareos project and co-founder of the Bareos company. I apologize for not using my original email address but that has been banned from this list withoout any given reason. I attach my original footer below. I just want to comment on 2 points: 1. The Free Software Foundation Europe (FSFE) is the copyright holder of Bacula open source. We've worked together with the FSFE to clear some formal things in the version history and header files. I.E. some copyright information had to be changed. We've changed everything the way the FSFE has asked for. On August 12th 2013 the last mail from the FSFE stated, that they do not see any more problems. Please read our FAQ article for full quotation: https://www.bareos.org/en/faq/items/copyright_bacula_bareos.html In that FAQ you can also find the history about the open source code fragments regarding the bandwidth limitation feature. 2. GIT Our sources are all on GIT Hub since late 2012. Before that the long year Bacula community developer Marco van Wieringen has maintained his own branch mainly with patches by him and other contributors that were rejected by bacula.org. So a private thing but the only way to preserve those contributions. After the decision was made to start an own project based on that branch, it was published, is 100% AGPL and will stay so. I don't want to comment on more, because these are the important things. Everyone can reuse our code in a open source way (fully compliant with AGPL). And everyone can choose whatever open source project he or she likes best. One more thing to add: we've given a fundamental value to the Bacula community, too: the Bareos clients are compatible with Bacula daemons. And there are repositories for almost all Linux distribution ready to use + a rewritten Windows installer for the Windows client - ready to install (graphical or even unattended by command line switches). If you are missing a bacula client for your particular Linux distribution, MacOS or Windows, feel free to test our Bareos client with your Bacula director. With kind regards. -- Mit freundlichen Grüßen -- Maik Außendorf maik.aussend...@bareos.com Bareos GmbH Co. KG Phone: +49221630693-93 http://www.bareos.com Fax: +49221630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz, M. v. Wieringen -Original Message- From: Kern Sibbald k...@sibbald.com To: bacula-users bacula-users@lists.sourceforge.net; bacula-devel bacula-de...@lists.sourceforge.net; bacula-announce bacula-annou...@lists.sourceforge.net Sent: Mon, Nov 25, 2013 5:57 pm Subject: [Bacula-users] Bacula Status Report Hello, I would like to speak to you about the following points: 1. The rumors of the death of Bacula (the Community version) 2. The Bareos fork of Bacula 3. Bacula Systems and the FSFE (Free Software Foundation Europe) 4. The future of Bacula (the Community version) 1. The rumors of the death of Bacula (the Community version): I borrow words from a quote of Mark Twain: The rumors of the death of Bacula are highly exaggerated! I began working on Bacula 14 years ago (in January 2000), and it has been Open Source from the time it was publicly released in April 2002, and it will remain Open Source. I have been and am fully devoted to Open Source, and in particular to Bacula, which is like my “baby”. So to hear rumors that Bacula is dead or that I have withheld commits because they are Enterprise features is shocking and hurtful to me as well as not true. I did inform the Bacula Community several years ago that my personal participation in Bacula would decrease a bit for several years to allow me to focus more on getting Bacula Systems started. In my opinion, that has not been a serious disadvantage for the Bacula project since Bacula Systems over that period has contributed far more code to Bacula than I could have alone over the same period, and as you will see a bit later in this status report, Bacula Systems contributions are absolutely guaranteed to continue in the long run, and even increase. 2. The Bareos fork of Bacula: The Bacula repository has been on “hold” since our last release in early February, because on 27 February 2013, I learned that there was a fork of Bacula made by a former “consultant” of Bacula Systems with a former reseller of Bacula Systems. Unfortunately, despite the fact that Bareos hired one of the best German Open Source lawyers , there were a number of serious copyright violations with their code. Since the Bacula code is copyrighted by the Free Software Foundation Europe
[Bacula-users] Bacula Status Report
Hello, I would like to speak to you about the following points: 1. The rumors of the death of Bacula (the Community version) 2. The Bareos fork of Bacula 3. Bacula Systems and the FSFE (Free Software Foundation Europe) 4. The future of Bacula (the Community version) 1. The rumors of the death of Bacula (the Community version): I borrow words from a quote of Mark Twain: The rumors of the death of Bacula are highly exaggerated! I began working on Bacula 14 years ago (in January 2000), and it has been Open Source from the time it was publicly released in April 2002, and it will remain Open Source. I have been and am fully devoted to Open Source, and in particular to Bacula, which is like my “baby”. So to hear rumors that Bacula is dead or that I have withheld commits because they are Enterprise features is shocking and hurtful to me as well as not true. I did inform the Bacula Community several years ago that my personal participation in Bacula would decrease a bit for several years to allow me to focus more on getting Bacula Systems started. In my opinion, that has not been a serious disadvantage for the Bacula project since Bacula Systems over that period has contributed far more code to Bacula than I could have alone over the same period, and as you will see a bit later in this status report, Bacula Systems contributions are absolutely guaranteed to continue in the long run, and even increase. 2. The Bareos fork of Bacula: The Bacula repository has been on “hold” since our last release in early February, because on 27 February 2013, I learned that there was a fork of Bacula made by a former “consultant” of Bacula Systems with a former reseller of Bacula Systems. Unfortunately, despite the fact that Bareos hired one of the best German Open Source lawyers , there were a number of serious copyright violations with their code. Since the Bacula code is copyrighted by the Free Software Foundation Europe (FSFE), I provided the technical support, and the FSFE worked with Bareos to clean up their copyright violations. That took a significant amount of time (many months), and the Bareos code though significantly improved is still not totally free of copyright infringements. I won't go into the details here as all of you may not be interested, but will have much more to say about Bareos in later blogs, and when the blog is setup I will let you know. I find Bareos an unusual fork, because it wasn't done in what I believe to be the normal Open Source way. Normally a fork is made when a project is blocked or has serious disagreements with the users. Its also normally done in open communication rather than underhanded or in secret. In the case of Bacula, though some of the development slowed down (I will go into this in detail later), it certainly was by no means stopped. To complain about active development in Bacula Systems, is, in my opinion, incorrect first because adding features to the Enterprise version costs Bacula Systems a lot mostly in salaries yet takes absolutely nothing from Bacula. In fact, when you read the next section, you will see that the more that Bacula Systems develops, the more features that Bacula over time will have. Going back to what I find abnormal about the Bareos fork is that they claim that they spent three years developing a lot of new features, thus they are more feature rich than Bacula. Yes, for the moment, they have a few features that Bacula does not yet have, but not for long, and more importantly over the three years of development of those features they never offered these new features to Bacula nor to any Open Source project. Instead they were developed in secret. I find that a very strange behavior for a self-proclaimed Open Source company (actually, they are “forced” to be Open Source because of the Bacula AGPLv3 license). So as Bacula contributors and users, you would be within your rights to feel very upset with Bareos, because they never offered you the code they developed. I assure that I will do all in my power to ensure that any worthwhile features that Bareos implements will be implemented in Bacula, and most likely better integrated and more robust, and where possible with even more functionality and growth potential. 3. Bacula Systems and the FSFE: If you have been a long time Bacula user you may recall that I discussed the possibility in 2006-2007 of creating a company, now called Bacula Systems, to ensure the continuation of Bacula when I will no longer be able to personally contribute – say in 10 or 20 years, as well as to provide the financial means to add high-end features to Bacula (a fibre channel network costs about $50K to setup). Much to my surprise 95% or more of the responses I got were very positive. Bacula Systems was created in July 2008, and for the first two years, the Enterprise code base and the Community code base were identical. Unfortunately, that didn't work financially for Bacula Systems. Companies willing to
Re: [Bacula-users] Bacula Status report
Hello Kern, On 07/23/2010 05:54 PM, Kern Sibbald wrote: Hello, This is a sort of mini-Bacula status report on the following: 1. Next release 2. New release cycle 3. New bugs tracking database 4. New Bacula server (www.bacula.org) 5. New Bacula source distribution server 1. Next release: Before the end of August, we will be releasing the next version of Bacula -- version 5.0.3 which is a bug fix update to 5.0.2. This release is almost ready and the most recent code is in the SF bacula git repository under Branch-5.0 Thanks for that, and all the good works done, as usually. 2. New release cycle: The little code we currently have for the next major release is in the SF bacula git repository under Branch-5.1. We are considering to moving to a regular 6 month release cycle. The advantage of such a cycle is that it gets features out to you faster. The disadvantage is that it doesn't work so well in small projects like Bacula if there are not sufficient contributions. Such a release would consist of the following points: - A release every 6 months - The deadline is not absolute and could be extended to 9 months if there were insufficient new submissions. - There will be far fewer or no bug fix updates as they are not really needed if we can maintain a 6 month cycle. - Two months before the projected release we will decide if there are sufficient new features to release - The release count down will consist of 3 phases 1. We will add all new approved features The first 4 months after a release this phase will go into effect for the next release - 2. Only very small new features (a few lines) will be added Two months before the final release this phase will go into effect. Note, this phase can be delayed 3 months if insufficient new features are submitted 3. Only bug fixes This phase will go into effect one month before the release Under this scheme, we are currently in Phase 3 for the 5.0.3 release, and the next major release (5.2.0) would be made before mid-January 2011, and is currently under development in Branch-5.1 on Source Forge. I would appreciate comments on this proposed new deadline release cycle. If generally the 6 month schedule is used in FOSS project, I'm seeing more more exhausted users admin to always update. There's sometimes good reasons, sometimes not. following the adage : if it's not breaked, don't change it. I've no idea for Bacula is this would work. Bacula the backup stuff are long time cycles. So if a 6 months release cycle take place, a special attention is needed to permit easy migration/update from the 2 previous release ( 5.0.0 5.0.2 - 5.0.3 for example). Perhaps giving more importance (helping those who want to do that) to the regressing test installation. I also be interested in the cycle release you will have with Bacula-System's enterprise edition ? For example, I've one customers which doesn't want to change anything before a new server come. And it run the 1.38.11 version (1.38 do what it has to do : reliable backup and restore) I don't know how fragmented (in term of version running outside) is the bacula installed base is. And this quick release can raise this. But seeing new feature bug fixes coming out regularly, can also prove to outside how in wellness the project is and make some FOSS marketing about that. My last suggestion, is trying to find a way ( that's not so easy but who knows ) to have a maximum release made one or two month before the launch of big block distribution : giving time to packagers to include them inside their next release 3. New bugs tracking database Sometime in early August (possibly slightly before) we will be moving the current Mantis based bug tracking system to a new RT based system hosted by Bacula Systems. The upside is that the RT system is far more powerful, flexible and adaptible, and most important of all, it allows email responses to bugs. The downside is that it is a bit more complicated (as are most things that have more features) and that it will require everyone to re-register for the new system. In addition, if you don't want to rely on just the community to furnish bug fixes, you will be able to subscribe to a bug fix service that is more professional and has a guaranteed response time (not to be mistaken for a guaranteed fix time). More on this when the service is ready for production. joke What ? We need to recreate the account, this is a real pain :-) /joke 4. New Bacula server The current Bacula Community server is as you probably know generously offered by UKFast. However, the hardware is starting to age, so they have gratiously provided us with a new machine that we will be putting in place in the next few weeks. We don't expect that you will notice any differences, but the hardware running
[Bacula-users] Bacula Status report
Hello, This is a sort of mini-Bacula status report on the following: 1. Next release 2. New release cycle 3. New bugs tracking database 4. New Bacula server (www.bacula.org) 5. New Bacula source distribution server 1. Next release: Before the end of August, we will be releasing the next version of Bacula -- version 5.0.3 which is a bug fix update to 5.0.2. This release is almost ready and the most recent code is in the SF bacula git repository under Branch-5.0 2. New release cycle: The little code we currently have for the next major release is in the SF bacula git repository under Branch-5.1. We are considering to moving to a regular 6 month release cycle. The advantage of such a cycle is that it gets features out to you faster. The disadvantage is that it doesn't work so well in small projects like Bacula if there are not sufficient contributions. Such a release would consist of the following points: - A release every 6 months - The deadline is not absolute and could be extended to 9 months if there were insufficient new submissions. - There will be far fewer or no bug fix updates as they are not really needed if we can maintain a 6 month cycle. - Two months before the projected release we will decide if there are sufficient new features to release - The release count down will consist of 3 phases 1. We will add all new approved features The first 4 months after a release this phase will go into effect for the next release - 2. Only very small new features (a few lines) will be added Two months before the final release this phase will go into effect. Note, this phase can be delayed 3 months if insufficient new features are submitted 3. Only bug fixes This phase will go into effect one month before the release Under this scheme, we are currently in Phase 3 for the 5.0.3 release, and the next major release (5.2.0) would be made before mid-January 2011, and is currently under development in Branch-5.1 on Source Forge. I would appreciate comments on this proposed new deadline release cycle. 3. New bugs tracking database Sometime in early August (possibly slightly before) we will be moving the current Mantis based bug tracking system to a new RT based system hosted by Bacula Systems. The upside is that the RT system is far more powerful, flexible and adaptible, and most important of all, it allows email responses to bugs. The downside is that it is a bit more complicated (as are most things that have more features) and that it will require everyone to re-register for the new system. In addition, if you don't want to rely on just the community to furnish bug fixes, you will be able to subscribe to a bug fix service that is more professional and has a guaranteed response time (not to be mistaken for a guaranteed fix time). More on this when the service is ready for production. 4. New Bacula server The current Bacula Community server is as you probably know generously offered by UKFast. However, the hardware is starting to age, so they have gratiously provided us with a new machine that we will be putting in place in the next few weeks. We don't expect that you will notice any differences, but the hardware running www.bacula.org should be more stable. 5. New Bacula source distribution server You may or may not be aware that we have not always been pleased with the services offered by Source Forge. The uploading is complicated by lines dropping (I have *never* seen this else where), their user interface is horrible, we don't get good statistics, being US based, they block direct access to our code from a number of countries such as Cuba, ... So, probably in September or October we will be moving our Bacula project off of Source Forge to a new server provided by UKFast. There is still a *lot* of work to be done to make this work -- principally getting up a good and suitable interface for users -- more as this develops. As mentioned above, I would appreciate any comments you might have, particularly on the proposed new release cycle. Best regards, Kern -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Status report
Thanks for all the work you do, this sounds great. Sounds a lot like the Fedora Linux release cycle the last time I looked at it. Good luck on moving to the new server and thanks to UKFast. Thomas On Friday 23 July 2010 11:54:03 Kern Sibbald wrote: Hello, This is a sort of mini-Bacula status report on the following: 1. Next release 2. New release cycle 3. New bugs tracking database 4. New Bacula server (www.bacula.org) 5. New Bacula source distribution server 1. Next release: Before the end of August, we will be releasing the next version of Bacula -- version 5.0.3 which is a bug fix update to 5.0.2. This release is almost ready and the most recent code is in the SF bacula git repository under Branch-5.0 2. New release cycle: The little code we currently have for the next major release is in the SF bacula git repository under Branch-5.1. We are considering to moving to a regular 6 month release cycle. The advantage of such a cycle is that it gets features out to you faster. The disadvantage is that it doesn't work so well in small projects like Bacula if there are not sufficient contributions. Such a release would consist of the following points: - A release every 6 months - The deadline is not absolute and could be extended to 9 months if there were insufficient new submissions. - There will be far fewer or no bug fix updates as they are not really needed if we can maintain a 6 month cycle. - Two months before the projected release we will decide if there are sufficient new features to release - The release count down will consist of 3 phases 1. We will add all new approved features The first 4 months after a release this phase will go into effect for the next release - 2. Only very small new features (a few lines) will be added Two months before the final release this phase will go into effect. Note, this phase can be delayed 3 months if insufficient new features are submitted 3. Only bug fixes This phase will go into effect one month before the release Under this scheme, we are currently in Phase 3 for the 5.0.3 release, and the next major release (5.2.0) would be made before mid-January 2011, and is currently under development in Branch-5.1 on Source Forge. I would appreciate comments on this proposed new deadline release cycle. 3. New bugs tracking database Sometime in early August (possibly slightly before) we will be moving the current Mantis based bug tracking system to a new RT based system hosted by Bacula Systems. The upside is that the RT system is far more powerful, flexible and adaptible, and most important of all, it allows email responses to bugs. The downside is that it is a bit more complicated (as are most things that have more features) and that it will require everyone to re-register for the new system. In addition, if you don't want to rely on just the community to furnish bug fixes, you will be able to subscribe to a bug fix service that is more professional and has a guaranteed response time (not to be mistaken for a guaranteed fix time). More on this when the service is ready for production. 4. New Bacula server The current Bacula Community server is as you probably know generously offered by UKFast. However, the hardware is starting to age, so they have gratiously provided us with a new machine that we will be putting in place in the next few weeks. We don't expect that you will notice any differences, but the hardware running www.bacula.org should be more stable. 5. New Bacula source distribution server You may or may not be aware that we have not always been pleased with the services offered by Source Forge. The uploading is complicated by lines dropping (I have *never* seen this else where), their user interface is horrible, we don't get good statistics, being US based, they block direct access to our code from a number of countries such as Cuba, ... So, probably in September or October we will be moving our Bacula project off of Source Forge to a new server provided by UKFast. There is still a *lot* of work to be done to make this work -- principally getting up a good and suitable interface for users -- more as this develops. As mentioned above, I would appreciate any comments you might have, particularly on the proposed new release cycle. Best regards, Kern --- --- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- == Thomas McMillan Grant Bennett
Re: [Bacula-users] Bacula Status report
Kern Sibbald wrote: I would appreciate if beta testers would retest the current SVN. Thanks. Other than weird-files2 (known glitch due to cp deficiency) it passes everything fine on Mac OS 10.4. Also passes everything on my fedora 7 test system. -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula Status report
Hello, As I have mentioned several times, we are nearing the end of stabilizing the next release (I consider the current 2.1.28 beta pretty good). There are still a few bugs open on the current code, but they should be resolved shortly, if they are not already fixed. What remains is a bit more documentation, particularly to write a bit more documentation on bat, and the final ReleaseNotes. I expect that all this will be complete in a week or two. Beginning tomorrow, I will be on a mini-vacation in the nearby mountains of Switzerland for four days, so during that time, my connectivity and responsiveness will fall below the current low levels ... :-) In the next hour or two, I will be releasing a new version of depkgs, which will not have the qwt package (Graphics package used by bat). However, I will also release a depkgs-qt, which will have both the Qt4 package and the qwt. This will permit you to build bat, should you wish, on any system where you do not have one or both of those packages. The documentation is included in the INSTALL document in depkgs-qt. I would appreciate if beta testers would retest the current SVN. Thanks. Best regards, Kern - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula status report
Jeffrey L. Taylor wrote: I like SuSE a lot and have been running it and participating in the betas for severals years. However, 10.1 has been very problematic. I agree. I would wait until they sort out the package manager problem(s). They are getting close. There was a major fix about a week ago. I haven't had time to monitor the reaction. I've installed the latest libzypp update, no improvement. But you can install SMART, it's a good workaround. http://www.tweakhound.com/linux/suse/101/installing_1.htm F. -- Fábio Mengue - Núcleo de Informática - Hospital das Clínicas - Unicamp fabiao at hc dot unicamp dot brfabio at unicamp dot br Larguei a bebida. O ruim é que não lembro onde. - Badá The highest function of ecology is the understanding of consequences. - Pardot Kynes Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula status report
On Wednesday 28 June 2006 21:14, Joshua J. Kugler wrote: On Wednesday 28 June 2006 05:02, Kern Sibbald wrote: Searching for a new distro is not so easy. Kubuntu treats users as idiots by disabling the root account and giving full sudo privilege to the main user. Well, I suppose...but I've found it quite easy to adapt. I suppose you could say it is more Mac-ish, in that you have admin accounts that can do priv'ed operations, but really, it is the way sudo was designed. And you can always do sudo bash :) Trust me, I do that quite often. Ubuntu won't boot on a relatively modern (1.5 years old) machine. Well, in the classic works for me, YMMV tradition, I have to say I've been thrilled with Kubuntu. It's installed on a few-month-old Acer AMD Sempron system on my desktop, and has been rock solid. I think I've only had to kill X once, and never have I had a hard freeze. Running with an nVidia 6600 video card, and a Via chipset motherboard. I'm sorry to hear you've had trouble. What kind of errors does it throw? Or does it even get far enough to throw the errors? I never had any problem loading Kubuntu. I'm just not comfortable with their philosophy of how to setup a Linux machine. Their philosophy is probably quite reasonable for desktop use and for dealing with inexperienced users, but for old-timers like me, I don't have the patience to deal with a different way of using security/root. I did have problems loading Ubuntu. I forget what it was, but basically the ISO images would not load on my machine -- a bad sign. Debian is great on stability and security updates, but has really old software. If you use Debian testing, you get good stability and recent software but currently (they are in the process of changing) no security updates. Agreed...It'll be great when they start doing security updates for testing. Yes, at that point, they may get another person converting his desktop. Though the more I see of SuSE, the more I am impressed. I had thought it would not be suitable for server applications because of the lack of SELinux, which I run on my server. SELinux is, however, *extremely* complex and it is not easy to write rules for it. On the other hand the SuSE AppArmor *appears* to accomplish the same thing in a much simpler way and for the most part using automated tools. I still haven't found a technical paper on how AppArmor really works, so this is an open research subject for me. -- Best regards, Kern ( /\ V_V Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula status report
Quoting Kern Sibbald [EMAIL PROTECTED]: On Wednesday 28 June 2006 21:14, Joshua J. Kugler wrote: [snip] Though the more I see of SuSE, the more I am impressed. I had thought it would not be suitable for server applications because of the lack of SELinux, which I run on my server. [snip] I like SuSE a lot and have been running it and participating in the betas for severals years. However, 10.1 has been very problematic. I would wait until they sort out the package manager problem(s). They are getting close. There was a major fix about a week ago. I haven't had time to monitor the reaction. I concur with the conclusion, I am just advising caution on the timing. HTH, Jeffrey Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula status report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 sudo -s does a shell. Not sure why people keep suggesting 'sudo bash' -- any good reason? _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - User Support Spec. III |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 Joshua J. Kugler wrote: Well, I suppose...but I've found it quite easy to adapt. I suppose you could say it is more Mac-ish, in that you have admin accounts that can do priv'ed operations, but really, it is the way sudo was designed. And you can always do sudo bash :) Trust me, I do that quite often. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (MingW32) iD8DBQFEpCBUmb+gadEcsb4RApJFAJ4mDSl+jgab3j06GPTS0KEEPy8NUQCdERh3 Zqe+kLBLRYW5OQOnSLr+G50= =RdRM -END PGP SIGNATURE- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula status report
On Thursday 29 June 2006 10:47, Ryan Novosielski wrote: Joshua J. Kugler wrote: Well, I suppose...but I've found it quite easy to adapt. I suppose you could say it is more Mac-ish, in that you have admin accounts that can do priv'ed operations, but really, it is the way sudo was designed. And you can always do sudo bash :) Trust me, I do that quite often. sudo -s does a shell. Not sure why people keep suggesting 'sudo bash' -- any good reason? Because I didn't know about sudo -s? :) j -- Joshua Kugler Lead System Admin -- Senior Programmer http://www.eeinternet.com PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE PO Box 80086 -- Fairbanks, AK 99708 -- Ph: 907-456-5581 Fax: 907-456-3111 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula status report
On Wednesday 28 June 2006 05:02, Kern Sibbald wrote: Searching for a new distro is not so easy. Kubuntu treats users as idiots by disabling the root account and giving full sudo privilege to the main user. Well, I suppose...but I've found it quite easy to adapt. I suppose you could say it is more Mac-ish, in that you have admin accounts that can do priv'ed operations, but really, it is the way sudo was designed. And you can always do sudo bash :) Trust me, I do that quite often. Ubuntu won't boot on a relatively modern (1.5 years old) machine. Well, in the classic works for me, YMMV tradition, I have to say I've been thrilled with Kubuntu. It's installed on a few-month-old Acer AMD Sempron system on my desktop, and has been rock solid. I think I've only had to kill X once, and never have I had a hard freeze. Running with an nVidia 6600 video card, and a Via chipset motherboard. I'm sorry to hear you've had trouble. What kind of errors does it throw? Or does it even get far enough to throw the errors? Debian is great on stability and security updates, but has really old software. If you use Debian testing, you get good stability and recent software but currently (they are in the process of changing) no security updates. Agreed...It'll be great when they start doing security updates for testing. j -- Joshua Kugler Lead System Admin -- Senior Programmer http://www.eeinternet.com PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE PO Box 80086 -- Fairbanks, AK 99708 -- Ph: 907-456-5581 Fax: 907-456-3111 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
