This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Feedback needed on proposed cygwin feature
- To: cgf at bbc dot com
- Subject: Re: Feedback needed on proposed cygwin feature
- From: Jason Zions <jazz at softway dot com>
- Date: Mon, 01 Dec 1997 12:45:53 -0700
- CC: gnu-win32 at cygnus dot com
- Organization: Softway Systems Inc.
- References: <EKHt00.DM8@bbc.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".