From: Thomas Flavel <thomasfl@cogs.susx.ac.uk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] odds and ends
Date: Wed Jan 24 16:35:02 2001 [thread overview]
Message-ID: <20010124233516.E29166@tsuny.ctn.cogs.susx.ac.uk> (raw)
In-Reply-To: <20010124160851.D3615@cvs.gentoo.org>; from drobbins@gentoo.org on Wed, Jan 24, 2001 at 04:08:51PM -0700
On Wed, Jan 24, 2001 at 04:08:51PM -0700, drobbins@gentoo.org wrote:
> On Wed, Jan 24, 2001 at 10:43:53PM +0000, Thomas Flavel wrote:
> > > 1.0_rc4-pre2 is fully compatible with all modern Intel and Intel-compatible
> > > processors, from the i486 on up. While 1.0_rc4-pre2 is optimized for the
> > > 486, Achim plans to build several different versions of 1.0_rc4 optimized for
> > > various processors. 1.0_rc4-pre2 has been tested on K6 systems and works
> >
> > I don't understand why not a 386? I kind of expected the distcd to be 386
> > binaries, and then to compile and install optimised to whatever my processor
> > happens to be? What am I mis-understanding? ;)
> >
> > How would gentoo be installed on a 386?
>
> Very slowly. 386's and bzip2-compressed packages don't exactly get along :)
:) Is it feasible to have two alternate install routes; one compiling from scratch
and the other pre-compiled?
> If there's a need, we can create a 386-compatible build.
I'm just thinking along the lines of a minimum binary system where absolutley
needed, and compiling specifically everywhere else? I realise this would be
slow to install on slower systems, but, since we're all power users... ;)
Seriously though, I do think this would be a nice feature, unless there's some
practicality reason I'm missing.
> > Excellent. Roughly what size is minimum now?
>
> Do you mean the minimum HD space needed for installation? I'd guess about 400Mb
> of HD space. We haven't specifically attempted to "squeeze" the base install
> into a minimum of space. If we did, we could probably get it to live in around
> 250Mb, maybe less. If we started recompiling packages and linking them to a tiny
> libc, we might be able to get this down to <100Mb :) But, since we're all power
> users, this isn't something that we're focusing on right now.
Ok
- Tom
next prev parent reply other threads:[~2001-01-24 23:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 15:30 [gentoo-dev] odds and ends drobbins
2001-01-24 15:44 ` Thomas Flavel
2001-01-24 16:09 ` drobbins
2001-01-24 16:35 ` Thomas Flavel [this message]
2001-01-24 16:39 ` drobbins
2001-01-24 16:38 ` Achim Gottinger
2001-01-24 16:44 ` Thomas Flavel
2001-01-24 16:44 ` drobbins
2001-01-24 17:01 ` Achim Gottinger
[not found] <20010124234502.7F94151359@cvs.gentoo.org>
2001-01-25 3:27 ` Robert Schrem
2001-01-25 6:04 ` Achim Gottinger
2001-01-25 6:34 ` Gabriel
2001-01-25 7:25 ` Achim Gottinger
2001-01-25 7:52 ` mats pettersson
2001-01-25 9:48 ` drobbins
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=20010124233516.E29166@tsuny.ctn.cogs.susx.ac.uk \
--to=thomasfl@cogs.susx.ac.uk \
--cc=gentoo-dev@gentoo.org \
/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