Return-Path: Received: from serenity.surpasshosting.com (serenity.surpasshosting.com [72.29.68.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 29 Aug 2009 21:57:45 +0200 (CEST) Received: from 160-129.94-24.tampabay.res.rr.com ([24.94.129.160]:38484 helo=localhost) by serenity.surpasshosting.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1MhU3L-00014E-52 for dm-crypt@saout.de; Sat, 29 Aug 2009 15:57:36 -0400 From: Stroker Date: Sat, 29 Aug 2009 15:58:58 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908291558.58894.dmcryptmailman@strokerville.com> Subject: [dm-crypt] Random fill List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de So, I estimate it will take 80 hours to fill my drives via: dd if=/dev/urandom of=/dev/sdb1 There seems to be mixed opinions regarding the use of frandom or erandom. My question is, wouldn't the following command fill my drives with randommess? Much more quickly than urandom? dd if=/dev/zero of=/dev/mapper/encrypted_sdb1 Perhaps change the key afterward, or even delete/rebuild the dm-crypt block? Thanks, Stroker