From owner-freebsd-stable Thu Mar 30 1:56: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.x-link.za.net (ns2.x-link.za.net [163.195.1.237]) by hub.freebsd.org (Postfix) with ESMTP id 71F1437BB8D for ; Thu, 30 Mar 2000 01:55:49 -0800 (PST) (envelope-from swhite@gov.za) Received: from localhost (swhite@localhost) by ns2.x-link.za.net (8.8.8/8.8.7) with SMTP id LAA14310 for ; Thu, 30 Mar 2000 11:55:50 +0200 (SAST) (envelope-from swhite@gov.za) Date: Thu, 30 Mar 2000 11:55:50 +0200 (SAST) From: X-Sender: swhite@ns2.x-link.za.net To: stable@freebsd.org Subject: Custom boot disks Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Forgive me if this is the wrong place to ask this but I need help with a sticky problem. 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? As a side issue, any chance of this patch making it into the standard distribution? I've tested it on as many different systems as I can, ranging from 486 to P-II and it's not broken on any of them. Regards, - Sean. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message