home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!news.claremont.edu!jarthur.claremont.edu!jwinstea
- From: jwinstea@jarthur.claremont.edu (Jim Winstead Jr.)
- Subject: Re: root disk vs. mj disk, also hd.c patch
- Message-ID: <1992Aug12.184959.20152@muddcs.claremont.edu>
- Sender: news@muddcs.claremont.edu (The News System)
- Organization: Harvey Mudd College, WIBSTR
- References: <1992Aug12.011334.17155@ultb.isc.rit.edu>
- Date: Wed, 12 Aug 1992 18:49:59 GMT
- Lines: 24
-
- In article <1992Aug12.011334.17155@ultb.isc.rit.edu> axi0349@ultb.isc.rit.edu (A.X. Ivasyuk ) writes:
- >First of all, how do you get the executables to be so tiny on the root disk
- >and the mj distribution? I can't get mine under 9K, even a 'hello, world'
- >program. I'd like to be able to squeeze my 80MB drive to the max.
- >It can't be just the -O flag on gcc.
-
- Use both the '-N' and '-s' flags to the linking stage. -N creates an
- 'impure' executable, which can't be demand-paged. -s strips the
- symbol information from the compiled file.
-
- >Second, why the large difference in file size between some of the binaries
- >on the 'official' root disk and the mj disk? Are they different versions?
- >Provide extra features?
-
- It's possible they're different versions of the same package, or
- completely different versions of the same type of software. A good
- example is 'tar' - on the 0.97 (and 0.96) root, tar is simply a
- symlink to pax, the Posix standard archiver. On the MJ releases, tar
- has been GNU tar.
- --
- + Jim Winstead Jr. (CSci '95)
- | Harvey Mudd College
- | jwinstea@jarthur.Claremont.EDU
- + This is all my words. Honest!
-