From owner-freebsd-questions Fri Sep 27 01:00:08 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA16996 for questions-outgoing; Fri, 27 Sep 1996 01:00:08 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA16962; Fri, 27 Sep 1996 01:00:05 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.6.12/8.6.12) with SMTP id AAA18399; Fri, 27 Sep 1996 00:58:51 -0700 Date: Fri, 27 Sep 1996 00:58:49 -0700 (PDT) From: Jaye Mathisen To: Larry Dolinar cc: owner-questions@freebsd.org, questions@freebsd.org Subject: Re: Little problems from Havana In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Couldn't this also be removing the gzip'd executable support? I don't remember the exact line, but I think it even says it in the GENERIC kernel that if you remove it, /stand/sysinstall won't work. On Thu, 26 Sep 1996, Larry Dolinar wrote: > Date: Thu, 26 Sep 1996 08:36:34 +600 CDT > From: Larry Dolinar > To: owner-questions@freebsd.org > Cc: questions@freebsd.org > Subject: Re: Little problems from Havana > > | From: "Donald J. Maddox" > > | > On Wed, 25 Sep 1996, Eliezer Rodriguez Gonzalez wrote: > | > > | > > I built a custom kernel, doing nothing else but eliminating the support > | > > for the hardware I don't have. I faced not problems doing that, it worked > | > > well from the very begining but I could no longer run the program > | > > /stand/sysinstall 'cause it cries with a: "Exec format error. Wrong > | > > architecture". > | > > | > Don't run sysinstall then. You don't really need it. What are you trying > | > to do that requires sysinstall? > > Are you sure you didn't also kill some of the "cpu" lines as well? The first > time I built a kernel (2.0.5) I only enabled the 486 and had the exact > same problem. Try leaving "I386_CPU" in along with your CPU of choice, > recompile, and see what happens. Not as efficient, but assuming it works, > you can find the sysinsall code and recompile it later. > > corections welcomed, > larry > > ps. Sorry for the humor in the other post: where is ee? I never saw a reply. >