From owner-freebsd-stable Sun Jul 23 16: 6:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2F63837BCF1; Sun, 23 Jul 2000 16:06:21 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA22470; Sun, 23 Jul 2000 16:06:09 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: John Baldwin Cc: Kris Kennaway , zingelman@fnal.gov, stable@FreeBSD.ORG Subject: Re: sysinstall resetting USA_RESIDENT=NO In-reply-to: Your message of "Sun, 23 Jul 2000 15:32:03 PDT." <200007232232.PAA25039@pike.osd.bsdi.com> Date: Sun, 23 Jul 2000 16:06:08 -0700 Message-ID: <22467.964393568@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, he's right. sysinstall is definitely broken in this respect, and > I'm definitely interested in your patches to fix it. :) One quick fix would be to disable the USA_RESIDENT hack entirely and just let users edit their make.conf files appropriately. When this bug was first reported, I looked at a couple of fixes to it and found them to be generally icky, adding to sysinstall's global variable bloat (which I'd dearly love to remove) or otherwise further obfuscating code which is already too obfuscated as it is. It was on my TODO list to simply shoot the damn thing in the head. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message