From owner-freebsd-current Sat Jul 19 18:25:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA21070 for current-outgoing; Sat, 19 Jul 1997 18:25:11 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA21062 for ; Sat, 19 Jul 1997 18:25:07 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id SAA22428; Sat, 19 Jul 1997 18:24:11 -0700 (PDT) To: Sean Eric Fagan cc: current@FreeBSD.ORG Subject: Re: I am contemplating the following change... In-reply-to: Your message of "Sat, 19 Jul 1997 09:49:56 PDT." <199707191649.JAA15918@kithrup.com> Date: Sat, 19 Jul 1997 18:24:11 -0700 Message-ID: <22424.869361851@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As I just told Jordan... I disagree. > > The visual config stuff is neat, and can be a lifesaver... but requiring > users to do it is going to bite, *hard*. I had to help a (very technical) I agree, which is why I'd like to do something other than have to visit it EVERY SINGLE TIME I do an install in order to change from that obnoxious default of 5. I have probably installed several hundred FreeBSD machines at this point, for myself and many other people, and I have _yet_ to have a single card be at IRQ 5 by default. The ed1 entry is also the cause of much tech support for me since it "catches" cards at 0x300 but invariably with the wrong IRQ, so the user is tricked into thinking that things work until the install is well underway and the only message they're now seeing is: "ed1: device timeout" from the bogus IRQ value. Jordan