strip(1): will it goof anything?

[Mikel Manitius]

> > One note.  An unmonitored strip, perhaps stuck inside a find, will
> > silently remove setuid bits throughout the find path...be careful.
> 
> Or run it as "root".  I can't speak for System V (thanks to COFF, "strip"
> consists of no less than 8 ".c" files, and I'm not about to see how it does
> the stripping), but it may not remove the setuid bits there.
> 
> 	Guy Harris

I just checked strip on System V release 2, it does not change the suid
bits, nor the ownership. It really does not do anything to the program
other than strip the symbol tables.
-- 
	Mikel Manitius  - ...{ihnp4|akguc|attmail|indra!koura}!codas!mikel