From: "Gluszczak, Glenn" <Glenn.Gluszczak@dell.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: chere install problem
Date: Mon, 25 Sep 2017 15:21:00 -0000 [thread overview]
Message-ID: <91DCAC3CB99C724EB365BB64677FBE7B1EFB1A21@MX204CL04.corp.emc.com> (raw)
In-Reply-To: <BN6PR2001MB10748F56BBAB57F02925805EF17A0@BN6PR2001MB1074.namprd20.prod.outlook.com>
"Hive not writable" sounds like permission for a registry key.
Mind you, Cygwin unloads the registry on a filesystem.
/proc/registry/HKEY_CURRENT_USER/....
------------------------------------------------------------------------------------------------------
Moving to a new machine with Windows 10 from an old machine with Windows 7, I am installing Cygwin from scratch. I am having trouble with package chere:
$ cygcheck -c chere
Cygwin Package Information
Package Version Status
chere 1.4-1 OK
$ chere -if -t mintty -s bash
Error (5): Access is denied.
/usr/bin/chere Error: Hive not writable
/usr/bin/chere: Aborting.
$
I've added "noacl" to the entries in /etc/fstab, but it had no effect:
none /cygdrive cygdrive binary,noacl,posix=0,user 0 0 C:/cygwin64/home /home dummy binary,noacl
Chere is a marvelously useful utility. I'd hate to have to give it up.
Any help?
--Ken Nellis
--
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
--
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:[~2017-09-25 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 15:09 Nellis, Kenneth
2017-09-25 15:21 ` Gluszczak, Glenn [this message]
2017-09-25 16:37 ` Nellis, Kenneth
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=91DCAC3CB99C724EB365BB64677FBE7B1EFB1A21@MX204CL04.corp.emc.com \
--to=glenn.gluszczak@dell.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).