From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] i have an idea ! (erescue)
Date: Tue, 17 May 2005 12:51:40 -0400 [thread overview]
Message-ID: <1116348700.14290.32.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <1116290915.10849.8.camel@TesterBox.tester.ca>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Mon, 2005-05-16 at 20:48 -0400, Olivier Crête wrote:
> I would tend to believe that the content of a stage1 or stage2 would be
> enough and just for the majors architectures (those that have a
> stage1).. Anyways people will rebuild said packages once that's done,
> right? That's not much for the mirrors.. Around 168 megs for the content
> of a stage1 or 300 megs for the stage2..
Honestly, a stage1 is not a good starting point. In fact, there should
*never* be anything provided that is directly laid onto the live
filesystem.
A much better approach would be for there to be a rescue build,
completely independent of the stages, since it doesn't need to mirror
them in any way. It should be extracted (self-extracted?) to something
like /rescue and executed from there, being completely self-contained.
This keeps it from stomping on system files and breaking
collision-protect or doing anything else nasty like hosing configuration
files (ever made the mistake of extracting a stage onto a live
filesystem?) when unpacked.
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-17 16:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 21:18 [gentoo-dev] i have an idea ! (erescue) Mike Frysinger
2005-05-15 21:19 ` Tom Wesley
2005-05-15 21:21 ` Henrik Brix Andersen
2005-05-15 21:24 ` Carlos Silva
2005-05-16 13:44 ` Chris Gianelloni
2005-05-15 21:29 ` Krzysiek Pawlik
2005-05-15 22:32 ` Donnie Berkholz
2005-05-15 22:45 ` Krzysiek Pawlik
2005-05-15 22:48 ` Ryan
2005-05-15 23:29 ` Sami Samhuri
2005-05-15 23:41 ` david stanek
2005-05-16 0:22 ` Mike Frysinger
2005-05-16 1:12 ` John Myers
2005-05-16 1:56 ` David Stanek
2005-05-16 2:24 ` David Stanek
2005-05-16 10:24 ` [gentoo-dev] " Duncan
2005-05-16 11:20 ` Jan Kundrát
2005-05-16 13:38 ` [gentoo-dev] " Duncan
2005-05-16 13:48 ` Jan Kundrát
2005-05-16 11:33 ` [gentoo-dev] " Thomas de Grenier de Latour
2005-05-16 13:48 ` [gentoo-dev] " Duncan
2005-05-15 21:31 ` [gentoo-dev] " Olivier Crête
2005-05-16 13:57 ` Chris Gianelloni
2005-05-16 22:11 ` Pete Ezzo
2005-05-17 0:48 ` Olivier Crête
2005-05-17 16:51 ` Chris Gianelloni [this message]
2005-05-17 17:33 ` Donnie Berkholz
2005-05-17 17:51 ` Chris Gianelloni
2005-05-24 21:11 ` [gentoo-dev] i have an idea ! (erescue) ro-overlays Jim Northrup
2005-05-24 21:48 ` Mike Frysinger
2005-05-24 22:34 ` Jim Northrup
2005-05-24 22:40 ` Mike Frysinger
2005-05-24 23:44 ` Stuart Longland
2005-05-25 13:32 ` Chris Gianelloni
2005-05-25 16:50 ` James Northrup
2005-05-16 4:07 ` [gentoo-dev] i have an idea ! (erescue) Sami Samhuri
2005-05-16 4:29 ` David Stanek
2005-05-16 7:09 ` Colin Kingsley
2005-05-16 8:48 ` Chris Bainbridge
2005-05-18 7:07 ` [gentoo-dev] " R Hill
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=1116348700.14290.32.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@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