From: Nathaniel Grady <nate@nutopia.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Boot failure
Date: Wed Oct 31 12:31:02 2001 [thread overview]
Message-ID: <20011031143039.A28413@nutopia.org> (raw)
In-Reply-To: <20011031100323.J10122@cvs.gentoo.org>; from drobbins@gentoo.org on Wed, Oct 31, 2001 at 10:03:23AM -0700
While I havn't done this since 1.0RC5 I believe it should still work ok. Try using a current slackware boot/root disk set - if memory serves they have support for reiserfs. Boot from the boot/root disks as usual, use fdisk to create a partition, format it, mount it, then extract the build tbz file onto that partition, then mount /proc /newpartition/proc -o bind and chroot /newpartition and you should be set... To get the tbz you may want to use the "network" root disk so you can access NFS or else i believe ftp was on the "color" root disk.
My method now is to have 2 partitions and just cycle back and forth. Install gentoo (or some other linux) on one partition, format the other partition, extract the latest gentoo build tarball onto that partition, mount proc on the new system and chroot to it. From there it's the same as off a cd ('cept you may want to mount the original partition under /mnt/oldgentoo and copy files from /etc/ rather than recreating them - but watch out for changes to the rc system and such if you do that). When you're ready to upgrade again you do the same thing with the partitions reversed. This has the distinct advantage that you *always* have a working system at any given point - you don't destroy the old system untill you're absolutly shure the new one works (or not at all if you have disk space to burn... I actually keep my mp3's on which ever partition i'm not using them and offload them to another computer during the upgrade since i can live w/o them). Very important if you screw someting up and have to write a paper then next day... <sarcasm>not that there is a reason I descided to follow this approach or anyting - d'oh</sarcasm>
hope I'm not forgetting someting important here :)
Good luck!
--Nate Grady
On Wed, Oct 31, 2001 at 10:03:23AM -0700, Daniel Robbins wrote:
> On Wed, Oct 31, 2001 at 11:17:21AM +0100, Rychlik, Michael wrote:
> > Hi,
> >
> > I cannot boot build-ix86-1.0_rc6_r10.iso it crashes my machine while
> > decompressing rescue.gz after a line or so of dots is displayed. The box in
> > question is an AMD K6/266 in an ASUS P5A mobo. Award BIOS 4.5x. Voodoo 3 and
> > NE2000. 96Mb od RAM.
> >
> > The same CD boots fine elsewhere.
> >
> > Is it still possible to build from floppy ?
>
> We don't have a floppy boot/build method yet. I'm guessing that this is related
> to your BIOS, since there have been other Award BIOS problems (4.51). But Award
> probs were supposed to be fixed in the latest isolinux release. You may try
> updating your BIOS if possible.
>
> Best Regards,
>
> --
> Daniel Robbins <drobbins@gentoo.org>
> Chief Architect/President http://www.gentoo.org
> Gentoo Technologies, Inc.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2001-10-31 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3192224256F2D21187C70008C73C87A81162E9@email>
2001-10-31 10:04 ` [gentoo-dev] Boot failure Daniel Robbins
2001-10-31 12:31 ` Nathaniel Grady [this message]
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=20011031143039.A28413@nutopia.org \
--to=nate@nutopia.org \
--cc=gentoo-dev@cvs.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