From: <evansbryant@look.ca>
To: <cygwin@sourceware.cygnus.com>
Subject: RE: Why not mount / at C: ?
Date: Thu, 24 Aug 2000 15:56:00 -0000 [thread overview]
Message-ID: <001201c00e1f$2ac67c80$5c8e42d8@raptor> (raw)
In-Reply-To: <200008240853.KAA09772@dphdse.saclay.cea.fr>
> It's likely a FAQ, but since I still don't understand :
> Why is it discouraged to mount '/' at 'C:' ?
In general, under Windows, mounting things in C:\ is just a bad idea. for
one thing, some proprietary software already install things as \bin and
others. Some ISP installations do this, and some computer outlets install
things there. Do you really want to have Cygwin wiped because you install a
new ISP?
Also, though most of the people on a developers list might handle things in
root well, average users do not. I have seen users with over 100 files
(docs, etc) in their root.
~Neil
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-08-24 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-24 1:53 Jean-Paul Le Fevre
2000-08-24 15:56 ` evansbryant [this message]
2000-08-30 8:42 ` David A. Cobb
2000-08-30 9:05 ` DJ Delorie
2000-08-31 9:24 ` David A. Cobb
2000-08-24 4:54 Earnie Boyd
2000-08-24 5:43 ` Jean-Paul Le Fevre
2000-08-24 7:33 ` David Starks-Browning
2000-08-30 5:43 ` David A. Cobb
2000-08-30 7:25 ` Chris Faylor
2000-08-24 16:14 ` evansbryant
2000-08-26 20:51 ` Gregory Walker
2000-08-30 7:27 ` David A. Cobb
2000-08-30 7:50 ` Chris Faylor
2000-08-24 6:29 ` Egor Duda
2000-08-30 7:25 ` David A. Cobb
2000-08-24 6:27 Nash, John
2000-08-24 7:51 Earnie Boyd
2000-08-24 8:04 Earnie Boyd
2000-08-24 9:45 Bernard Dautrevaux
2000-08-30 9:19 Peter Ring
2000-08-30 10:08 ` DJ Delorie
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='001201c00e1f$2ac67c80$5c8e42d8@raptor' \
--to=evansbryant@look.ca \
--cc=cygwin@sourceware.cygnus.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).