From: Andrey Repin <anrdaemon@yandex.ru>
To: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>, cygwin@cygwin.com
Subject: Re: Wild card to address drives
Date: Thu, 18 Jul 2019 17:20:00 -0000 [thread overview]
Message-ID: <133450076.20190718201835@yandex.ru> (raw)
In-Reply-To: <98821e64-e055-0ff9-46ea-1dbcc061cd4c@t-online.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1412 bytes --]
Greetings, Hans-Bernhard Bröker!
> Am 18.07.2019 um 10:03 schrieb Fergus Daly:
>> I have
>> none / cygdrive binary 0 0
>> as the only line in the file /etc/fstab to allow for example
>> $ ls /h/config.sys
>> instead of the long-hand
>> $ ls /cygdrive/h/config.sys
> And that's precisely your problem. You've now overlaid two mount points
> onto /: the cygdrive tree, and the normal Cygwin root mount.
I understand that, but I don't understand the /proc/cygdrive behavior in such
case.
My expectation was that /proc/cygdrive/ would only hold Windows drives.
But...
$ ls -l /proc/cygdrive
lrwxrwxrwx 1 anrdaemon None 0 иÑл 18 20:17 /proc/cygdrive -> /
Why?
> Without this, your command would have worked just fine.
>> In Linux I can type something like
>> ls /?/ -Ax
>> as a wild card to address ALL drives,
> Not really, as there is no such thing as "drives" on Linux. The above
> will list all directories under / that have single letters as their name
> --- whether those be mounted filesystems, or ordinary directories.
--
With best regards,
Andrey Repin
Thursday, July 18, 2019 20:15:38
Sorry for my terrible english...\x03BKCB\x1cØ\x19[H\x1c\^[Ü\x1cÎ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÜ\x1cØ\x19[\Ë\x1d^[[\x03BTN\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ\KÃB^[ØÝ[Y[\x18]\x1a[Û\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ^[ØÜË\x1d^[[\x03B[ÝXØÜXH\x1a[Î\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÛ[\vÈÝ[ÝXØÜXK\Ú[\^[\x19CBB
next prev parent reply other threads:[~2019-07-18 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 8:03 Fergus Daly
2019-07-18 16:09 ` Hans-Bernhard Bröker
2019-07-18 17:20 ` Andrey Repin [this message]
2019-07-19 2:49 ` Brian Inglis
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=133450076.20190718201835@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=HBBroeker@t-online.de \
--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).