Timeline for What harm would there be in running strip on all files?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 2, 2016 at 19:47 | vote | accept | Délisson Junio | ||
| Aug 2, 2016 at 7:01 | answer | added | JigglyNaga | timeline score: 1 | |
| Aug 2, 2016 at 0:17 | answer | added | Gilles 'SO- stop being evil' | timeline score: 6 | |
| Aug 1, 2016 at 21:35 | answer | added | Thomas Dickey | timeline score: 11 | |
| Aug 1, 2016 at 21:10 | comment | added | grochmal |
If you run find / -type f -exec file {} \; | grep 'not stripped' you should get a list of all not stripped binaries, which should turn to be a rather short list. Then you only need to run strip on that. It probably is quicker that well too.
|
|
| Aug 1, 2016 at 21:06 | review | Close votes | |||
| Aug 2, 2016 at 10:24 | |||||
| Aug 1, 2016 at 20:39 | comment | added | Délisson Junio |
@StephenHarris true, most of them are, but there are some other packages i've installed manually that aren't, so I'm interested in any side-effects of running a system-wide strip
|
|
| Aug 1, 2016 at 20:32 | comment | added | Stephen Harris |
Are you sure they're not already stripped? Run file and see if it reports stripped in the output.
|
|
| Aug 1, 2016 at 20:28 | history | asked | Délisson Junio | CC BY-SA 3.0 |