From owner-freebsd-current Sat Mar 31 12:42:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id E7F5E37B718; Sat, 31 Mar 2001 12:42:46 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2VD6dX07055; Sat, 31 Mar 2001 05:06:39 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103311306.f2VD6dX07055@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: current@freebsd.org, peter@freebsd.org Subject: Re: is it supposed to be this broken? In-reply-to: Your message of "Sat, 31 Mar 2001 02:15:12 PST." <20010331021512.H9431@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Mar 2001 05:06:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is cute... > > If you disable a device using /boot/device.hints like so: > hint.ppc.0.disabled="1" > hint.ppc.1.disabled="1" > hint.ppbus.0.disabled="1" > hint.ppbus.1.disabled="1" > > you get this: > ppc1: at port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on > isa0 That's because the PnP entity is still matched. You can't disable PnP devices; it just doesn't work that way. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message