This is in reply to Christopher Faylor's post
http://cygwin.com/ml/cygwin/2002-09/msg01430.html
With this in mind I will like you to consider publishing in the Cygwin FAQ
the guidlines one should use for distributing an (open source) application
outside the official net release. I believe
On Mon, Sep 30, 2002 at 06:50:28AM -0700, Joshua Daniel Franklin wrote:
This is in reply to Christopher Faylor's post
http://cygwin.com/ml/cygwin/2002-09/msg01430.html
With this in mind I will like you to consider publishing in the Cygwin
FAQ the guidlines one should use for distributing an
This is in reply to Christopher Faylor's post
http://cygwin.com/ml/cygwin/2002-09/msg01430.html
I am trying to set the mind set here. As the person responsible for
cygwin
development, that's how we are progressing.
I totally agree and apreciate the openness.
Actually, it doesn't work all
- Original Message -
From: Igor Pechtchanski [EMAIL PROTECTED]
To: Doru Carastan [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, September 27, 2002 6:24 AM
Subject: Re: [Proposal] Moving user mount information to HKLM
On Thu, 26 Sep 2002, Doru Carastan wrote:
How about breaking free from
On Sat, Sep 28, 2002 at 06:49:00PM -0700, Doru Carastan wrote:
This is totally great news. I don't monitor the deloper list but it is great
to hear that my http://www.cygwin.com/ml/cygwin/2002-02/msg00805.html
suggestion is being considered. I am totally sorry about the fact that I
couldn't get
This is in reply to Christopher Faylor's message
http://cygwin.com/ml/cygwin/2002-09/msg01428.html. I hope it will show up
correctly in the mail list.
.. I expect that, as time progresses, there will be more checks to
ensure that doesn't happen. 1.3.13 has new checks for this, in fact.
This
On Sat, Sep 28, 2002 at 07:47:28PM -0700, Doru Carastan wrote:
.. I expect that, as time progresses, there will be more checks to
ensure that doesn't happen. 1.3.13 has new checks for this, in fact.
This makes sense only if RH views Cygwin as an Microsoft Windows OS
UNIX extension and not as a
On Thu, Sep 26, 2002 at 09:38:21PM -0700, Doru Carastan wrote:
How about breaking free from using the windoze registry. There is
absolutely no special need to use it IMO.
I'll second that. Relying on a single monolithic binary file for system
critical information is an extraordinarily bad
On Thu, 26 Sep 2002, Doru Carastan wrote:
How about breaking free from using the windoze registry. There is
absolutely no special need to use it IMO. All the mount info can be stored
in a plain ASCII file like 'cygwin.cfg'. As part of its initialization the
cygwin1.dll can use
On Fri, 2002-09-27 at 23:15, Charles Krug wrote:
On Thu, Sep 26, 2002 at 09:38:21PM -0700, Doru Carastan wrote:
How about breaking free from using the windoze registry. There is
absolutely no special need to use it IMO.
I'll second that. Relying on a single monolithic binary file for
On the user mount in HKLM idea, it's a no-goer. Normal users don't
have write access to most of HKLM, on any partly-secure install
of NT (which is where the original posters issue arose).
I may be wrong, but couldn't setup, or whoever creates the original
HKLM/../cygwin key, set up the
On Sat, 2002-09-28 at 00:19, Dan Vasaru wrote:
On the user mount in HKLM idea, it's a no-goer. Normal users don't
have write access to most of HKLM, on any partly-secure install
of NT (which is where the original posters issue arose).
I may be wrong, but couldn't setup, or whoever
users. But we'll
go with it while waiting for a better mount.
Thanks, Dan.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Robert Collins
Sent: Friday, September 27, 2002 4:28 PM
To: Dan Vasaru
Cc: [EMAIL PROTECTED]
Subject: RE: [Proposal] Moving user mount
Robert,
FWIW the HKLM user mounts would have the same security
ramification (which is why it's not a generically viable solution).
True, but one could fine-tune access rights to HKLM/Software/Cygwin such
that:
1) All users have Create subkey permission in HKLM/./Cygwin/Users.
2) All user
On 9/26/2002 9:38 PM, Doru Carastan wrote:
How about breaking free from using the windoze registry. There is
absolutely no special need to use it IMO. All the mount info can
be stored in a plain ASCII file like 'cygwin.cfg'. As part of its
initialization the cygwin1.dll can use
Problem:
The mount -u command fails if a domain user's registry hive is not
downloaded from the domain controller and no local hive cache exists.
Solution:
Change cygwin1.dll/mount to
1. store mount information under HKLM/CYGWIN/MOUNTS/{USER-SID}, or
2. let mount succeed without persisting
How about breaking free from using the windoze registry. There is
absolutely no special need to use it IMO. All the mount info can be stored
in a plain ASCII file like 'cygwin.cfg'. As part of its initialization the
cygwin1.dll can use GetModuleFileName() to figure out from where it was
17 matches
Mail list logo
