From owner-freebsd-stable Thu Mar 30 8:54: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id B243D37B820 for ; Thu, 30 Mar 2000 08:54:01 -0800 (PST) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.9.3/8.8.8) with ESMTP id IAA25027; Thu, 30 Mar 2000 08:53:48 -0800 (PST) Message-Id: <200003301653.IAA25027@ptavv.es.net> To: "Jordan K. Hubbard" Cc: swhite@gov.za, stable@FreeBSD.ORG Subject: Re: Custom boot disks In-reply-to: Your message of "Thu, 30 Mar 2000 02:08:06 PST." <94087.954410886@zippy.cdrom.com> Date: Thu, 30 Mar 2000 08:53:48 -0800 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 30 Mar 2000 02:08:06 -0800 > From: "Jordan K. Hubbard" > Sender: owner-freebsd-stable@FreeBSD.ORG > > > I have several systems with broken PCI chipsets that I need to upgrade to > > 3.4-R from 2.2.7-R. I've patched 'pcibus.c' to fix the problem on these > > systems (reversed the config mode probe order) but now I need to build > > boot/install stiffies to get these machines up and running. Is there any > > quick/simple way to do this without going through a 'make release' > > process? > > Just make a kernel and make sure you keep "options MFS" and "options > MFS_ROOT" in there. Then whap it over the kernel on kern.flp, which > you can mount as a normal floppy. One step Jordan forgot to mention is that you need to gzip the kernel file before trying to move it to the floppy or it will never fit! Of course this is pretty obvious from the name of the kernel file on the floppy...kernel.gz. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message