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
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49A4F3EC.7060005@slax.org>
Date:	Wed, 25 Feb 2009 08:31:56 +0100
From:	Tomas M <tomas@...x.org>
To:	"David P. Quigley" <dpquigl@...ho.nsa.gov>
CC:	Theodore Tso <tytso@....edu>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux kernel

David P. Quigley wrote:
> Earlier in the thread someone said that the AUFS team needs
> to slim it down to just core features and get those mainlined. The
> Unionfs team did this when we were moving for mainline inclusion and I
> think that is one of the reasons why people jumped ship and moved to
> AUFS.

I can speak just for myself, and in my opinion it wasn't it.

At least Knoppix and Slax switched to AUFS even before the release of unionfs 2.0.
The switch was not due to missing features in unionfs, it was due to huge instability, for example simple filesystem operations freezed the whole computer, mmap support was completely missing or broken (until unionfs people incorporated the idea from aufs), and so on. Any single similar problem did not happen with aufs, which is used in Slax by hundreds of thousands of users.

In general, I need an union filesystem and I do not care if that is unionfs or aufs. But since I have very bad experience with unionfs (and I am not alone), and I have very good experience with aufs, along with all hundreds of thousands users of Slax, I wish aufs to be mainlined; because the code simply works, since its initial release, for many years.

Tomas M
slax.org

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ