Subject: Re: kern/34085: "scsibus* at umass?" missing for GENERIC kernel
To: None <,,,>
From: Matthias Drochner <>
List: netbsd-bugs
Date: 07/26/2006 11:55:02
The following reply was made to PR kern/34085; it has been noted by GNATS.

From: Matthias Drochner <>
To: Quentin Garnier <>
Subject: Re: kern/34085: "scsibus* at umass?" missing for GENERIC kernel 
Date: Wed, 26 Jul 2006 13:54:52 +0200 said:
 > The contents of scsi.4 and other config files proves that we can't
 > expect people to maintain it (not that I blame anyone--it just cannot
 > be done). 
 Yes, sad but true.
 > audio has been listed that way since 1.6, and
 > I don't remember seeing people complaining about that facts
 So it should be OK... I did somehow assume that people,
 especially those with a traditional BSD background, expect
 a real device tree. Perhaps I'm too old.
 > adventurous users of adjustkernel
 While it isn't much of an issue for audio, wiring down disks
 makes a lot of sense even for average users, to avoid messup
 if one fails on boot.
 > Requesting that interface
 > attributes should appear without a wildcard would be fine with me,
 > however it will bring a whole new kind of confusion for some users.
 I don't think it is that bad. With a meaningful error message
 and a heads-up in current-users people could handle it.
 (I'd also prefer to have interface attributes easily recognized
 by some special syntax, and disallow the "device foo {}" shortcut
 in files.*. I've fixed a number of cases in the past where interface
 attributes were used needlessly in files.*, just creating bloat.)
 > So, where and how do you think I should list providers of "scsi" and
 > "atapi"?  In scsi.4 I guess, but I'm not sure of the form.
 scsi.4 already contains a list... I'd list both ways, the traditional
 one and the "at scsi?", separated by a big "or". btw, the "channel"
 locator should also be listed as in other bus attachments.
 best regards