Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!samba.rahul.net!rahul.net!a2i!olivea!grapevine.lcs.mit.edu!newsie.dmc.com!news.zipnet.net!usenet
From: mi@aldan.algebra.com (Mikhail Teterin)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: purpose of /stand ???
Date: 2 May 1996 15:58:18 GMT
Organization: Aldan at Newton Upper Falls
Lines: 18
Message-ID: <4mam2r$43v@news.zipnet.net>
References: <31724B4D.41C67EA6@merlin.rockwell.cz>
<4l46vg$ar@anorak.coverform.lan>
Reply-To: mi@ALDAN.algebra.com
NNTP-Posting-Host: ip23-max1-bos.zipnet.net
X-Newsreader: knews 0.9.6
Honorable Brian Somers
wrote on 18 Apr (in article <4l46vg$ar@anorak.coverform.lan>):
=These files are all linked to eachother. /stand is basically one big
=executable with lots of names. It checks its name to determine how to
=run. The idea is that a program capable of doing the job of 20 programs
=is less in size than the sum of the individual program sizes. It also
=has a rather big text segment that gets loaded once only (is this right?).
=
=As you already suspect, /stand stands for "standalone". These programs are
=used at installation time.
What are the pros and cons of using them regularly? Thanks!
-mi
--
"Windows for dummies"