old-www/HOWTO/Ext2fs-Undeletion-12.html

36 lines
1.5 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>Linux Ext2fs Undeletion mini-HOWTO: Will this get easier in future?</TITLE>
<LINK HREF="Ext2fs-Undeletion-13.html" REL=next>
<LINK HREF="Ext2fs-Undeletion-11.html" REL=previous>
<LINK HREF="Ext2fs-Undeletion.html#toc12" REL=contents>
</HEAD>
<BODY>
<A HREF="Ext2fs-Undeletion-13.html">Next</A>
<A HREF="Ext2fs-Undeletion-11.html">Previous</A>
<A HREF="Ext2fs-Undeletion.html#toc12">Contents</A>
<HR>
<H2><A NAME="sec-easier"></A> <A NAME="s12">12. Will this get easier in future?</A></H2>
<P>Yes. In fact, I believe it already has. Although as of this writing,
current stable kernels (in the 2.0.x series) zero indirect blocks, this does
not apply to development kernels in the 2.1.x series, nor to the stable
2.2.x series. As I write this on 2 February 1999, kernel 2.2.1 was released
a few days ago; Linux vendors are likely to start producing distributions
containing and supporting 2.2.x kernels a month or two from now.
<P>Once the indirect-zeroing limitation has been overcome in the production
kernels, a lot of my objections to the technique of modifying inodes by hand
will disappear. At the same time, it will also become possible to use the
<CODE>dump</CODE> command in <CODE>debugfs</CODE> on long files, and to conveniently use
other undeletion tools.
<P>
<P>
<HR>
<A HREF="Ext2fs-Undeletion-13.html">Next</A>
<A HREF="Ext2fs-Undeletion-11.html">Previous</A>
<A HREF="Ext2fs-Undeletion.html#toc12">Contents</A>
</BODY>
</HTML>