From owner-freebsd-questions@freebsd.org Fri Jul 14 07:38:32 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 530DCD994F7 for ; Fri, 14 Jul 2017 07:38:32 +0000 (UTC) (envelope-from srs0=kjah=6r=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 3E7FC7FFC5 for ; Fri, 14 Jul 2017 07:38:31 +0000 (UTC) (envelope-from srs0=kjah=6r=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3x84LH2Gqcz2fkGs; Fri, 14 Jul 2017 00:38:31 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusual Question From: Doug Hardie In-Reply-To: <0ccfaae9-6fdb-adfa-71b2-5dd3978f41b3@qeng-ho.org> Date: Fri, 14 Jul 2017 00:38:30 -0700 Cc: David Christensen , "freebsd-questions@freebsd.org Questions" Content-Transfer-Encoding: quoted-printable Message-Id: <36DB0C7C-FF64-4BFA-9D7E-CF2A616FF534@mail.sermon-archive.info> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <0ccfaae9-6fdb-adfa-71b2-5dd3978f41b3@qeng-ho.org> To: Arthur Chance X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 07:38:32 -0000 > On 14 July 2017, at 00:26, Arthur Chance wrote: >=20 > On 14/07/2017 07:11, Doug Hardie wrote: >>=20 >>> On 13 July 2017, at 21:44, David Christensen = wrote: >>>=20 >>> On 07/09/17 02:57, Doug Hardie wrote: >>>> I have a FreeBSD 9.3 remote server that needs to be purged. I know = that rm -rf / will remove all the directory entries, but I need to write = over the drive. I thought that dd if=3D/dev/zero of=3D/dev/ada0 might = do the trick, but it gives an not permitted error. The whole thing can = crash and burn at the end. This is an unmanned site so moving drives is = not viable. >>>=20 >>> If the machine has BIOS and the system drive isn't too large, write = an assembly program that fits into the MBR bootstrap code area to wipe = the rest of the drive, assemble the program, write it into the MBR, and = reboot. >>>=20 >>>=20 >>> Bonus: the program deletes the MBR when done wiping the rest of the = drive. >>=20 >> Neat idea, but I have a number of these systems and they all use = different disk drives. That would be a lot of work writing drivers for = each type. >=20 > How about using the BIOS extended write sector call (INT 13h, AH=3D43h) = in > your code? That should be portable. I have no experience with the BIOS so that sounds reasonable, but I = couldn't say for sure. Even so, that would be a bunch of work to figure = all that out. Great project for someone with time available.