Gentoo!

burns · 3 Aug 2004 at 18:31

Originally posted by Mpemba Effect
Pentium II's are i586 I believe (I could be wrong), i686 only started with Penitum III I think. 'dmesg' will problerbly tell you.

Just checked in Scott Muellers Upgrading and Repairing PC's and PIIs are i686 aparently

. I think I'll get one of these ones instead. I guess I want to do rm /mnt/gentoo/*.* first to get rid of the stuff I just downloaded?
//edit, just realised there's no stage1 there anyway. I guess I'll stick with x86 then, any thoughts before I screw up again?

Mpemba Effect · 3 Aug 2004 at 18:35

Originally posted by burns
Just checked in Scott Muellers Upgrading and Repairing PC's and PIIs are i686 aparently. I think I'll get one of these ones instead. I guess I want to do rm /mnt/gentoo/*.* first to get rid of the stuff I just downloaded?

If your're going to compile from stage1 you need the x86 stage. All optimised stages are for stage2 and stage3 only. If you're decide to install from stage1 in the make.conf (like robmiller's upto above) you put in -march=i686 to compile an optimised stage2 yourself.

edit: since you're using a PII you're proberbly better going for a stage2 i686 or even stage3 i686 anyway since it'll take an age to bootstrap, and emerge system

burns · 3 Aug 2004 at 18:40

I think I'm going to stick to stage 1, I wont to see how this is done and I'll just leave it to chug away for as long as it wants.

robmiller · 3 Aug 2004 at 18:46

Righto, updating portage now. I got some crazy errors before that I nailed down to the html of a 404 error page in my make.conf that got there from mirrorselect I guess, but I'll soldier on

burns · 3 Aug 2004 at 19:22

hmm, I'm struggling to get into the environment on my hd. I do

chroot /mnt/gentoo /bin/bash
env-update

and it gives the following errors:

!!!invalid token (not "=") is
!!!ParseError: Invalid token(not "=") /etc/make.conf:7

I'm guessing I got some incorrect syntax in my make.conf, but I can't load vi having done the chroot bit

. Any ideas?

Mpemba Effect · 3 Aug 2004 at 19:26

Originally posted by burns
hmm, I'm struggling to get into the environment on my hd. I do

chroot /mnt/gentoo /bin/bash
env-update

and it gives the following errors:

!!!invalid token (not "=") is
!!!ParseError: Invalid token(not "=") /etc/make.conf:7

I'm guessing I got some incorrect syntax in my make.conf, but I can't load vi having done the chroot bit. Any ideas?

Either use 'nano' to do the editting or type 'exit' to get out of the chroot. You'll then need to do the chroot part again after making your changes.

robmiller · 3 Aug 2004 at 19:26

Originally posted by burns
hmm, I'm struggling to get into the environment on my hd. I do

chroot /mnt/gentoo /bin/bash
env-update

and it gives the following errors:

!!!invalid token (not "=") is
!!!ParseError: Invalid token(not "=") /etc/make.conf:7

I'm guessing I got some incorrect syntax in my make.conf, but I can't load vi having done the chroot bit. Any ideas?

That's what I got. Can you run nano? I had a 404 error page in there

Mpemba Effect · 3 Aug 2004 at 19:27

Oh right in the GENTOO_MIRRORS, in which case delete that mirror.

robmiller · 3 Aug 2004 at 19:29

Emerging system now

Will this take hours?

burns · 3 Aug 2004 at 19:33

Got it, cheers guys

.

Mpemba Effect · 3 Aug 2004 at 19:35

Originally posted by robmiller
Emerging system now

Will this take hours?

Wow! You bootstrapped pretty quick :eek:

emerge system normally takes less time that bootstrapping.

robmiller · 3 Aug 2004 at 19:35

I went for the wuss' way out and went from stage 2 :$

Mpemba Effect · 3 Aug 2004 at 19:37

Oh I see, It should take a couple of hours depending on your machine.

robmiller · 3 Aug 2004 at 19:39

Hmm, it's giving this message;

Resolving groff.ffii.org [ip addrss] failed: connection refused
!!! Couldn't download groff-1.18.1.tar.gz

What's groff, and do I need it?

Mpemba Effect · 3 Aug 2004 at 19:50

Yes you need groff, try emerging system again may be it can pickit up from a mirror

Mpemba Effect · 3 Aug 2004 at 19:55

OK press ctrl-c to break out of emerge system if it hasn't timed out or given you the connection refused error the do

Code:

cd /usr/portage/distfile
wget [url]http://mirrors.sunsite.dk/gnu/groff/groff-1.18.1.tar.gz[/url]
emerge system

robmiller · 3 Aug 2004 at 19:57

Code:
Originally posted by Mpemba Effect
OK press ctrl-c to break out of emerge system if it hasn't timed out or given you the connection refused error the do

Code:

cd /usr/portage/distfile wget [url]http://mirrors.sunsite.dk/gnu/groff/groff-1.18.1.tar.gz[/url] emerge system

There isn't a dir called "distfile", but there is "distfiles", is that the one?

Mpemba Effect · 3 Aug 2004 at 19:58

Originally posted by robmiller
There isn't a dir called "distfile", but there is "distfiles", is that the one?

Thats the one

robmiller · 3 Aug 2004 at 19:59

Okie doke, wget'ing now.

So it stores the downloaded packages in /usr/portage/distfiles when you update portage?

Mpemba Effect · 3 Aug 2004 at 20:01

No the portage tree is held in /usr/portage and when you update portage it just updates all the ebullds in /usr/portage. When you install something via emerge the source files are held in /usr/portage/distfiles (just in case you need to compile them again you don't need to redownload). During the install process the source files will be unpacked, patched etc in /var/tmp/portage.

So every now and again it's a good idea to clean out whats in /usr/portage/distfiles and /var/tmp/portage. /var/tmp/portage can get filled quickly with compiling 'junk' if you break out of mid emerge (like you've just done) since those temporary files are not 'cleaned' afterwards. SO every now ans again remove the contents of /vat/tmp/portage