public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Ability to specify /cygdrive mount value in setup
Date: Sun, 06 Dec 2015 17:12:00 -0000	[thread overview]
Message-ID: <874mfvtsb2.fsf@Rainer.invalid> (raw)
In-Reply-To: <87egeztzwg.fsf@Rainer.invalid> (Achim Gratz's message of "Sun,	06 Dec 2015 15:28:15 +0100")

Achim Gratz writes:
> I need cygpath to get the system directory (hint: it need not be in
> C:\Windows\System32) and cygpath delivers that directory with the
> cygdrive prefix and not /proc/cygpath prepended.  I wouldn't mind if all
> those special directories would also be available via /proc/<whatever>,
> which means I wouldn't even need to fork cygpath for getting there.

This will get me the correct path to link to, but I still think it's
unnecessarily ugly (and took a while to cover all the possibilities of
not-so-well-formed cygdrive prefixes):

--8<---------------cut here---------------start------------->8---
CYGDRIVE="$(/usr/bin/cygpath -u C:)"
WINETC="$(/usr/bin/cygpath -S -u)/drivers/etc"
WINETC="/proc/cygdrive/${WINETC#${CYGDRIVE%c}}"
--8<---------------cut here---------------end--------------->8---

versus the hypothetical

--8<---------------cut here---------------start------------->8---
WINETC="$(/usr/bin/cygpath -S -U)/drivers/etc"
--8<---------------cut here---------------end--------------->8---

BTW, the path comprising the cygdrive prefix probably needs to be
sanitized to avoid things like

--8<---------------cut here---------------start------------->8---
$ mount -c /bla//fasel////blum//////
--8<---------------cut here---------------end--------------->8---

leaking into the wild.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2015-12-06 17:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 19:06 Charlie
2015-11-25 20:35 ` Andrey Repin
2015-11-25 21:01   ` cyg Simple
2015-11-25 22:44     ` Buchbinder, Barry (NIH/NIAID) [E]
2015-11-26 13:52       ` Corinna Vinschen
2015-11-26 18:06         ` Achim Gratz
2015-11-26 20:08           ` Corinna Vinschen
2015-11-29 18:25           ` cyg Simple
2015-11-29 20:15           ` cyg Simple
2015-12-06  9:47         ` Achim Gratz
2015-12-06 14:10           ` Corinna Vinschen
2015-12-06 14:28             ` Achim Gratz
2015-12-06 17:01               ` cyg Simple
2015-12-06 17:16                 ` Achim Gratz
2015-12-06 17:12               ` Achim Gratz [this message]
2015-12-06 19:02               ` Corinna Vinschen
2015-12-06 19:07                 ` Achim Gratz
  -- strict thread matches above, loose matches on Subject: below --
2015-11-25 16:24 cyg Simple
2015-11-25 16:50 ` Eliot Moss
2015-11-25 17:39 ` Andrey Repin
2015-11-25 19:17   ` Buchbinder, Barry (NIH/NIAID) [E]
2015-11-25 18:51 ` Roger Wells

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=874mfvtsb2.fsf@Rainer.invalid \
    --to=stromeko@nexgo.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).