Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Steve Jorgensen <steve AT khoral DOT com>
Message-Id: <199910272047.OAA10593@benson>
Subject: Re: Snapshot and CD compatibility problems
To: cygwin AT sourceware DOT cygnus DOT com
Date: Wed, 27 Oct 1999 14:47:17 -0600 (MDT)
In-Reply-To: <19991027163120.B6229@cygnus.com> from "Chris Faylor" at Oct 27, 99 04:31:20 pm
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text

Chris Faylor wrote
>> >Chris Faylor wrote
>> >> On Wed, Oct 27, 1999 at 09:36:33AM -0600, Steve Jorgensen wrote:
>> >> >	Well, I created a /etc/passwd and /etc/group.  I guess my
>> >> >	confuse lies in that all I did was change the DLL, I didn't mess
>> >> >	with the CYGWIN variable or any of the other cygwin settings/config
>> >> >	files.  Does the CD cygwin1.dll have different defaults than
>> >> >	the snapshot?
>> >> 
>> >> Yes.  The default is "nontsec" on the Cygwin CD.  The snapshots have had
>> >> "ntsec" turned on so that people will test it.
>> >
>> >	Ok, well, I went back and played with the 10/25/1999 snapshot dll,
>> >	and setting nontsec vs ntsec.  If I use nontsec, this mode
>> >	causes the dll to change permissions on files I write out such that
>> >	I can't write to those files again.  If I leave it in ntsec mode and
>> >	add appropriate /etc/passwd entries, it works, but file access is
>> >	slower, presumable because it is looking up permissions.
>> >
>> >	Is there any way to get the snapshot to work under "nontsec" as the
>> >	CD version did?
>> 
>> The "nontsec" code on the snapshot is equivalent to the CD.  I just
>> turned off the ntsec on the CD.
>> 
>> I don't know what you're referring to when you say that this causes the
>> "DLL to change permissions".  What are the permissions?  Can you give
>> an example?

	Ok, here's what I'm seeing.  With the CD dll, I get the following
	on an ls -l on a file created by this dll:

	% ls -l Toolboxes
	-rw-rw-rw-   1 adminstr None	854 Oct 27 13:33 Toolboxes

	It stays this way after I change the file with some Khoros
	utilities that add and remove toolboxes.

	With the 10/25/1999 dll, both with the ntsec and nontsec set, before
	I touch the file, I get

	%ls -l Toolboxes
	-rwxrwxrwx   1 adminstr None	854 Oct 27 13:33 Toolboxes*

	After writing the file out using the same Khoros utilities as before
	with nontsec, I get:

	%ls -l Toolboxes
	-r--r--r--   1 adminstr None	854 Oct 27 13:33 Toolboxes

	with ntsec and appropriate /etc/passwd entries, I get:
	-rw-rw-rw-   1 adminstr None	854 Oct 27 13:33 Toolboxes

	Note, in all cases with the 10/25/1999 dll, the file permissions
	cannot be changed with chmod.

	In fact the most telling difference is that the NT security pane
	when you look at a file's properties is different.  File created
	under the CD dll, has permissions set to:

	Everyone ... Full Control (All)

	where under the 10/25/1999 dll, under nontsec (after I write it out)
	you get:

	Everyone ... Special Access (R)
	HOBBS\administrator ... Special Access (RWDPO)

	with ntsec set, I get
	
	Everyone ... Special Access (RW)
	HOBBS\administrator ... Special Access (RWDPO)

	Why doesn't it just set Full Control (All) as it started out?

	If it helps, I can send you my cygcheck output.
>> 
>> >	I'm not real clear on what it means when you say that the DLL
>> >	is compatible, but the library and object files may not be, but
>> >	I'm guessing there is something else I need to do when I play
>> >	with snapshots.
>> 
>> The DLL is compatible with older executables.  Executables are files
>> whose filename ends in ".exe".
>> 
>> Older object files and libraries may not be compatible with the DLL.
>> They may refer to globals that have been moved from libcygwin.a into
>> the DLL itself.
>> 
>> That means that you have to recompile them.  Object files are filenames
>> that end in '.o'.  Libraries are filenames which end with '.a'.
>> 
>> If you still don't get this, then maybe somebody else on the list can
>> try to explain.  I'm pretty much explained out.
	Ok, I get this now.  This is not my problem then, sorry for
	the hassle.

						Steve


-- 
-----------------------------------------------------------
Steven Jorgensen      steve AT khoral DOT com	    steve AT haunt DOT com
------------------------------+----------------------------
Khoral Research Inc.          | PHONE: (505) 837-6500
6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
Albuquerque, NM 87110         | URL: http://www.khoral.com/
-----------------------------------------------------------

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com