From owner-freebsd-current Fri Aug 13 15:59:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 6B2C21501F for ; Fri, 13 Aug 1999 15:59:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id UAA00649; Wed, 11 Aug 1999 20:01:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908120301.UAA00649@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: geoffr@is.co.za (Geoff Rehmet), brian@pobox.com, current@FreeBSD.ORG Subject: Re: ATA - Trouble mounting secondary master In-reply-to: Your message of "Wed, 11 Aug 1999 09:25:51 +0200." <199908110725.JAA56854@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 11 Aug 1999 20:01:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Geoff Rehmet wrote: > > Hmm, > > = > > My root device still lands up on "wd0" - even though my fstab has > > the root filesystem on ad0s1a. I haven't looked at getting it to > > use the ad dev entries for the root file system. (I'm assuming that > > is still WIP.) > = > Our boot blocks/loader dont have the needed computrons to use the > "ad" device name. However I have some patches to boot2 that allows > to boot off an ad root device, provided you dont use the loader, and > put the rigth boot string in boot.config. This should now be totally redundant as long as your /etc/fstab entry = is correct. -- = \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message