| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <BANLkTini-g9XVOohKjwpZT-SGozcwx720A@mail.gmail.com> Date: Tue, 12 Apr 2011 17:00:03 +0200 From: Michal Suchanek <hramrach@...trum.cz> To: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Unionmount status? Hello, as some already know the Unionmount VFS union which has been in development for some years now is the only True Union (TM) that can be accepted into the kernel mainline by the VFS maintainers (for reasons of their own which you can surely find if you search the web or ask them directly). The current UnionMount version that can be found here: http://git.kernel.org/?p=linux/kernel/git/val/linux-2.6.git;a=shortlog;h=refs/heads/ext2_works works for me as good as aufs does. That is I can build a live CD using this unioning solution and it boots and runs without any apparent issues. There are probably many possible uses of the union which I did not test nor did I test long term stability of using the unioned filesystem. As far as ephemeral live systems go it works fine for me, though. The issue is that while the code is (nearly) finished it is not yet merged into mainline and as I am not familiar with the details of ever-changing Linux VFS layer forward-porting this code to current kernels is somewhat challenging. What is the plan with unionmount now? What is required for it to be merged into mainline? Thanks Michal -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists