Why unstripped DEC commands?
George Robbins
grr at cbmvax.commodore.com
Fri Oct 19 09:13:08 AEST 1990
In article <143 at rc6.urc.tue.nl> rcpt at urc.tue.nl writes:
> There are a lot of ULTRIX commands that are not stripped. On our Ultrix 3.1
> DECstations we have for example:
> /usr/bin/dxterm: mipsel demand paged setuid executable not stripped - version 1. 31
> -rwsr-xr-x 5 root 5080168 Nov 16 1989 /usr/bin/dxterm
> If I strip this command I get a size of:
> -rwxr-xr-x 1 rcpt 2727936 Oct 18 12:04 /rc6u1/rcpt/dxterm
>
> Can somebody explain why this, and other commands, are NOT stripped. Is this to
> sell more disks?
Most of the commands *are* stripped. Far too many of them in my opinion, since
it makes it impossible to trace/debug them when something goes wrong. I'm
not sure why some aren't stripped, perhaps because they do need to debugged,
or because the program or some other program needs access to the symbol table
or perhaps simple oversight...
--
George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing: domain: grr at cbmvax.commodore.com
Commodore, Engineering Department phone: 215-431-9349 (only by moonlite)
More information about the Comp.unix.ultrix
mailing list