public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: kashani <kashani-list@badapple.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is Gentoo still on the right path?
Date: Wed, 16 Nov 2005 14:30:28 -0600	[thread overview]
Message-ID: <437B96E4.5030507@badapple.net> (raw)
In-Reply-To: <20051117090935.27DE.NICK@rout.co.nz>

Nick Rout wrote:
> I read your message and was surprised at this. Last time I read the 
> handbooks the Handbook gave stage 1/2/3 options and the 2005.1
> handbook stuck to stage 3.  (Talking x86 here, I have never done an
> instal on other architectures).
> 
> Now, like you, I read this in the Handbook:
> 
> "Make sure you download a stage3 tarball - installations using a
> stage1 or stage2 tarball are not supported anymore."
> 
> WTF? When did this happen?
> 

About a week or two ago and was heavily discussed on gentoo-doc IIRC. 
Here's a rough summary.

stage1 is the cause of a number of circular dependency issues, it takes 
forever, the engineering and release team spends too much time on it, 
and the average Gentoo users get no benefit from doing a stage1 over a 
stage3. In order to get any benefit from stage1 you must edit the boot 
strap scripts in some way. Editting the boot strap scripts is not 
documented and not something general users should be mucking around in 
so we're going to drop everything, but stage3 on the CD.

Or at least that was my interpretation. I stopped paying attention 
around this point, but there was talk of keeping a stage1 for devs or 
people who need it... though I don't think exactly what or where was 
ever fully hashed out.

kashani
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-11-16 20:42 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 16:20 [gentoo-user] Is Gentoo still on the right path? Derek Tracy
2005-11-16 18:23 ` Mark Knecht
2005-11-19 15:07   ` A. Khattri
2005-11-16 19:53 ` Daniel da Veiga
2005-11-16 20:50   ` Derek Tracy
2005-11-16 21:50     ` Jeff Smelser
2005-11-16 22:32       ` Derek Tracy
2005-11-17  0:26         ` Richard Fish
2005-11-16 22:46     ` Neil Bothwick
2005-11-17 11:24       ` Derek Tracy
2005-11-17 11:59         ` Nagatoro
2005-11-17  7:44   ` jarmstrong
2005-11-16 22:51     ` Neil Bothwick
2005-11-17  3:03       ` Mark Knecht
2005-11-17  9:23         ` Neil Bothwick
2005-11-17 13:52           ` Allan Gottlieb
2005-11-17 14:35             ` Neil Bothwick
2005-11-17 17:44               ` Allan Gottlieb
2005-11-17 15:21           ` Mark Knecht
2005-11-17  0:17     ` Ciaran McCreesh
2005-11-17  0:34       ` Richard Fish
2005-11-16 20:12 ` Nick Rout
2005-11-16 20:30   ` kashani [this message]
2005-11-16 21:04     ` Nick Rout
2005-11-16 20:30   ` Benjamin Martin
2005-11-16 20:47     ` Mark Knecht
2005-11-16 20:55       ` Benjamin Martin
2005-11-16 20:59         ` Derek Tracy
2005-11-16 21:10         ` Mark Knecht
2005-11-16 21:20           ` Derek Tracy
2005-11-16 22:31             ` Richard Fish
2005-11-16 23:24             ` kashani
2005-11-16 21:33           ` Manuel McLure
2005-11-16 21:53         ` Jeff Smelser
2005-11-16 20:54   ` Zac Medico
2005-11-16 22:22 ` Richard Fish
2005-11-16 22:37   ` Derek Tracy
2005-11-17  0:21     ` Richard Fish
2005-11-17 14:03 ` Bill Roberts
  -- strict thread matches above, loose matches on Subject: below --
2005-11-16 20:27 Budd, Tracy

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=437B96E4.5030507@badapple.net \
    --to=kashani-list@badapple.net \
    --cc=gentoo-user@lists.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