| View previous topic :: View next topic |
| Author |
Message |
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
 Posted: Fri Mar 03, 2006 9:41 pm Post subject: [OUTDATED] The Evolution Mission Install Guide 1.0 |
 |
|
If you are currently installing, continue to do so, and check the newest thread at http://forums.gentoo.org/viewtopic-p-3180417.html for the upgrade guide soon.
From the man that brought you Nesl247's Conrad Install Guide, the Evolution Mission proudly presents...
The Evolution Mission Install Guide 1.0.2 Codename: "A New Beginning
-----
Forewarning
This guide uses packages (including ones in the toolchain which are the vital packages in Gentoo) that maybe in development. Please understand that we do not guarantee a bug-free system without a little bit of patience and work.
-----
A somewhat bleeding edge system including the following:
GCC 4.1, Glibc 2.4 snapshots, optimized LDFLAGs, C[XX]FLAGs, and more.
------
FAQ
(Q) This is insane. Why would I bother to use such a system and how usable would it be?
(A) Why would you bother, you ask? Well it is really up to you. I recommend this guide because it uses
software that will be released in the near future, so you are insuring that you have the latest and greatest.
-----
Toolchain Links
Glibc 2.3.91 (Updated Regularly)
GCC 4.1 [Beta]
------
IRC Channel
Join - #evo-mission on irc.freenode.net
-----
Notice:
Evolution Mission Install Guide is not supported in any way, shape, or form by the Gentoo Linux Foundation. Thus do not post bugs to Gentoo.
-----
Updates:
-----
The Evolution Mission Team
{Project Manager} Nesl247
{IRC Manager} - djpharoah
-----
Notes: We will assume that x in hdx is the drive letter throughout this guide.
1 - The LiveCD
1.1 - First of all, we are going to download the latest Gentoo Livecd If you do not wish to use this livcd or already have a working distribution in which to install from please skip this step.
| Code: | http://bouncer.gentoo.org/?product=gentoo-2006.0-livecd&os=x86 Contains X.org (Graphical)
http://bouncer.gentoo.org/?product=gentoo-2006.0-minimal&os=x86 Old Style Minimal CD |
1.2 - Burn it to a CD and boot it
If you do not know how to boot the disc I suggest that you do not use this guide.
2 -Preparing the Network
2.1 Checking for connection
If the following does not work, then do the steps after it.
| Code: | # ping google.com
# net-setup eth0 |
3 - Hard disk configuration
3.1 - View the hard disk configuration
| Code: | | # hdparm -i /dev/hdx |
3.2 - Test the Hard Disk's speed
| Code: | | hdparm -tT /dev/hdx |
3.3 - Get the maximum from your hard disk - Optional
I only recommend this option for ATA133 hard drives, not anything lower.
| Code: | (IDE ATA133 drives only)
hdparm -d1 -c1 -X69 /dev/hdx
(IDE ATA100 or lower drives)
hdparm -d1 -c1 /dev/hdx |
4 - Partitioning the Drive
4.1 Using Fdisk
Remember that once you have the partition layout, you need to set the type to 82 (A.K.A Linux Swap) for the swap partition. Once you have it setup correctly, hit w to write and exit.
| Code: | # fdisk /dev/hdx
Command (m for help): p
Disk /dev/hdx: xxx heads, xx sectors, xxxx cylinders
Units = cylinders of xxxxx * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdx1 1 14 158760 83 Linux # boot about 100 MB
/dev/hdx2 15 49 264600 82 Linux swap # swap about 512 MB
/dev/hdx3 50 70 remainder 83 Linux # root remainder of space
|
4.2 - Creating your partitons
| Code: | # mkfs.ext3 /dev/hdx3
# mkfs.ext2 /dev/hdx1
# mkswap /dev/hdx2
# swapon /dev/hdx2 |
4.3 Optimizing /root partition
| Code: | | # tune2fs -O dir_index /dev/hdx3 |
4.4 - Mounting your hard drives
| Code: | # mount /dev/hdx3 /mnt/gentoo
# mkdir /mnt/gentoo/proc /mnt/gentoo/boot
# mount -t proc none /mnt/gentoo/proc
# mount /dev/hdx1 /mnt/gentoo/boot |
5 - Setting up for a chroot
5.1 - Downloading and extracting a stage3 tarball
| Code: | # cd /mnt/gentoo
# wget http://gentoo.osuosl.org/releases/x86/2006.0/stages/stage3-i686-2006.0.tar.bz2
# tar -jxvpf stage3-i686-2006.0.tar.bz2 |
5.2 - Downloading and extracting a portage snapshot
| Code: | # wget http://distfiles.gentoo.org/snapshots/portage-latest.tar.bz2
# tar jxvpf portage-latest.tar.bz2 -C /mnt/gentoo/usr/ |
5.3 - Copying resolv.conf
| Code: | | # cp /etc/resolv.conf /mnt/gentoo/etc/ |
6 - Chrooting and preparing the environment
6.1 - Chrooting
| Code: | # chroot /mnt/gentoo /bin/bash
# env-update; source /etc/profile |
6.2 Updating the portage tree
6.3 - Setting the timezone
Change according to your zone
| Code: | # rm -rf /etc/localtime
# ln -s /usr/share/zoneinfo/US/Eastern /etc/localtime |
7 Building & Rebuilding System with GCC 4.1
7.1 - Downloading the root overlay
If you already have a /boot/grub/grub.conf, I suggest you make a backup as this will overwrite it.
| Code: | # cd /
# wget http://h1.ripway.com/evomission/root-overlay.tar.bz2
# tar -jxvpf root-overlay.tar.bz2
# rm root-overlay.tar.bz2 |
7.2 Updating /etc/make.conf
Replace $ARCH with one of the following:
i686, pentium3, pentium4, athlon-xp, athlon64 (aka k8)
| Code: | | # nano -w /etc/make.conf |
7.3 -Setting /etc/locales.build - Optional
You have to set this according to your region, area, and language
This is completely optional, it just saves build time
| Code: | | # nano -w /etc/locales.build |
Example file:
| Code: | # This file names the list of locales to be built when glibc is installed.
# The format is <locale>/<charmap>, where <locale> is a locale from the
# /usr/share/i18n/locales directory, and <charmap> is name of one of the files
# in /usr/share/i18n/charmaps/. All blank lines and lines starting with # are
# ignored. Here is an example:
# en_US/ISO-8859-1
en_US/ISO-8859-1
en_US.UTF-8/UTF-8 |
7.4 - Building the toolkit and upgrading portage
| Code: | # emerge glibc binutils gcc libstdc++-v3 libtool portage
# emerge --metadata
# emerge ccache confcache |
7.5 - Running gcc-config, and binutils-config
| Code: | # gcc-config 6
# binutils-config 2
# env-update; source /etc/profile
# emerge -aP gcc binutils |
7.6 - Updating /etc/portage to new layout
| Code: | # rm -r /etc/portage
# mv /etc/portage.2.1 /etc/portage |
7.7 Uncommenting LDFLAGS
Remove the '#' infront of 'LDFLAGS'
| Code: | | # nano -w /etc/make.conf |
7.8 - Rebuilding the toolkit
| Code: | | # emerge glibc binutils gcc libstdc++-v3 libtool portage |
7.9 - Rebuilding the System
| Code: | | # emerge --emptytree world |
8 Configuring the kernel
8.1 Emerging Archck-Sources
| Code: | | # emerge archck-sources |
8.3 - Configuring and Compiling the kernel
-----
I can only help you out so much, what I can do is tell you how to get started, and what is required.
| Code: | # cd /usr/src/linux
# make menuconfig |
| Code: | Required Options...
Code maturity level options --->
[*] Prompt for development and/or incomplete code/drivers
General setup --->
[*] Support for hot-pluggable devices
Loadable Module Support --->
[*] Module unloading support
Processor type and features --->
[*] Standard x86 support
(Change accordingly)
(Your Processor Family) Processor family
[*] Symmetric multi-processing support
# If you have exactly 1GB of memory use the following else just leave it at default.
Memory Split (3G/1G user/kernel split (for full 1GB Low memory)) ---->
File systems --->
Pseudo Filesystems --->
[*] /proc file system support
[*] Virtual memory file system support (former shm fs)
<*> Ext3 journalling file system support
<*> Second extended fs support
Device Drivers --->
ATA/ATAPI/MFM/RLL support --->
[*] Generic PCI bus-master DMA support
[*] Use PCI DMA by default when available
Device Drivers --->
Networking support --->
<*> PPP (point-to-point protocol) support
<*> PPP support for async serial ports
<*> PPP support for sync tty ports
100 MBIT/1000 MBIT --->
(make sure you compile in your proper network driver
Sound --->
[M] Sound card support
Alsa --->
PCI Cards --->
[M] Your Driver, mine is intel8x0, a common one is emu10k1 for soundblaster cards
USB Support --->
<*> USB Human Interface Device (full HID) support
Device Drivers > Graphics support:
[*] Support for frame buffer devices
<*> VESA VGA graphics support
VESA driver type (vesafb-tng) --->
(HRESxVRES@FREQ) VESA default mode # Pick your resolution - eg. 1024x768@84
Device Drivers > Graphics support > Console display driver support:
[*] Video mode selection support
<*> Framebuffer Console support
Device Drivers > Graphics support:
[*] Support for the framebuffer splash
Device Drivers > Block devices:
<*> RAM disk support
(4096) Default RAM disk size (kbytes) (NEW)
[*] Initial RAM disk (initrd) support |
8.4 - Compiling the Kernel
| Code: | | # make && make modules_install && cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.15-archck && cp .config /boot/config-2.6.15-archck |
8.5 - Emerging Grub
The E-Mission Install Guide does not support installing on a root partition. Please install to the MBR.
Windows users, your partition layout might look like this, 1-windows, 2-swap, 3-root, 4-boot
9 - Emerging additional system files
9.1 - Emerging necessary programs
Here we emerge reiser4progs for the purpose of being able to use reiser4 in the future.
| Code: | | # emerge syslog-ng reiserfsprogs sysfsutils dhcpcd coldplug gentoolkit acpid gentoolkit-dev slocate vixie-cron app-admin/sudo subversion |
9.2 - Adding the programs to the default runlevel
| Code: | # rc-update add syslog-ng default
# rc-update add net.eth0 default
# rc-update add coldplug default
# rc-update add acpid default
# rc-update add vixie-cron default
# rc-update add hdparm default
# rc-update del netmount |
10 - Setting up the framebuffer splash
If you followed the kernel compile options, you should have everything required
10.1 - Emerging splashutils and a few themes
| Code: | # emerge splashutils splash-themes-livecd
# rc-update add splash default |
10.2 Linking the splash theme to default
| Code: | | # ln -s /etc/splash/livecd-2006.0 /etc/splash/default |
10.3 - Generating an initrd image
Please select your resolution here. If you do not want 1024x768 then replace it with what you would normally run an X server in.
| Code: | # cd /etc/splash
# splash_geninitramfs -v -g /boot/fbsplash-default -r 1024x768 default |
11 - Setting up grub
11.1 Modifying /boot/grub/grub.conf
In grub, Y in hdxY is the partition number minus 1 (hdx1 is hd0,0) and so forth.
| Code: | | nano -w /boot/grub/grub.conf |
11.2 - Running grub for installation to MBR
| Code: | # grub
<grub:> root (hdx,Y) # boot partition
# (hdx) is the MBR of the drive.
<grub:> setup (hdx)
<grub:> quit |
12 - Configuring your system
12.1 - Updating conf files
It is safe to replace all files, so -5 is ok, but -1 recommended.
12.2 - Editing configuration files
Replace hdx with the correct drive letter.
| Code: | | # nano -w /etc/conf.d/hdparm |
12.3 - Set your hostname and domainname
| Code: | # nano /etc/conf.d/hostname
HOSTNAME="emission-gentoo" |
| Code: | # nano -w /etc/hosts
127.0.0.1 emission-gentoo localhost |
If you don't understand these 2 files, leave them alone.
| Code: | # nano -w /etc/conf.d/domainname
# DNSDOMAIN=""
# NISDOMAIN="" |
12.4 - Editing the /etc/conf.d/net
(Not necessary for dhcp users.)
| Code: | # nano -w /etc/conf.d/net
For possible lines, visit the Configuring the Network section in the Gentoo Handbook Here
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=8#doc_chap2 |
12.5 - Configuring FSTAB
12.6 - Setting up users
First set the root password
| Code: | # passwd
<enter new password>
<confirm new password> |
Then set up a user
| Code: | # useradd -m -G users,wheel,audio username
# passwd username
<set username's password>
<confirm username's password> |
13 - Rebooting and Booting!
13.1 Unmounting and Rebooting
| Code: | # exit
# umount /mnt/gentoo/boot /mnt/gentoo/proc /mnt/gentoo
# reboot |
13.2 - Booting the system
Find yourself at a grub menu, and boot into your system
If you get a kernel panic then check to make sure you configured everything properly by booting back into the livecd and mounting the partititions, etc.
14 - Other Configuration
14.1 USE Variables
| Code: | | # nano -w /usr/portage/profiles/use.desc |
There are tons of user variables, by x86 the following are used by default
| Code: | USE="x86 oss apm arts avi berkdb crypt cups encode foomaticdb gdbm gif gpm gtk gtk2 imlib jpeg kde gnome libg++
libwww mad mikmod motif mpeg ncurses nls oggvorbis opengl pam pdflib png python qt quicktime readline sdl
slang spell ssl svga tcpd truetype X xml2 xmms xv zlib indent" |
14.2 - Setting USE Flags
There are tons of use flags to choose from, personally, I like a gnome/gtk2/opengl/nvidia system, here is how I will set my use flags.
If you are using gnome, you must include gtk2 gnome gstreamer gstreamer010
| Code: | # nano -w /etc/make.conf
USE="nptl nptlonly glibc-omitfp alsa X gtk2 gnome -qt -kde -arts win32codecs nvidia opengl gstreamer gstreamer010" |
For more In-Depth configuration information, consult the Gentoo Handbook
15 - Installing Xorg-X11 and a graphical environment
15.1 Select a video card, and input device
Replace $CARD with the appropriate driver and uncomment VIDEO_CARDS. Since this is an advanced install guide, you should know what to put. Also if you need evdev or any other input device add that to the input_devices variable. If you leave these alone (remove $CARD if you don't know) then you will get all drivers.
| Code: | # nano -w /etc/make.conf
INPUT_DEVICES=keyboard mouse
VIDEO_CARDS=$CARD |
15.2 - Emerging Xorg
| Code: | # emerge --oneshot openmotif imake makedepend gccmakedep
# emerge xorg-x11 |
15.3 - Getting an xorg.conf setup
You should be able to do this on your own.
15.4 - Installing GNOME or KDE
Gnome:
If this fails, then continue on by doing the emerge command starting with gnome-vfs
| Code: | | # emerge gamin gnome gnome-audio |
| Code: | # emerge --oneshot --nodeps gnome-vfs
# emerge --oneshot --nodeps libgnome
# emerge --oneshot --nodeps libbonoboui
# emerge --oneshot --nodeps libgnomeui
# emerge gamin gnome gnome-audio |
KDE:
| Code: | (monolithic)
# emerge kde
(meta)
# emerge kde-meta |
15.5- Additional configuration
| Code: | # nano -w /etc/rc.conf
DISPLAYMANAGER="xdm" |
| Code: | | # rc-update add xdm default |
15.6 - Graphics Drivers
If you have 3D acceleration on your card, you may want to, and should install the Nvidia or ATI Drivers.
Gentoo NVIDIA Guide: http://www.gentoo.org/doc/en/nvidia-guide.xml
Gentoo-Wiki ATI Guide: http://gentoo-wiki.com/HOWTO_ATI_Drivers
16 Setting up ivman
Replce USERNAME with the name of your users you want to be able to automount with
If adding the username other than ivman is not needed, someone say so.
| Code: | # emerge ivman
# rc-update add dbus default
# rc-update add hald default
# rc-update add ivman default
# gpasswd -a USERNAME plugdev
# gpasswd -a ivman plugdev |
17 - Configuring ALSA
For more information you may want to visit the Gentoo Linux Alsa Guide.
Gentoo Alsa Guide: http://www.gentoo.org/doc/en/alsa-guide.xml
17.1 - Emerging alsa packages
| Code: | | # emerge alsa-utils alsa-oss |
17.2 - Running alsaconf
17.3 - Editing Additional Files
Find near the botton snd-***, and sound-***
change *** to your sound card name, for example:
snd-intel8x0 sound-intel8x0
snd-emu10k1 sound-emu10k1
| Code: | | # nano -w /etc/modules.d/alsa |
17.4 - Running alsamixer
You should run alsamixer to adjust the levels of your card, and make sure it is all unmuted, you can press 'M' to unmute/mute the card, by default, alsaconf should unmute all or most, depending on setup, of the things required.
17.5 - Adding alsasound to the default runlevel
| Code: | | # rc-update add alsasound default |
18 - Keeping your system up-to-date
18.1 - Updating the world
First of all always keep the sync up-to-date, a emerge --sync once a day at least is recommended
To update all the packages, run
| Code: | | # emerge -auDN world |
To update /usr/local/overlays/emission-guide and /etc/portage/package.*/emission-guide do the following as root:
| Code: | | # emission-manager update |
-----
Well this brings us to our end, I wish you the best of luck.
Your system now includes...
* Ext3 File system
* GCC 4.1 based system
* Nxsty's Glibc Overlay (2.3.91)
* Improved LD performance with -Bdirect and more
* The latest packages portage has to offer
* A very nice boot-up splash with a progress bar
-----
If you need other assistance, have suggestions, or need to contact me personally, do so at.
Email: nesl247@gmail.com
AIM: nesl247
MSN: nesl247@gmail.com
IRC: nesl247
------
Messages from Nesl247
I hope everything went successfully. If you have any questions, comments, complaints, suggestions, requests, etc please feel free to contact me or leave a reply.
Thanks,
Nesl247
All rights to replicate this guide and all packages of it are reserved. If you would like to distribute, or use any part of this guide, please have my prior permission. However I do reserve the right to revoke this permission at any time for any reason
Last edited by nesl247 on Wed Mar 15, 2006 8:57 pm; edited 6 times in total |
|
| Back to top |
|
 |
cheater1034
Veteran
Joined: 09 Sep 2004
Posts: 1551
|
| Posted: Fri Mar 03, 2006 11:00 pm Post subject: |
|
|
Good luck with your guide nesl,
This guide still looks like mine in the sense the same bb code just slightly edited, but I will let it go 
_________________
JOIN IRC!: #zen-sources on irc.rizon.net
zen-kernel.org
Zen bugs/requests?: http://zen-kernel.org/issues
--
Join: ARCFPWDLVEFOTTSBNA - Anti-Rice club for people who don't like volcanoes except for on the TVs sometimes but not always |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Fri Mar 03, 2006 11:12 pm Post subject: |
|
|
| Cheater please stop saying that, you do have to remember that the 2.0 guide was a modified form of mine. Eventually I will redo the guide to change it a bit but people needed this now (had several urgent requests) so I had no time to please you with it's look. |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3050
Location: Houston, TX
|
| Posted: Sat Mar 04, 2006 4:07 am Post subject: |
|
|
| cheater1034 wrote: | | This guide still looks like mine in the sense the same bb code just slightly edited, but I will let it go |
Ironic considering your original install guide was just a slightly-edited version of bobp's stage1/3. |
|
| Back to top |
|
|
cheater1034
Veteran
Joined: 09 Sep 2004
Posts: 1551
|
| Posted: Sat Mar 04, 2006 4:21 am Post subject: |
|
|
| slycordinator wrote: | | cheater1034 wrote: | | This guide still looks like mine in the sense the same bb code just slightly edited, but I will let it go |
Ironic considering your original install guide was just a slightly-edited version of bobp's stage1/3. |
I wrote my guide from scratch.
please get your facts straight, to avoid flaming I will PM you with a message.
Im a friendly and nice guy, I just get very frustrated at statements like these.
_________________
JOIN IRC!: #zen-sources on irc.rizon.net
zen-kernel.org
Zen bugs/requests?: http://zen-kernel.org/issues
--
Join: ARCFPWDLVEFOTTSBNA - Anti-Rice club for people who don't like volcanoes except for on the TVs sometimes but not always |
|
| Back to top |
|
|
anthony_barclay
n00b
Joined: 17 Feb 2006
Posts: 5
|
| Posted: Sat Mar 04, 2006 12:07 pm Post subject: |
|
|
| Just started the install and can't complete the first build of the toolchain due to the CFLAGS and LDFLAGS in the make.conf in the overlay. Seems you need to do what you did in your previous guides and have 2 make.confs - one with cut-down CFLAGS etc that can be used for the initial build done with GCC 3.4.4 and another to do the rebuild with GCC 4.1. Having replicated what you did previously it now seems to be building happily. Have I missed something obvious or is this what I should be doing? |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Sat Mar 04, 2006 12:16 pm Post subject: |
|
|
| I think it is the ldflags, I wish I didn't have to do that, was kind of annoying. Will fix that up shortly, so thank you for reporting the error. |
|
| Back to top |
|
|
anthony_barclay
n00b
Joined: 17 Feb 2006
Posts: 5
|
| Posted: Sat Mar 04, 2006 12:46 pm Post subject: |
|
|
| No problem - guess the nicest solution would be to make stage 3s with the necessary gcc & binutils in place but suppose it would be a lot of work to produce stage 3s for all the necessary architectures |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2637
Location: Gainesville, Florida
|
| Posted: Sat Mar 04, 2006 2:08 pm Post subject: |
|
|
Anything those of us who already have a system up and running using the 2.1 guide need to do? I'd surely like to avoid having to rebuild another system on this drive (now my main Gentoo box). I'm hoping you have an update script backwards compatible with 2.1.
I do intend on trying this new version in the near future on another new 60GB Maxtor ATA133 drive I just aquired.
One minor suggestion: Maybe on step 15.3, suggest using (or add) the option "Xorg -configure" instead of "xorgconfig." I never got xorgconfig to work with your guides (and I'ved used it many times previously over the years, and it's always a pain). Xorg -configure is really a breeze, essentially autoconfigs X, and for me has always succeeded first try on many boxes.
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Sat Mar 04, 2006 4:07 pm Post subject: |
|
|
I guess I can change it, but really if you are doing something like this, you should be able to configure it. I did it when xorg was first released, and even with xfree86.
I do plan on an upgrade guide (most likely via my script for automation) in the next few days.
Stage3's were always a plan of mine back when I worked under the Conrad Projects. I will do them eventually, but you have to understand that I would need actual hosting. What hosts this overlay is a cheap free hosting we found online.
Thanks, nesl247 |
|
| Back to top |
|
|
StifflerStealth
l33t
Joined: 03 Jul 2002
Posts: 954
|
| Posted: Sat Mar 04, 2006 6:25 pm Post subject: |
|
|
Oh, xorgconfig creates the wrong link to the rgb file, but Xorg -configure creates the right link ... strange. If you look at the path given by these two configure ways, the do a ls on those directories, you can see that the rgb.txt.
Another excellent guide. I am looking forward to the changes you have planned to the looks of it. 
_________________
Nothing to read in this sig. Move along. |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Sun Mar 05, 2006 3:43 am Post subject: |
|
|
I do hope for some feature requests this time. Also if anyone is able to provide hosting (with cpanel, or directadmin - You either need to own the server or have a reseller account) that would be excellent. We are also looking for stage3 hosting (requires about 2 GB of space and about 5GB of bandwidth with a decent download speed in the United States)
Thank you all again, and I hope to get some feedback soon. |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
| Posted: Sun Mar 05, 2006 3:55 am Post subject: |
|
|
You know, you could just build a default -march=686 stage3 and/or stage4 for now, and only build the guide on installing that, and later if users want to give back to you guide, you could create a standardization for your stage3's, and work with the users on creating them.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Sun Mar 05, 2006 4:05 am Post subject: |
|
|
| I do plan on building stage3's. This will allow people to skip past the toolchain process if they do not feel like modifying CFLAGS, LDFLAGS or CXXFLAGS. I will do this for the supported cpu types (athlon-xp, i686, athlon64, pentium3, pentium4). But first I need the hosting like I asked above. |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2637
Location: Gainesville, Florida
|
| Posted: Sun Mar 05, 2006 5:25 am Post subject: |
|
|
I've built the 2.1-pre version with gcc-4.1.0-pre20060223. I just did an emerge sync (been away for 3 days), and noticed gcc-4.1 was now in portage:
conrad-gentoo wrc # emerge -upD system
These are the packages that would be merged, in order:
Calculating system dependencies... done!
[ebuild U ] sys-devel/gnuconfig-20060227 [20051223]
[ebuild NS ] sys-devel/gcc-4.1.0 USE="fortran gtk multislot nls -bootstrap -build -gcj -ip28 -mudflap -nocxx -objc -objc++ -objc-gc -vanilla"
[ebuild U ] sys-apps/groff-1.19.2-r1 [1.19.2]
[ebuild U ] sys-apps/baselayout-1.12.0_pre16-r3 [1.12.0_pre16-r1]
[ebuild U ] sys-fs/udev-086 [085]
[ebuild U ] net-misc/openssh-4.3_p2-r1 [4.3_p1]
[ebuild U ] sys-apps/man-pages-2.25 [2.24]
Has anyone done this gcc-4.1 update, rebuilt world, and had any problems, and/or is this going to conflict with the nesl247 root-overlay in any manner?
I guess I'm not quite understanding if everytime we update a toolchain package that shows up in portage ~x86, is it also going to require and updated -root-overlay? Of course I'll do a "quickpkg gcc" first, just to play it safe.
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Sun Mar 05, 2006 5:39 am Post subject: |
|
|
The pre-release was not supported. No problems have been reported (I have rebuilt already).
This is the exact reason I posted the warning at the top to not use it. I won't give an upgrade path for the pre-release. I will have the 2.0 -> 1.0 soon. (1.0 being the release version of 2.1 since the guide name changed) |
|
| Back to top |
|
|
mafioso
Tux's lil' helper
Joined: 10 Jan 2006
Posts: 98
Location: arizona, usa
|
| Posted: Sun Mar 05, 2006 5:54 am Post subject: |
|
|
| wrc1944 wrote: |
Has anyone done this gcc-4.1 update, rebuilt world, and had any problems, and/or is this going to conflict with the nesl247 root-overlay in any manner?
I guess I'm not quite understanding if everytime we update a toolchain package that shows up in portage ~x86, is it also going to require and updated -root-overlay? Of course I'll do a "quickpkg gcc" first, just to play it safe. |
i installed this current install of gentoo using the 2.0.8 version of nesl's (conrad) guide (modified to suit my tastes). i just finished an emerge -e world and was able to build ALL 631 packages (using the latest gcc-4.1.0 & nxsty's glibc 2.3.91.20060303). the only problems i had was with the latest ffmpeg which compiled fine after all the other packages were done and with gtkglarea which i needed to grab an overlay for from nesl247's latest guide overlay.
_________________
persistance is THE key to success |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2637
Location: Gainesville, Florida
|
| Posted: Sun Mar 05, 2006 2:59 pm Post subject: |
|
|
nesl247 wrote:
| Quote: |
The pre-release was not supported. No problems have been reported (I have rebuilt already). This is the exact reason I posted the warning at the top to not use it. I won't give an upgrade path for the pre-release. |
Hmmm- I was anxious to get it up and running due to all my previous failures with the earlier versions, an I also thought you needed it tested. Anyway, it worked out fine and i have a great system built with 2.1-pre- here's what resulted:
Portage 2.1_pre5-r4 (default-linux/x86/2006.0, gcc-4.1.0-pre20060223, glibc-2.3.90.20060224-r0, 2.6.16_rc4-no1 i686)
=================================================================
System uname: 2.6.16_rc4-no1 i686 AMD Athlon(tm) XP 3000+
Gentoo Base System version 1.12.0_pre16
ccache version 2.4 [enabled]
No problems with the 2.6.16-rc4 kernel, and I've got the new /etc/portage/package directories version.
I hope to avoid having to completely redo my 2.1-pre install, but will certainly do so if need be.
As an alternative, and since there's not going to be an upgrade script from the 2.1-pre to current Evolution Mission, can I copy over etc/portage from a new "Evolution Mission" install on another ATA133 hard disk to this older "2.1-pre" installation, and then do an emerge -e world, thus in effect updating 2.1-pre to "Evolution Mission"? The new "Evolution Mission" version would be built on the same or virtually identical box.
Another question: I thought I had uncommented the video card line in make.conf, but apparently I foolishly forgot, because it pulled in all the video drivers when I emerged xorg. Can I just comment out all the others I don't need except "ati" in /etc/portage/package.unmask/nesl247-guide, and also emerge -C them?
Thanks mafioso,
Guess I'll try an emerge -e world too. Am I going to need the nxsty 2.3.91.20060303 glibc overlay. I really am apprehensive about mixing stuff up, and maybe I'd be better off doing a new Evolution install on another drive, and try copying over /etc/portage as I postulated above?
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Sun Mar 05, 2006 3:05 pm Post subject: |
|
|
| wrc1944: I needed people to look through it and find bugs without installing. The guide changed rapidly is why I can't support it. I do advise doing a reinstall because you need to do the emerge -e world now, and you need my updated manager script (well you don't NEED it but it is the only supported method for updating the overlay), and /etc/portage has changed a bit. Some other stuff to. Also, just uncomment the video card line and put in the needed stuff, then un-emerge all the other drivers. (emerge -C /var/db/pkg/x11-drivers/* && emerge xf86-input-keyboard xf86-input-mouse, and then any other needed drivers) |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2637
Location: Gainesville, Florida
|
| Posted: Sun Mar 05, 2006 5:02 pm Post subject: |
|
|
nesl247,
Thanks for the info. I think the first thing I'll do is complete a new Evolution install on my other 60GB ATA133 drive, and get that under my belt. Then compare what's changed, and perhaps try and avoid wiping my great 2.1-pre install- it works so well I just can't bring myself to wipe it without at least trying to update it to Evolution.
Here's my thinking:
Coudn't I rename my current 2.1-pre installation /etc/portage and /usr/local/overlays directories, and then pick up at step 7.1 and extract the new Evolution Mission overlay? Then continue on with rebuilding everything as in steps 7.8 and 7.9?
Wouldn't that get me current with Evolution and the new update manager script? Or am I overlooking something vital?
BTW, I just compiled the new gcc-4.1 in portage OK.
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Sun Mar 05, 2006 5:03 pm Post subject: |
|
|
Anyone who has used this guide please do the following:
| Code: | # rm /etc/portage/profile/virtuals
# wget --output-document=/etc/portage/profile/package.provided http://h1.ripway.com/evomission/package.provided |
|
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Sun Mar 05, 2006 6:08 pm Post subject: |
|
|
| You could just remove /etc/portage, /usr/local/overlays/gnome-experimental, /usr/local/overlays/emission-guide, and then follow from the extracting of the root-overlay forward. (Of course you should know which steps you can skip, such as the emerging of xorg-x11 which you will have re-compiled via emerge -e world) |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2637
Location: Gainesville, Florida
|
| Posted: Sun Mar 05, 2006 9:07 pm Post subject: |
|
|
Thanks nesl247,
I figured that should work. I'm currently on step 7.4 of a new evomission install on my other drive, so when that's done, I'll give the other update from 2.1-pre a try. (only have one monitor and have to share it with all my boxes, so I have to do one install at a time).
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Sun Mar 05, 2006 9:14 pm Post subject: |
|
|
I hope it goes well for you, update me on your status every once in a while.
Still looking for feedback, and stage3/site hosting offers. But mostly, I just want feedback (any feedback, good, bad, and the ugly) |
|
| Back to top |
|
|
StifflerStealth
l33t
Joined: 03 Jul 2002
Posts: 954
|
| Posted: Mon Mar 06, 2006 12:34 am Post subject: |
|
|
I just got done doing a emerge -e world to use the new glibc and gcc 4.1 final, and it all worked. Only thing was kpdf not liking the new poppler, but emerge sync and emerge --resume fixed that. So, everything is up and runny and VERY fast. KDE has never been this fast before. I love it. ^^ Thanks for the guide. Though, I did modify it a bit by taking out the gnome overlay, and I am using my own partition for the portage tree: Gentoo main is at /portage/gentoo and the overlay is at /portage/overlay. /portage is hdb1 and a 10 gig partition. But other than that, I mainly followed the guide. Now I need to set up Alsa. That's my feedback.
_________________
Nothing to read in this sig. Move along. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
