Bug#519548: Getting mondo updated
Hello, Rogério Brito said on Tue, Sep 08, 2009 at 10:47:23AM -0300: I'm not a pure expert, but know where I want the code to go. And my will is: remove useless static memory allocation (tricky) I'm not sure about which static memory allocation you mean. Do you mean char foo[BIG_SIZE_HERE]? Yes; It has caused many different issues in the code (strcat without checks leading to seg fault, stupid limitations in sizing, huge allocation of memory where it's not useful, ...) Depending on the situation, just including some malloc's/free's are gratuitous artificial complexity. Well if it's done at a sufficiently low level, it's not a problem IMO. It's relatively fast, you use what you need only, and adapt to machine resources, not to fixed barriers (nobody will ever need more than 640KB syndrom ;-) And, anyway, if said code is not used in a non-standard ways, it is marked auto by the compiler and disposed when the scope of the function ends. THere were some recursive and interesting usage + some statics. I usually favor statically compiled languages, but I'm not opposed to Perl, *if* the programs don't inflate the memory requirements of the interpreter too much. Will have to measure that. But frankly looking at the code since 8 years now, and more precisely during the last 4, most of what was written in C should never have been written in C !! : The code still contains more than 600 system calls ! Or how to use C as a scripting language. There are some parts that could benefit from staying in C, but only a few IMO. We would like to want the code to work even on small platforms, after all. Yes but nowadays it's far from being the majority of users. Now we could target netbooks, phones, ... why not. But that would anyway require a good re-architecture/re-write. And perl is available on so many platform it shouldn't be a problem. And I always found the perf great (never looked too much at the memory side). Sure, but I'd guess that they may not be that interesting, now that the versions have diverged a bit. I'm including it here anyway. Please, note that the patch has already three patches in it (patch in patch format, to be handled with quilt). I don't know quilt myself. IIUC it aggregates patches. Why not, as Andree can say to you, I tend to prefer single (small ;-) patches in order to study them before inclusion. It seems that the lzma file is not clean: lzma: Decoder error Could you resend it again please ? (start is on control file modifications, and I'll apply them without issue). Very nice. I am short on space and like to keep my backups under 500MB, so that I can use dvdisaster (yes, I am a bit paranoid). BTW, by using dvdisaster, one can create solid archives (like I mentioned with you many moons ago). And the backups are smaller themselves. Sorry forgot about that. Indeed looks very interesting. Will package it for my Mandriva which doesn't seem to have it. Would you like to contribute a mondo extension allowing its joint usage ? OK, in a slightly tangent comment, it seems that the version 2.2.7 has problems with Linux images that have not been compressed with gzip (newer kernels allow bzip2 and lzma compressed images). Do you have support for that? Humm. Not at the moment. Right now, mondo dies trying to be smart about the kernel that I compiled if I use one of those images, but it is wrong in its decision. It's in GetInitrdFilesystemToUse and only supports gziped compressed kernel. Can easily be adapted (this code was made by Andree BTW for Debian originaly and was merged ;-) And, BTW, why are there differences regarding burning CDs/CD-RWs? I can't really see the point (besides the fact that CD-RWs may have to be blanked before writing them). I know there are diffs for drive that can eject/inject or not but I also never understood why they were considerd separately indeed. Probably more cleanup to do. I absolutely agree that sane defaults are essential. But letting the experienced user override the defaults is important to have a good share of the target market for this tool. Which is aplea for config file which are right now missing in mondo. It's in my trunk tree (useless BTW except for taking some ideas I tried). No problems with postponing things. But I am much more favorable to gradual changes than to radical changes. +1 ! Over-engineering is a problem that should be avoided. A certain degree of generality is good, but not that much. Vast question ;-) Great. Now that GCC 4.4 has test coverage, we can see which paths are used and which ones are not. I'm interested if you can give example of how we could apply that to mondo. Size is still important (and will always be), but 1MB of a 650MB CD wouldn't make that much difference. It's a bit more today. mindi is around 30MB. It's still less than 10% of a CD and nothing of a DVD/USB key. * cleaning the logs a little bit. You mean the project logs or Debian
Bug#519548: Getting mondo updated
Hello, Andree Leidenfrost said on Mon, Aug 31, 2009 at 07:18:58PM +1000: I am also CC'ing upstream and I suggest the of you communicate directly, especially but not limited to issues that could possibly be addressed upstream - Bruno is planning a new release shortly. Yes. 2.2.9 is in a frozen state now. I just want to fix a last remaining bug seen on a customer site. Then publish. I'm also working in // on 2.2.10 which already contains a large number of modifications. On Wed, 2009-08-26 at 06:05 -0300, Rogério Brito wrote: Anyway, back to the subject of maintaining mondo, yes, I would like to work on it a little bit. I'm still not sure if I can co-maintain it (most probably, I can), but I would like to delve further in the code. Well, I'm also interested to provide to Debian the latest packages as soon as possible. Thanks to Andree's work, I have a whiole build infrastrcuture in place to produce packages for Debian 3.1, 4.0 and 5.0. So Iwas considering the possibility to become a Debian Maintainer (Cf: http://wiki.debian.org/Maintainers) in order to be able to help. WDYT ? That being said, if I decide to co-maintain the package, can I put my name in the uploaders field and add the DMUA: yes (as I am a DM)? In Personaly, I have no issue for that, of course. And feel free to involve me around bugs seen in Debian for Mondo/Mindi. fact, I think that a good thing would be to have mondo/mindi/etc in a public repository (I would suggest that we create one named pkg-mondo in alioth). I'm not sure what you mean here. Mondo/mindi is already in a public repo (http://trac.mondorescue.org/browser/branches/2.2.9). Even my build system is in a public repo (http://trac.project-builder.org/browser/projects/mondorescue/pbconf/branches/2.2.9 e.g. for the upcoming stable version). Do you think of the specific Debian build files ? Knowing that my goal is to reduce as much as possible the differences between upstream and packages. Andree helped me a lot in that perspective, and his contribution has been very valuable for the project, as well as for Debian. What do you think? I would also be willing to spread the word so that we can get some more contributions (and/or users). Yes ! Yes !! Once it's ready, we can at least announce on our ML that we have another DD with Andree working on the packaging. I'll let you do the same on the Debian side. Happy to see continuous interest from Debian to our project ! Greetings, Bruno. -- Linux Profession Lead EMEA / Open Source Ambassador \ EMEA CME Sol. Center http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org pgpiSllAyGAK6.pgp Description: PGP signature
Bug#475221: mondo: CVE-2008-1633
This bug will be fixed by the upcoming debian package for Lenny which is based on 2.2.7 so post 2.2.5 which doesn't contain the issue anymore. Bruno. -- Linux Profession Lead EMEA / Open Source Evangelist \HP CI EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403454: mindi does rm -Rf /home !
Andree Leidenfrost said on Sat, Dec 23, 2006 at 09:47:48AM +1100: I think you don't need to pass time on that Andree. I'll publish soon 2.2.1 which will fix that. You'll just have to update your packages. Unfortunately, a new upstream version in Debian is not currently an option as we are in freeze. I can really only fix RC bugs at the moment. Well upstream is the king. Let me propose you something: I can publish a new 2.2.0-3 which is equal to 2.2.1 if it's more convenient for you. Of course I'm cheating. But I have a problem if Etch only contains 2.2.0 on my side. I'd prefer that we fix the remaining differences in mindi ;-) Maybe this could be something to sort out during LCA2007? That was in my planning for LcA 2007 ;-) Bruno. -- Linux Profession Lead EMEA / Open Source Evangelist \HP CI EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org pgpKTR1rYnSSN.pgp Description: PGP signature
Bug#403454: mindi does rm -Rf /home !
Matija Nalis said on Thu, Dec 21, 2006 at 09:35:08PM +0100: both have been fixed promptly in upstream. Ok I'm happy that they are now indeed fixed. I really like debian users as they give feedback ;-) I might send you a patch to try against mindi-2.20-1. Would you be able to test it? I think you don't need to pass time on that Andree. I'll publish soon 2.2.1 which will fix that. You'll just have to update your packages. I intend to get this fixed over the weekend, i.e. no later than 24 Dec 06. I'd prefer that we fix the remaining differences in mindi ;-) FYI, the server currently runs your mindi 2.20-1 recompiled for sarge with only patches for above two problems, and it works ok. Great ;-) But I'll be visiting LCA2007 in Sydney in mid-January, so direct interrogation is an option :) Yep, I'll be there too ;-)) Bruno. -- Linux Profession Lead EMEA / Open Source Evangelist \HP CI EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398425: mondo: Crash during backup : *** glibc detected *** free(): invalid next size (fast): 0x080e1898 ***
Olivier LARRIGAUDIERE said on Wed, Nov 15, 2006 at 11:22:04AM +0100: Could you please give me more detailed instructions on how to produce a backtrace ? Please look at http://trac.mondorescue.org/wiki/AndreesStuff Bruno -- Linux Profession Lead EMEA / Open Source Evangelist \HP CI EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org pgpviJD61hv4Q.pgp Description: PGP signature
Bug#357785: mondoarchive exits with fatal error :Can't loopmount /tmp/mindilinux/8087/mountpoint8087
mahashakti89 said on Sun, Mar 19, 2006 at 08:11:19PM +0100: Could you retry without the FAILSAFE option please ? Already done this morning before I decided to post a bug report. I tried it one more time = same result Ok, will leave it to Andree when he comes back from vacations then, as I know he worked in that erea before leaving, and this is IMO a problem due to the Debian env. rather than an upstream pb (At least I think). Bruno. -- Linux Solution Consultant / Open Source Evangelist \HP CI EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357785: mondoarchive exits with fatal error :Can't loopmount /tmp/mindilinux/8087/mountpoint8087
Hello, [Main] mondo-cli.c-handle_incoming_parameters#270: -k FAILSAFE Could you retry without the FAILSAFE option please ? Bruno. -- Linux Solution Consultant / Open Source Evangelist \HP CI EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352323: FW: Bug#352323: mondo: ---FATALERROR--- Pre-param initialization phase failed. Please review the error messages above, make the specified changes, then try again. Exiting...
Andree Leidenfrost said on Sun, Feb 12, 2006 at 07:16:35PM +1100: Btw. the code I use is taken from libmondo-archive.c where we check in the same fashion the outcome of calling 'mindi -custom ...'. What do you say? Ok. Apply it. And as usual if you could adapt with asprintf for trunk, that would be great. Bruno. -- Linux Solution Consultant / Open Source Evangelist \HP CI EMEA ISG HP/Intel Solution Center http://hpintelco.net Hewlett-Packard Grenoble/France Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org pgpUalOVzlUBy.pgp Description: PGP signature
