Op Sun, 10 Oct 2004 13:13:23 -0400 schreef Christopher Faylor in <[EMAIL PROTECTED]>: : On Sun, Oct 10, 2004 at 08:36:38AM +0200, Bas van Gompel wrote: : > Op Sat, 9 Oct 2004 19:18:13 -0400 schreef Christopher Faylor : > So cygcheck will have the same problem... : : Right, but cygcheck can rely on the fact that cygwin1.dll is around, at : least, if necessary.
The dll is/should be around after setup ran (in install-mode), as well. : I guess a goal could be to come up with a generic : library which did sanity checking and corrections on cygwin permissions. Which would than have to be linked statically, or suffer from it's own permission-problems... : > How about doing it from a (postinstall-)script? : : A post-install script doesn't help if someone copied all of their stuff : to a CD-ROM and then to a new system. I didn't think that was a supported procedure. (IOW: YOWTWYWT) A post-install script does have the advantage of being run from within cygwin. : We really should improve setup, too, but I still think we need this in : two places. Probably. It could also be done from _cygwin_dll_entry, or some such. : Maybe we could get by with just having a sanity shell script that could : be run but it still seems like it should be tied into cygcheck somehow. : : Or, maybe we need a "cygfix"... Or more options to cygcheck: -F: try to fix. (implies -s) -p: print commands to execute to try to fix. (implies -qs) -q: suppress normal output. L8r, Buzz. -- ) | | ---/ ---/ Yes, this | This message consists of true | I do not -- | | / / really is | and false bits entirely. | mail for ) | | / / a 72 by 4 +-------------------------------+ any1 but -- \--| /--- /--- .sigfile. | |perl -pe "s.u(z)\1.as." | me. 4^re
