From owner-freebsd-questions Wed Jan 16 15:11: 9 2002 Delivered-To: freebsd-questions@freebsd.org Received: from Mail4.mgfairfax.rr.com (fe4.southeast.rr.com [24.93.67.51]) by hub.freebsd.org (Postfix) with ESMTP id 717A037B416 for ; Wed, 16 Jan 2002 15:11:01 -0800 (PST) Received: from there ([24.168.212.227]) by Mail4.mgfairfax.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Wed, 16 Jan 2002 18:11:01 -0500 Content-Type: text/plain; charset="iso-8859-1" From: Ray Kohler To: sridharv@ufl.edu, questions@FreeBSD.ORG Subject: Re: about /dev Date: Wed, 16 Jan 2002 18:13:55 -0500 X-Mailer: KMail [version 1.3.2] References: <200201160407.XAA15222@anansi.vpha.health.ufl.edu> In-Reply-To: <200201160407.XAA15222@anansi.vpha.health.ufl.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: <0aa490111231012FE4@Mail4.mgfairfax.rr.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday 15 January 2002 11:07 pm, sridharv@ufl.edu wrote: > what do the device files in the /dev directory point to > exactly. the device drivers for that device?? > have seen some material about this but its not too > clear.. They are "virtual files" that can trick the system into thinking a lot of hardware are just regular files. For instance, if a program opens a regular file for writing, and writes on it, the data goes into that file on the disk. If it does the same to /dev/cuaa0, the data gets sent to the first serial port (assuming you have that driver in your kernel). This allows programmers not to care whether the output is to a file or to some hardware. All that's really stored on the disk for a device file is a pair of numbers to tell the kernel what kind of device it is and which one to use. -- Ray Kohler Playing an unamplified electric guitar is like strumming on a picnic table. -- Dave Barry, "The Snake" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message