From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Consequences of mount -c
Date: Fri, 24 Jun 2016 12:54:00 -0000 [thread overview]
Message-ID: <577c16cc-4f02-c779-e1a8-f909da4d1c02@gmail.com> (raw)
In-Reply-To: <20160624095236.7319634.62780.695@bonhard.uklinux.net>
On 24/06/2016 11:52, Fergus wrote:
> I have set
> /bin/mount -c "/"
> in â~/.bashrc with many subsequent easements in use.
> In /usr/share/fonts/microsoft/ there are unfortunately
> multiple links referring to files in
> /cygdrive/c/Windows/Fonts/; all broken.
> Similarly inâ /etc/, several links pointing to files in
> /cygdrive/c/Windows/System32/drivers/etc/; all broken.
> I've only just noticed this. I don't much want to remove the mount -c instruction. Is there anything else that can be done to correct things?
> Fergusâ
> ââ
>
if you use mount in â~/.bashrc, it is too late for postinstall script
like
/etc/postinstall/zp_fontconfig_cache_1.sh
Use /etc/fstab
------------------------------------
# For a description of the file format, see the Users Guide
# http://cygwin.com/cygwin-ug-net/using.html#mount-table
none / cygdrive binary 0 0
------------------------------------
and run again
/etc/postinstall/zp_fontconfig_cache_1.sh
Regards
Marco
--
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
next prev parent reply other threads:[~2016-06-24 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 10:55 Fergus
2016-06-24 12:54 ` Marco Atzeri [this message]
2016-06-24 13:32 ` Achim Gratz
2016-06-25 6:21 ` Andrey Repin
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=577c16cc-4f02-c779-e1a8-f909da4d1c02@gmail.com \
--to=marco.atzeri@gmail.com \
--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).