From: jazz@softway.com (Jason Zions) Subject: Re: Feedback needed on proposed cygwin feature 1 Dec 1997 19:51:24 -0800 Message-ID: <348313F1.45C1076E.cygnus.gnu-win32@opennt.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: cgf@bbc.com Cc: gnu-win32@cygnus.com It strikes me that the best place for per-binary attributed like this would be in the binary itself. I don't know how closely cygwin's exec() looks at the program being exec'd; if it looks at the program header, there should be a way to squirrel the attributes away there someplace. Many "real Unix" systems do just this sort of thing; e.g. chatr in HP-UX, which is used to alter a.out attributes. Pro: a) attributes are *really* a part of the binary; symlinks and hardlinks all pointing to the same bits on the disk will behave the same, while name-based approaches may be inconsistent b) makes it easier for attributes to work over network mounts (when filesystems can be mounted in different places) Con: a) extracting the attributes from the binary may be slower b) may be hard to find a "safe place" to stash the bits Jason - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".