linux-ext4 - A question about the naming of e2fsprogs/tests

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 17 Oct 2012 21:13:51 +0800
From:	Zheng Liu <gnehzuil.liu@...il.com>
To:	linux-ext4@...r.kernel.org
Cc:	tytso@....edu, adilger.kernel@...ger.ca
Subject: A question about the naming of e2fsprogs/tests

Hi All,

Now I am trying to create some regression tests for e2fsprogs to test
inline data feature.  I have a question about the naming of
e2fsprogs/tests.  I notice that in tests dir there are a lot of
directories, which have different prefixes, such as d_loaddump,
e_brel_bma, f_baddir, m_dasd_bs, r_move_itable, t_mmp_1on, and u_mke2fs.
As far as I can understand, d_ is for debugfs, f_ means test for filesystem,
m_ is for mke2fs, r_ is for resize2fs, t_ is for tune2fs, and u_ is for e2undo.
Could anyone tell me what e_ stands for?  If I misunderstand something, please
point it out.  Thanks.

Regards,
Zheng
--
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