From: Anton Farygin <rider@altlinux.com> To: ALT Linux kernel packages development <devel@altlinux.ru> Subject: [devel] [Fwd: [Unionfs] paid bugfix] Date: Mon, 23 Jan 2006 10:28:08 +0300 Message-ID: <43D48588.3050304@altlinux.com> (raw) [-- Attachment #1: Type: text/plain, Size: 44 bytes --] Никто не хочет заняться ? ;-) Rgds, Rider [-- Attachment #2: [Unionfs] paid bugfix --] [-- Type: message/rfc822, Size: 3311 bytes --] From: Tomas M <tomas@linux-live.org> To: unionfs@filesystems.org Cc: Subject: [Unionfs] paid bugfix Date: Sun, 22 Jan 2006 22:18:35 +0100 Message-ID: <43D3F6AB.6040000@linux-live.org> Hello all developers (official and unofficial) in this list. I see there are a lot of people who understand the unionfs code and can contribute to fix bugs in it. I would like to offer you an opportunity to make some money and to help unionfs at the same time :) For many months, I'm facing a problem while running unionfs as a chrooted filesystem (in a Live CD). Everything works correctly untill I add a new branch to the union (by using unionctl). Then the system hangs or at least behaves strange. This is very hard to reproduce or track. I don't know if this can be fixed or if it's just an unfixable issue, but here is my offer: If you 1) fix unionfs code so it will work correctly as a root filesystem with the ability to add branches and 2) the fix is accepted by unionfs developers to unionfs official sources then I'll pay you 2000 USD. I'm not able to help you much as I don't understand the unionfs code, but I'll do my best with providing my feedback and testing your patches. I hope this offer didn't offend anyone, if yes then please forgive me. Thank you very much. Tomas Matejicek slax.org linux-live.org _______________________________________________ unionfs mailing list unionfs@mail.fsl.cs.sunysb.edu http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
reply other threads:[~2006-01-23 7:28 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=43D48588.3050304@altlinux.com \ --to=rider@altlinux.com \ --cc=devel@altlinux.ru \ --cc=devel@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Team development discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \ devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru public-inbox-index devel Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.devel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git