public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: dev/null
Date: Sun, 07 Jan 2001 09:49:00 -0000	[thread overview]
Message-ID: <20010107124950.A22232@redhat.com> (raw)
In-Reply-To: <3A584E4F.14775.318E1FA4@localhost>

On Sun, Jan 07, 2001 at 11:09:03AM -0500, Soren Andersen wrote:
>On 6 Jan 2001, an entity purporting to be Gerrit P. Haase
>[Gerrit P. Haase <gerrit.haase@t-online.de>] wrote [regarding Re: dev/null]
>
>> > Gerrit P. Haase wrote:
>
>> > > I created a dev/null, but then i got this error:
>
>> > > # of unexpected failures        2
>> > > WARNING: find_version failed:
>> > > couldn't read file "/dev/null": permission denied
>
>One thing that I have not read anybody explain yet, in this thread: the 
>WinDOS system counterpart to UNI* 'dev/null' is simply 'nul' (or 'NUL'). If 
>you need a null file to redirect IN to a command I guess you'd use that. I 
>never try to redirect out to /dev/nul in Cygwin or otherwise, anyway -- 
>although scripts generated by others need to be accomodated. But 
>manually, I just use 'nul'.

/dev/null in cygwin eventually translates to the Windows NUL device.

There is no reason to use 'NUL' rather than '/dev/null' since they are
both the same thing ... unless you enjoy using MS-DOS constructs rather
than UNIX ones.  That's sort of anti-Cygwin, though.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2001-01-07  9:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-01  4:14 dev/null Gerrit P. Haase
2001-01-06 10:12 ` dev/null Melvyn Sopacua
2001-01-06 10:43   ` dev/null Christopher Faylor
2001-01-06 13:28   ` dev/null Gerrit P. Haase
2001-01-06 19:04     ` dev/null Christopher Faylor
2001-01-07  8:09     ` dev/null Soren Andersen
2001-01-07  9:49       ` Christopher Faylor [this message]
2001-01-08  5:37         ` dev/null Soren Andersen
2001-01-08  6:53           ` dev/null Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010107124950.A22232@redhat.com \
    --to=cgf@redhat.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).