From owner-freebsd-bugs Thu Apr 16 12:50:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25350 for freebsd-bugs-outgoing; Thu, 16 Apr 1998 12:50:54 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: (from gnats@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25256; Thu, 16 Apr 1998 12:50:20 -0700 (PDT) (envelope-from gnats) Date: Thu, 16 Apr 1998 12:50:20 -0700 (PDT) Message-Id: <199804161950.MAA25256@hub.freebsd.org> To: freebsd-bugs Cc: From: "Jonah Kowall" Subject: Re: kern/6204: wdc0 goes away with newest sources Reply-To: "Jonah Kowall" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/6204; it has been noted by GNATS. From: "Jonah Kowall" To: , "Jonah Kowall" Cc: Subject: Re: kern/6204: wdc0 goes away with newest sources Date: Thu, 16 Apr 1998 15:40:08 -0400 This had to do with the device change in the STABLE tree. This message I found in the lists sums it up. So please close the bug report. On Thu, 12 Mar 1998, Kent Vander Velden wrote:> > Hos something changed in -current during the past two weeks that would > affect how the root filesystem is mounted? The problem that I am seeing > at the moment is with a new -current kernel, the root file system will > fail to mount on boot. Running mount with no arguments shows that / > has the device 'root_device' mounted on it and not '/dev/sd0a' as I would > aspect. When I try to mount '/dev/sd0a' on / mount gives the error: > "Specified device does not match mounted device.\n". I will try recompiling > mount in a moment. Any other suggestions?Try sd0s1a. I think a change went into -stable too -- have had some complaints from stable users about a name change. - Jonah Kowall VP Technology Coffeehaus Networks / Content Advisor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message