Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: "K." <conradp@cse.unsw.edu.au>, linux@cthulhu.engr.sgi.com
Subject: Re: crtbegin.o, crtend.o
Date: Tue, 13 Jan 1998 02:36:59 +0100	[thread overview]
Message-ID: <19980113023659.28414@uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.3.95.980112121719.6175A-100000@lager.engsoc.carleton.ca>; from Alex deVries on Mon, Jan 12, 1998 at 12:18:47PM -0500

On Mon, Jan 12, 1998 at 12:18:47PM -0500, Alex deVries wrote:

> On Mon, 12 Jan 1998 ralf@uni-koblenz.de wrote:
> > Upgrade your system with all the rpm packages.  root-0.01 was my first
> > collection of Indy executables and basically_every_ ELF file has bugs in
> > it ...
> 
> On that note, I should probably get around to creating root-0.02 which has
> all the 'new' binaries in it...  are there any more files than the ones in
> root-0.01 I should add?

Actually I'm thinking about the opposite.  root-0.02.tar.gz was a quite
fat tarball, I think it was about 20mb.  I received some complaints about
it.  If you're going to build a new root-0.2 filesystem, then it should
be stripped down to an absolute minimum that is necessary to allow the
installation of further rpms, partitioning, mounting and more.  Having
gcc in the tarball is overkill and makes maintenance a pain.

  Ralf

  reply	other threads:[~1998-01-13  1:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-12  5:23 crtbegin.o, crtend.o K.
1998-01-12  8:58 ` ralf
1998-01-12 17:18   ` Alex deVries
1998-01-13  1:36     ` ralf [this message]
1998-01-13  3:24       ` Alex deVries
1998-01-12 18:56   ` Thomas Bogendoerfer
1998-01-13  2:36     ` ralf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19980113023659.28414@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=adevries@engsoc.carleton.ca \
    --cc=conradp@cse.unsw.edu.au \
    --cc=linux@cthulhu.engr.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox