Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've used dban before, but it actually creates a boot disk which destroys all the data on the drives. I'm looking for something that will run from within Linux that I can use to wipe only specific files and folders.
This person has a good entry on the 'shred' utility & why it is not effective. I've been looking for awhile, but have yet to find any. The best that I can find is to copy my data files to a thumb drive or CD, wipe the disk & re-install everything. No fun. Something HAS to be out there... or, one would hope =).
On this (Ubuntu) system the man page for shred says that the utility is effective on ext3 filesystems without journaling:
"In the case of ext3 file systems, the above disclaimer applies (and shred is thus of limited effectiveness) only in data=journal mode, which journals file data in addition to just metadata. In both the data=ordered (default) and data=writeback modes, shred works as usual."
So it should be OK unless the administrator has specifically enabled journaling on the filesystem that holds the target.
I'm not an expert, but I believe than ext3 has other extensions which may work on ext3 filesystems, and that the code automatically downgrades to ext2 mode if the actual filesystem was formatted as ext2. The Wikipedia article talks about directory indexes and support for resizing: http://en.wikipedia.org/wiki/Ext3.
My point was really that Red Hat, Fedora, Ubuntu and Debian format and mount filesystems as ext3 by default, but do not actually enable the journaling - so shred should be OK on most systems.
The Ubuntu (Dapper) package is 5.93-5ubuntu4, so the actual shred utility and documentation that I'm looking at could be more recent than on other systems, I guess.
if it's ext3 journaling is enabled.. if you mount an ext3 partition as EXT2, that is the only time journaling is disabled..
Journaling for ext3 is on by default otherwise it wouldn't be considered a jouraling file system and would simply be called ext2...
The ext3 journaling actually has several modes, and I think that this is confusing things. ext3 journals metadata by default, but it does not journal alterations to the files by default. As the bit I quoted says, the man page for shred (for this version at least) specifies that it is the non-default modes of ext3 that stop shred working correctly.