Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:2141 comp.os.linux.misc:11891
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!vixen.cso.uiuc.edu!newsrelay.iastate.edu!news.iastate.edu!ponderous.cc.iastate.edu!michaelv
From: michaelv@iastate.edu (Michael L. VanLoon)
Newsgroups: comp.os.386bsd.misc,comp.os.linux.misc
Subject: Re: Impressions: FreeBSD vs Linux
Date: 29 Mar 94 05:02:37 GMT
Organization: Iowa State University, Ames, Iowa
Lines: 61
Message-ID: <michaelv.764917357@ponderous.cc.iastate.edu>
References: <CMzw69.92K@tower.nullnet.fi> <Cn1KJ1.9pr@boulder.parcplace.com> <HJSTEIN.94Mar24111940@sunset.huji.ac.il> <1994Mar28.123516.20304@uk.ac.swan.pyr>
NNTP-Posting-Host: ponderous.cc.iastate.edu
In <1994Mar28.123516.20304@uk.ac.swan.pyr> iiitac@uk.ac.swan.pyr (Alan Cox) writes:
>In article <HJSTEIN.94Mar24111940@sunset.huji.ac.il> hjstein@sunset.huji.ac.il (Harvey J. Stein) writes:
>>In article <Cn1KJ1.9pr@boulder.parcplace.com>
>>imp@boulder.parcplace.com (Warner Losh) writes:
>> >What do people mean with this (`looks and feels like a beta/not finished')?
>> >What in Linux makes that unfinished look'n'feel?
>> From my point of view it is the building of a system. On FreeBSD, all
>> I type is "make world," then go out for the night. When I come back,
>> all my user level utilities have been build and installed (in addition
>> to libraries, include files, etc). For Linux I must have missed
>> something because I've never seen a source distribution I could do
>> this with (feel free to prove me wrong). This is due, I think, to the
>> fact that there is exactly one core distribution and an central group
>> running the show that is responsible (as a group) for the entire
>> system.
>>I believe that the TAMU distribution allows this.
>Out of curiosity I got the README entries for all the packages on my machine
>and the size of source + build space. To make world my entire system I'd
>need 4.6Gb of disk space, or 3.1Gb assuming I did a make clean on each
>package after building. Whoopee... There are good reasons for binary
>releases at time.
The *operating system* is what we're discussing. Not every known
piece of fluff utility someone in some remote corner of the world
thinks would be neato to have. Last time I estimated with
NetBSD-current, the operating system source (kernel, /bin, /sbin,
/usr/bin, /usr/sbin, /usr/libexec, and /usr/lib, plus the things in
/usr/include and /usr/share) took roughly 90 meg to keep around. The
object directory tree (everything resulting from the build process)
took another 40-50 meg (this is just the object tree, not counting the
disk space taken up by the installed binaries). Hardly an unmanagable
amount.
My own source tree of favorite things I've ported/compiled myself
takes up another unrelated chunk of disk real-estate.
>On the other hand I do wish the slackware_src was layed out better and
>unpacked as /usr/src/<binarypathname>/* for each thing, but I don't have
>the time sort that out and I'm sure Patrick has far more useful things to
>do with his life...
It is very nice. Especially when dealing with multiple architectures.
Having one unified source tree that can be made to automagically build
for several different architectures into architecture-specific object
subtrees without any conflice is not only nice, but essential in even
a medium-sized operation. The uniformity and organization is quite
nice to work with.
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Michael L. VanLoon Iowa State University Computation Center
michaelv@iastate.edu Project Vincent Systems Staff
Free your mind and your machine -- NetBSD free Un*x for PC/Mac/Amiga/etc.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -