From owner-freebsd-stable Mon Jul 17 14:55: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 8C76F37B569; Mon, 17 Jul 2000 14:54:56 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA09936; Mon, 17 Jul 2000 14:54:55 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.9.3/8.9.3) id OAA73745; Mon, 17 Jul 2000 14:54:00 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000717213203.7240.qmail@web3102.mail.yahoo.com> Date: Mon, 17 Jul 2000 14:53:59 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Richard Stanaford Subject: Re: bioscall.s Cc: stable@FreeBSD.ORG, Keith Mackay , obrien@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jul-00 Richard Stanaford wrote: > --- David O'Brien wrote: >> On Mon, Jul 17, 2000 at 10:58:06AM -0400, Keith Mackay wrote: >> > Is there a known issue in bioscall.s? >> >> Yes, it has been documented all over the place in this mailing list. >> It is also documented in /usr/src/UPDATING. >> >> You should review the expectations of running -STABLE and consider if you >> are better off just sticking with the released product. > > > I have looked at both .. > > ftp://ftp.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING > ftp://cvsup2.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING > > And I see nothing regarding bioscall.s. If it's not much bother (I have to > wonder given the tone of your response) please indicate where this has been > documented. Mailing list archives. You would have seen literally 50+ messages about assembler errors in the past month if you had been reading this list, which is generally mentioned as a "requirement" of running -stable. As for UPDATING, the relevant entry is that the binutils (which includes the assembler) were upgraded: 20000706: Binutils were updated. In order to build a kernel after this date, you must follow the updating proceedure for building kernels exactly as presented here. You may be able to get away with doing it the old way, but if it breaks, make sure that you've tried the "To build a kernel" section with a fresh /usr/obj first. As you can see if you _read_ this entry, you need to follow "the updating proceedure [sic] for building kernels as presented here": To build a kernel ----------------- cd /usr/src # If you have not already done so, please buildworld here # You will also need to update your config file to 4.0. Usually # people tend to start with GENERIC from 4.0 and hack from there. make buildkernel KERNEL= make installkernel KERNEL= # Verify that the new kernel works, it will be installed as # /YOUR_KERNEL_HERE chflags noschg /kernel chflags noschg /YOUR_KERNEL_HERE mv /kernel /kernel.old mv /YOUR_KERNEL_HERE /kernel chflags schg /kernel The reason some people are rather short over this issue is that this has already been discussed about 50 times on this mailing list in the past month, and after a while answering the same question 50 times gets old. > Thank you, > -Richard -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message