From owner-freebsd-hackers Tue Jan 28 05:06:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA13075 for hackers-outgoing; Tue, 28 Jan 1997 05:06:35 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA13070 for ; Tue, 28 Jan 1997 05:06:32 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id XAA24970; Tue, 28 Jan 1997 23:56:44 +1100 Date: Tue, 28 Jan 1997 23:56:44 +1100 From: Bruce Evans Message-Id: <199701281256.XAA24970@godzilla.zeta.org.au> To: msmith@atrad.adelaide.edu.au, Shimon@i-Connect.Net Subject: Re: 2.2-BETA Questions Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > 9. Some safety checks in disklabel and newfs and/or kernel slice- >> > partition handling could be nice. If you create an 'a' partition >> > which is exactly an overlap of a 'c' in a slice that dominates >> > the disk, newfs will FREEZE the system. >> >> Novel. I've never seen that, and I've done it many times. > >I checked some more. It has to do with the manner in which disklabel is >called. If you have it use /etc/disktab, all is well. The -e is only safe >if you initialized with the (-rwB?) /etc/disktab option. `disklabel -e' should not start unless the label already exists. Perhaps you had a wrong label and reinitializing it fixed it. >> > 10. Kernel Question: On an i386 PC, how does one make sure that >> > another driver does not use the same ISA ports as you do? >> > You are trying to be nice and NOT use something someone else is >> > already using. There is a Linux thing to do that... >> >> ISA resource allocation is a particularly noisome can of worms. >> Currently, if your driver is configured with a base address in a >> region previously claimed by another driver, your probe routine won't >> be called. That can obviously cause problems if you plan to probe >> several possible port ranges in a single probe routine. > >Perfect! Linux drivers seem to explicitly call some routine that registers >the addresses. I like hte BSD solution better. It's simpler when it works, but inadequate. Bruce