From: Igor Peshansky <pechtcha@cs.nyu.edu>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: Not directly Cygwin: Windows special filenames
Date: Mon, 31 Jul 2006 13:37:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.63.0607310917550.5912@access1.cims.nyu.edu> (raw)
In-Reply-To: <44CD87F6.30308@hotmail.com.INVALID>
On Mon, 31 Jul 2006, Shaddy Baddah wrote:
> Hi again,
>
> On 7/31/2006 2:11 PM, Shaddy Baddah wrote:
> > Indeed cygpath -m /dev/sda or /dev/sda1 return the equivalents from this
> > page. Is this misleading, seeing as they are not really valid DOS names?
>
> Sorry, that was a little presumptions of me. Are paths such as
> \device\harddisk0\partition0. When I try to open a file to this path, it is
> not recognised as valid.
>
> Does it live in the same namespace, so to speak, as C:, \\suchandsuchserver,
> etc?
I would imagine you'd need to use '\\.\device\harddisk0\partition0', but
MSDN is not particularly forthcoming on this issue...
> That's where I am coming from in terms of an expectation of what cygwin
> -w would return.
I take it you mean "cygpath -w"... Yes, I suppose one would expect to be
able to use the exact output of "cygpath -w" to open the equivalent
Windows file/device... PTC, of course.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
prev parent reply other threads:[~2006-07-31 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 4:11 Shaddy Baddah
2006-07-31 4:33 ` Shaddy Baddah
2006-07-31 10:26 ` Corinna Vinschen
2006-08-01 9:57 ` Shaddy Baddah
2006-07-31 13:37 ` Igor Peshansky [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=Pine.GSO.4.63.0607310917550.5912@access1.cims.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=cygwin-talk@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).