From: Andrey Repin <anrdaemon@yandex.ru>
To: Fergus Daly <fergusd84@outlook.com>, cygwin@cygwin.com
Subject: Re: Contents of /dev/
Date: Mon, 9 Jan 2023 00:11:38 +0300 [thread overview]
Message-ID: <1792047542.20230109001138@yandex.ru> (raw)
In-Reply-To: <DB6P18901MB0055313BF90C37200F187DCFA4F99@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>
Greetings, Fergus Daly!
> Until recently my Cygwin installation (which is of considerable size though far from complete)
> consisted entirely of directories (here about 3300), files (49000), links (2300) and just 1 socket.
> Now under /dev/ I find
> 3 directories
> 0 files
> 4 links
> 12 type b being block (buffered) special
> 17 type c being character (unbuffered) special
> I don't think I've installed anything new for ages so these have probably arrived with an update.
> For me the last two types are an entirely new animal. Is it easy to explain what they are and (only
> secondly, out of interest) whether anybody else is experiencing this for the first time?
The "files" in /dev/ are virtual.
If you check the directory from outside the Cygwin environment, you'll see it
it nearly empty.
--
With best regards,
Andrey Repin
Monday, January 9, 2023 00:09:58
Sorry for my terrible english...
prev parent reply other threads:[~2023-01-08 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 14:39 Fergus Daly
2023-01-08 21:11 ` Andrey Repin [this message]
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=1792047542.20230109001138@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=fergusd84@outlook.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).