From owner-cvs-user Thu May 18 03:17:54 1995 Return-Path: cvs-user-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA02557 for cvs-user-outgoing; Thu, 18 May 1995 02:21:01 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA02542 ; Thu, 18 May 1995 02:20:53 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: "Rodney W. Grimes" cc: CVS-commiters@freefall.cdrom.com, cvs-user@freefall.cdrom.com Subject: Re: cvs commit: src/release/sysinstall command.c disks.c dist.c install.c label.c menus.c system.c tcpip.c In-reply-to: Your message of "Thu, 18 May 95 02:05:12 PDT." <199505180905.CAA13935@gndrsh.aac.dev.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 18 May 1995 02:20:52 -0700 Message-ID: <2541.800788852@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: cvs-user-owner@FreeBSD.org Precedence: bulk > You might try asking me.... I have done a lot of bad144 work in the > last. Well, I thought you'd long since gone to bed as well.. :-) By all means, here's the question: Given a random slice (/dev/sd0s2, say), what bad144 command(s) should I run on the thing to make it do its magic? Jordan