From owner-freebsd-alpha Mon May 17 19:22:29 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2F44B14E96 for ; Mon, 17 May 1999 19:22:27 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id TAA26726; Mon, 17 May 1999 19:21:39 -0700 Date: Mon, 17 May 1999 19:21:39 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Terry Lambert Cc: dfr@nlsystems.com, mike@smith.net.au, alpha@FreeBSD.ORG Subject: Re: I dunno... is this a bug? In-Reply-To: <199905172128.OAA27052@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ah! Perhaps that's why it changed... On Mon, 17 May 1999, Terry Lambert wrote: > > > I'm not sure why this worked before. The problem is that alpha puts the > > > label at offset 64 (dictated by OSF1 and NetBSD) and i386 puts it at > > > offset 512. We could update readdisklabel to look in both places I > > > suppose. > > > > I don't know why it did but it sure did! > > > > Why isn't readdisklabel a architecture independent function? One of the > > *huge* wins for Linux is it's ability to cope with multiple disk label > > formats. > > Because Julian's SLICE code is no longer there, and it was the function > of that code to perform disk identifications, like the one you suggest? > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message