public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna.vinschen@cityweb.de>
To: Paul Sokolovsky <paul-ml@is.lg.ua>
Cc: Timothy Reaves <treaves@y11a165.neo.rr.com>,
	cygwin@sourceware.cygnus.com
Subject: Re: Total lack of accurate documentation!
Date: Sun, 28 Feb 1999 23:02:00 -0000	[thread overview]
Message-ID: <36D5C60C.5886E53C@cityweb.de> (raw)
Message-ID: <19990228230200.SNomAuK6sBgPYwM21TjWZQVkYnF6UIIkx4jOx8MSsnA@z> (raw)
In-Reply-To: <18958.990224@is.lg.ua>

Paul Sokolovsky wrote:
> [...]
>     Something like that I had, little more worse, though.
> I solved it globally (after consulting to maillist and being told
> those are 'features' of cygwin) - unmount all except root.
> Replace in registry '/' mount point from drive where
> windows installed to drive where cygwin itself installed (it's another
> cygwin feature). Make /tmp on that drive. Keep youself within that
> drive. Use //cygdrive/ syntax to access other drives (search list
> archive for more info). Forget forever about one of the MOST NICE
> and USEFUL features of cygwin.

Why do you tell this?

Nothing of this, what you are telling is really necessary! I'm using cygwin
mount points on many computers with many windows partitions and it works fine!
You are not obliged to use REGEDIT, to change the root mount! Try
	umount /
	mount [-bf] X: /
and you will see: This works, too!
So, too, it's definitly unnecessary, to use a //cygdrive style syntax!
Many nice features of cygwin are working as expected, some others have errors
in it, but less than windows itself! Some code also workarounds windows shit!

As a result, IMHO, your last sentence is a insolence!

Corinna


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  reply	other threads:[~1999-02-28 23:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-24 12:37 Timothy Reaves
1999-02-24 13:03 ` Re[2]: " Paul Sokolovsky
1999-02-25 13:56   ` Corinna Vinschen [this message]
1999-02-26  2:32     ` Paul Sokolovsky
1999-02-28 23:02       ` Paul Sokolovsky
1999-02-28 23:02     ` Corinna Vinschen
1999-02-28 23:02   ` Re[2]: " Paul Sokolovsky
     [not found] ` < 36D463C4.E65C2961@y11a165.neo.rr.com >
1999-02-24 13:45   ` DJ Delorie
1999-02-28 23:02     ` DJ Delorie
1999-02-28 23:02 ` Timothy Reaves
  -- strict thread matches above, loose matches on Subject: below --
1999-02-25 13:23 Earnie Boyd
1999-02-28 23:02 ` Earnie Boyd
1999-02-24 14:37 Andrew Dalgleish
1999-02-28 23:02 ` Andrew Dalgleish
1999-02-24 11:09 Timothy Reaves
     [not found] ` < 36D44F22.EE44A099@y11a165.neo.rr.com >
1999-02-24 11:33   ` DJ Delorie
     [not found]     ` < 199902241933.OAA31698@envy.delorie.com >
1999-02-24 11:56       ` Christopher Faylor
     [not found]         ` < 19990224145635.C26668@cygnus.com >
1999-02-24 12:11           ` DJ Delorie
     [not found]             ` < 199902242010.PAA31965@envy.delorie.com >
1999-02-24 18:08               ` Pierre A. Humblet
1999-02-28 23:02                 ` Pierre A. Humblet
1999-02-28 23:02             ` DJ Delorie
1999-02-28 23:02         ` Christopher Faylor
1999-02-28 23:02     ` DJ Delorie
1999-02-24 11:36   ` Paul Kinnucan
1999-02-28 23:02     ` Paul Kinnucan
1999-02-24 23:38 ` Heinz-Jürgen Oertel
1999-02-28 23:02   ` Heinz-Jürgen Oertel
1999-02-28 23:02 ` Timothy Reaves

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=36D5C60C.5886E53C@cityweb.de \
    --to=corinna.vinschen@cityweb.de \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=paul-ml@is.lg.ua \
    --cc=treaves@y11a165.neo.rr.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).