Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "linda w \(cyg\)" <cygwin@tlinx.org>
To: <cygwin@cygwin.com>
Subject: RE: Wavplay for cygwin?
Date: Wed, 14 May 2003 18:18:11 -0700
Message-ID: <000101c31a7f$d9e66670$1403a8c0@sc.tlinx.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <Pine.GSO.4.44.0305141608340.26041-100000@slinky.cs.nyu.edu>


> /dev (like /proc and /cygdrive) is a virtual directory[*], 
> and is handled
> via cygwin1.dll. 
---
	Ahh...somehow 'ls /cygdrive' and ls '/proc' both show up 
with entries in them, but an 'ls /dev/' comes back with 
ls: /dev: No such file or directory, so it's not quite as obvious.

	As for proc going in 10 versions ago...well...maybe I just
forgot about it...but just saw someone mention it recently, so
I asked...oh well...

	I'd have alot easier time keeping track of the universe if I just
knew the initial state (and the CVS log of all the state transitions...
:-)).

> You can create a /cygdrive/c/cygwin/dev 
> directory, for
> tab completion and the like, and even use a batch file I 
> posted earlier to
> populate /dev with zero-length files that will show up as devices.
---
	Ah...will have to search on it.  Sounds useful.  My only
wish there was that different windows each had their own TTY identifier.
makes it easier to keep around a finite number of history files that
retain history from the past few sessions.  Often I'll forget an exact
command and remember I just used it and rather than reread the man page
and refiguring out the manpage, it's often easier to grep though my
bash history files -- not a reliable means, but an occasional laziness
technique.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/