https://sourceforge.net/p/dban/patches/2019-05-27T07:43:01.118000ZRecent changes to patches2019-05-27T07:43:01.118000Z2019-05-27T07:43:01.118000ZM. S. https://sourceforge.net/u/msdban/https://sourceforge.net111b74581e5e980b9457266b58304604c9128f64

<div class="markdown_content"><p>I am trying to use DBAN for the first time, but cannot get it to load using Bootable USB or CD. When trying to use a CD, I get the message 'Can't open "/proc/cmdline". When trying to enter drive list when DBAN started from CD.</p> <p>When trying to use a Bootable USB, I get ‘Loading – This may take several seconds…’ but it never loads. </p> <p>I have a Gigabyte GA-Z270X-UD5 motherboard, running Windows 10 Pro with UEFI bios, and using YUMI-UEFI-0.0.1.5 &amp; the DBAN distro to create the bootable USB. </p> <p>Please advise. </p></div>

2007-10-11T03:21:24Z2007-10-11T03:21:24ZMatt Domschhttps://sourceforge.net/u/mdomsch/https://sourceforge.net279da4f1d3181021e8b2a84960ad34b12931cd98

<div class="markdown_content"><p>First, thanks for this program - I've found it useful. I wanted to be able to run the dwipe function in the context of a running Fedora 7 x86_64 system rather than boot a stand-alone CD. In building from dban 1.0.7 source, I had to fix a few things for it to build.</p> <p>* There are some 64-bit unclean points which I didn't fix all, but fixed at least one.</p> <p>* the third argument to _IOR is not a sizeof, it's the actual type. BLKGETSIZE64 definition needed fixing.</p> <p>* gzip.c build_bl_tree() prototype and definition didn't quite match.</p> <p>* syscalls.c _syscall3() and _syscall2() prototypes were incorrect.</p></div>

2003-02-26T20:19:36Z2003-02-26T20:19:36ZBen Hochstrasserhttps://sourceforge.net/u/tictactux/https://sourceforge.net875c5051fbed3b70cb5541df1144e1cd906a1113

<div class="markdown_content"><p>I slightly modified the rc file (and consequently built a new initrd) so <br /> that instead of running the complete Gutmann mantra only the <br /> following is done:</p> <p>wipe -z .......<br /> wipe -b85 ......<br /> wipe -b170 <br /> ......<br /> wipe -b255 ......<br /> wipe -z ......</p> <p>As multiple calls to wipe <br /> are necessary for this it has the additional advantage that each drive <br /> gets some time to settle the bits before the next wipe. (i.e. first all <br /> drives get zeroed, then all drives get -b85'ed etc.)</p> <p>I was <br /> thinking about putting some flag file ŕ la DOD_NUKE on the floppy <br /> instead of having two different diskette images but thought I'd better <br /> hear your opinion first.</p> <p>Thanks for this tool!</p> <p>--<br /> Ben</p></div>