From owner-freebsd-hackers  Mon Jun 12 13:42:24 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA20708
          for hackers-outgoing; Mon, 12 Jun 1995 13:42:24 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA20700
          for <hackers@freebsd.org>; Mon, 12 Jun 1995 13:42:19 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA27564; Tue, 13 Jun 1995 06:40:18 +1000
Date: Tue, 13 Jun 1995 06:40:18 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199506122040.GAA27564@godzilla.zeta.org.au>
To: hackers@freebsd.org, jfieber@cs.smith.edu
Subject: Re: `device' versus `disk' in kernel config file
Sender: hackers-owner@freebsd.org
Precedence: bulk

>What exactly is the difference between saying:

>   device sd0
>   device st0

>and 

>   disk sd0
>   tape st0

>in a kernel config file?

The latter wouldn't work.  In general, `disk's are attached to controllers
and `devices's are stand-alone.  `device sd0' would give little more than
a file "sd.h" with `#define NSD 1" in it, except config/mkioconf.c knows
that the devices cd, ch, sd, st and uk are scsi devices (:-() and generates
extra code for them.

Bruce