Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.hawaii.edu!ames!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: 13 May 1996 21:43:57 GMT
Organization: Aldan at Newton Upper Falls
Lines: 20
Message-ID: <4n8aet$40m@news.zipnet.net>
References: <31724B4D.41C67EA6@merlin.rockwell.cz>
<4l46vg$ar@anorak.coverform.lan> <4mam2r$43v@news.zipnet.net>
<4mtgtp$il@anorak.coverform.lan> <4n0c00$ooo@uriah.heep.sax.de>
Reply-To: mi@ALDAN.algebra.com
NNTP-Posting-Host: aldan.zipnet.net
X-Newsreader: knews 0.9.6
Honorable J Wunsch
wrote on 10 May (in article <4n0c00$ooo@uriah.heep.sax.de>):
[About using /stand binaries]
=> Pros: Save disk space by removing the 'real' versions
=> Cons: They are a bit skeletal - they don't support all of the
=> options that the real versions do.
=
=What makes you think this?
=
=It's a ``normal'' crunched binary, with no special (and hard to main-
=tain) crippleties applied. Look into /usr/src/release/boot_crunch.conf
=to see how it's being assembled.
So, there are no `cons'?
-mi
--
"Windows for dummies"