From owner-freebsd-hackers Tue Aug 29 19:31:48 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id TAA04069 for hackers-outgoing; Tue, 29 Aug 1995 19:31:48 -0700 Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id TAA04062 for ; Tue, 29 Aug 1995 19:31:44 -0700 Received: from [199.183.109.242] by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Tue, 29 Aug 1995 21:31:30 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 29 Aug 1995 21:31:32 -0500 To: "Kaleb S. KEITHLEY" From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: pilot error on my part or feedback on the 2.1 snap Cc: hackers@freebsd.org Sender: hackers-owner@freebsd.org Precedence: bulk "Kaleb S. KEITHLEY" writes: >On the advice of Richard Wackerbarth I decided to install the 2.1 snap >instead of the 2.0.5 RELEASE. >Is this somehow a pilot error or should I fall back to 2.0.5? I'm not quite sure what the problem is. However, in my defense, the code that is giving you trouble (the disk headers) is the same in 2.0.5 as it is in later versions. Personally, I dislike the design decision to subvert the entire concept of disklabeling simply to conform to MSDOS's way of doing things. But then I was not allowed to be party to that design decision. When I changed from 2.0 to 2.0.5, I had to go in and reformat EVERY disk (all 20Gig) and copy things onto new partitions. It wasn't fun, but now I am assured that I can remove any disk and use it as a bootable disk on another system. I hope you get past the disk initialization. Then if you have additional problems, perhaps I can help. ---- Richard Wackerbarth rkw@dataplex.net