From owner-freebsd-stable Tue Mar 10 13:43:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06859 for freebsd-stable-outgoing; Tue, 10 Mar 1998 13:43:55 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from northwest.com (port31.northwest.com [204.119.42.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06753 for ; Tue, 10 Mar 1998 13:43:32 -0800 (PST) (envelope-from stevemw@northwest.com) Received: from fuji (localhost [127.0.0.1]) by northwest.com (8.8.8/8.8.7) with ESMTP id NAA02605; Tue, 10 Mar 1998 13:42:09 -0800 (PST) (envelope-from stevemw@fuji) Message-Id: <199803102142.NAA02605@northwest.com> To: Mike Smith cc: Robert Watson , stable@FreeBSD.ORG Subject: Re: New mount/slice changes for root device In-reply-to: Your message of "Tue, 10 Mar 1998 13:10:34 PST." <199803102110.NAA20209@dingo.cdrom.com> Date: Tue, 10 Mar 1998 13:42:08 -0800 From: Stephen Wynne Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In message <199803102110.NAA20209@dingo.cdrom.com>, Mike Smith writes: There is a typo in the code responsible for this message; you can safely ignore it as you surmised. It'll be fixed shortly. I had to change my root from /dev/wd0a to /dev/wd0sNa as well. (In my case, N = 2 because of some bizarre things I'm doing with NT.) I have some other related things to observe that may not be specific to this update. o I have an odd configuration with just one 1.9GB /. Don't ask -- NT is involved, and it was what I used to create the partition table. o I seem to have to fsck every time I boot now! Perhaps all the "-c" boots are doing that to me... I, too survived the "broken window" yesterday to cvsup twice, but then when I got it all together, I tried to create a debugging kernel, and I suddenly got hit with the 1023-cylinder limit from /usr/src/sys/i386/boot/biosboot/disk.c: line 223. o I adventurously modified this to the limit which my bios accepts, and then booted again. Is that OK? o I ran into problems with the BOUNCE_BUFFERS option at that point. o I didn't know what to do, so I gave up and gladly compiled and booted from a normal kernel, which is working fine. Suggestions on how to deal with the error I got with my bounce buffers? By the way, I now have my vibra16 (Soundblaster 16 PnP) working very well with Luigi Rizzo's bits. FreeBSD is rocking -- literally! I'll stick a web page up on how I did it if anyone is interested. Thanks, Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message