From owner-freebsd-bugs Tue Jun 6 01:06:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA07887 for bugs-outgoing; Tue, 6 Jun 1995 01:06:02 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA07880 ; Tue, 6 Jun 1995 01:05:54 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA30935; Tue, 6 Jun 1995 18:03:47 +1000 Date: Tue, 6 Jun 1995 18:03:47 +1000 From: Bruce Evans Message-Id: <199506060803.SAA30935@godzilla.zeta.org.au> To: gordon@sneaky.lonestar.org, jkh@freefall.cdrom.com Subject: Re: Comments on 2.0.5-ALPHA boot floppy - Jun 4 Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >> first screen just before it turns blue. I can't read much more >> than "etc/sysinstall" in repeated tries. The second screen >> shows that the system really DOES NOT LIKE my 1.1.5.1 disklabels >> and complains that several are "not entirely within the slice". >> Does this mean there is no chance for 1.1.5.1 and 2.0.5 to >> co-exist due to incompatible disklabel format, even if they >Not at all, it just means that 2.0.5 won't pass up the chance to >complain bitterly about them before grudgingly mounting them in >"compatability mode". :-) They will be compatible enough until you write a new label. BSD partitions outside of the BSD slice will be ignored after warning about them and the apparent number of sectors and cylinders on the disk will be reduced to the number in the slice. Writing the label will commit these changes to the disk and 1.1.5 may become confused. Don't write a new label if you want to keep running 1.1.5. >> The system finds network devices 'cuaa0' and 'cuaa1' which >> the -c option doesn't list. Are these PPP/SLIP pseudo-devices? >Yes, they are. That's why they're listed as "possible PPP/SLIP device" :-) Er, they are standard serial (callout) devices. Serial devices happen to be useable for PPP and SLIP. Bruce