From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: dev/null
Date: Sat, 06 Jan 2001 19:04:00 -0000 [thread overview]
Message-ID: <20010106220423.A14912@redhat.com> (raw)
In-Reply-To: <3A579C6B.23537.152CFF@localhost>
On Sat, Jan 06, 2001 at 10:30:03PM +0100, Gerrit P. Haase wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
><6 Jan 2001, 19:11 Uhr wars, als Melvyn Sopacua folgendes schrub:>
>< 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
>> > make[3]: *** [check-DEJAGNU] Error 1
>> >
>> > How to set up dejagnu or cygwin to handle this?
>>
>> How did you setup the /dev/null?
>> I can't get `mknod' to work. I always get 'function not supported'.
>>
>> And the flags - are they BSD compatible?
>
>It was just a try of me as i didn't get dejagnu to run. Normally,
>/dev/null is emulated inside cygwin and you don't need to set it up.
> I was a little blue-eyed, i made this as a directory, just with
>windows-explorer, but it didn't solve my problems.
Since /dev/null is not a directory that is hardly surprising.
>Try to ask again, with mknod as subject content.
Or, read the answer that I already provided.
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2001-01-06 19:04 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 ` Christopher Faylor [this message]
2001-01-07 8:09 ` dev/null Soren Andersen
2001-01-07 9:49 ` dev/null Christopher Faylor
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=20010106220423.A14912@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).