linux-ext4 - Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs

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: <20070920215427.GL30221@thunk.org>
Date:	Thu, 20 Sep 2007 17:54:27 -0400
From:	Theodore Tso <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Andreas Dilger <adilger@...sterfs.com>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs

On Thu, Sep 20, 2007 at 03:22:16PM -0500, Eric Sandeen wrote:
> I'd do this, my rpm-fu is still reasonably strong, though - I'm curious,
> is there a compelling reason to split out just libcom-err?  what about
> libuuid?  libblkid?  e2fsprogs is a bit of a grab bag of things.  What's
> the rationale for the split?

Nope, there isn't much rationale unless we also split out fsck, so
that people who don't want to use any ext 2/3/4 filesystems don't need
to install programs like e2fsck, mke2fs, libext2fs.so, etc.   

The main reason why Debian did was more out of code wanking reasons
than anything else, as far as I know....

     	           	      	       	      	- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html