Subject: Re: kern/34085: "scsibus* at umass?" missing for GENERIC kernel
To: None <cube@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,>
From: Matthias Drochner <M.Drochner@fz-juelich.de>
List: netbsd-bugs
Date: 07/26/2006 10:50:02
The following reply was made to PR kern/34085; it has been noted by GNATS.

From: Matthias Drochner <M.Drochner@fz-juelich.de>
To: gnats-bugs@NetBSD.org
Cc: cube@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org,
	christianbiere@gmx.de
Subject: Re: kern/34085: "scsibus* at umass?" missing for GENERIC kernel 
Date: Wed, 26 Jul 2006 12:48:59 +0200

 cube@cubidou.net said:
 >  I'll probably fix scsibus.4, too, although it's interesting to have a
 >  list somewhere of the devices that expose the scsi attribute, so it
 > does
 >  make sense to have it that way. 
 
 The problem here is that no documentation tells which devices
 provide the "scsi" interface attribute, so the "at scsi?"
 example would be completely without context.
 Also in the kernel config files there is no logical chain
 between parent and child, but in this case the use of interface
 attributes is OK for efficiancy reasons. Users who want to
 wire down devices would revert to real device names.
 Btw, the config(8) language sucks here - the should be
 no question mark in "at scsi?" because attributes are
 not counted like devices.
 
 best regards
 Matthias