[comp.unix.ultrix] Why unstripped DEC commands?

rcpt@rw7.urc.tue.nl (Piet Tutelaers) (10/18/90)

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? 

Thanks,

Piet Tutelaers

uucp:   rcpt@urc.tue.nl       | Piet Tutelaers        Room  RC 1.82
bitnet: rcpt@heithe5.BITNET   | Eindhoven University of  Technology
phone:  +31 (0)40 474541      | P.O. Box 513, 5600 MB Eindhoven, NL

grr@cbmvax.commodore.com (George Robbins) (10/19/90)

In article <143@rc6.urc.tue.nl> rcpt@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@cbmvax.commodore.com
Commodore, Engineering Department     phone:  215-431-9349 (only by moonlite)