From: bills@warwick.net (bills)
Subject: RE: file system bogosity?
1 Aug 1998 02:38:57 -0700
Message-ID: <01BDBC9B.BABEC860.bills.cygnus.gnu-win32@warwick.net>
Reply-To: "bills@warwick.net" <bills@warwick.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: "'Charles Randall'" <crandall@matchlogic.com>
Cc: "gnu-win32@cygnus.com" <gnu-win32@cygnus.com>

You want file system bogosity?  Try this ( I started in / ):

/ ls
ARCHIVE       GRAPHICS      Programs      bin           pub
BAT           HTML          Q2Demo        code          stiwtts.jbc
CVS           LINT          RECYCLER      etc           tmp
Cygnus        MASM61        Temp          info          usr
Download      MISC          UTIL          msdownld.tmp  wbbu
/ cd ...
//... ls
ARCHIVE       GRAPHICS      Programs      bin           pub
BAT           HTML          Q2Demo        code          stiwtts.jbc
CVS           LINT          RECYCLER      etc           tmp
Cygnus        MASM61        Temp          info          usr
Download      MISC          UTIL          msdownld.tmp  wbbu
//... cd ...
//.../... ls
ARCHIVE       GRAPHICS      Programs      bin           pub
BAT           HTML          Q2Demo        code          stiwtts.jbc
CVS           LINT          RECYCLER      etc           tmp
Cygnus        MASM61        Temp          info          usr
Download      MISC          UTIL          msdownld.tmp  wbbu
//.../... cd ...
/code/Lethe/...
/code/Lethe/... ls
CVS             include         mtos            printers        syslib
Makefile        keyboards       objects         readers         utilities
communications  libmedia.a      ourlibc         screen          validation
displays        media           parameters      startup
/code/Lethe/...

-----Original Message-----
From:	Charles Randall [SMTP:crandall@matchlogic.com]
Sent:	Thursday, July 30, 1998 5:08 PM
To:	gnu-win32@cygnus.com
Subject:	file system bogosity?

Is there a plan to address file system bogosity such as the following?

	bash-2.01$ mkdir t
	bash-2.01$ cd t
	bash-2.01$ ls
	bash-2.01$ touch bozo
	bash-2.01$ ls
	bozo
	bash-2.01$ ls bozo.
	bozo.
	bash-2.01$

Note the "." on the end of the last ls command. That file doesn't exist.

Charles
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
