| View previous topic :: View next topic |
| Author |
Message |
anarchron
n00b
Joined: 13 Jul 2003
Posts: 38
|
 Posted: Mon Jan 12, 2004 10:53 am Post subject: |
 |
|
| Are there any optimizations for stage2 and stage3 tarballs? |
|
| Back to top |
|
 |
dreas
Guru
Joined: 06 Aug 2003
Posts: 359
Location: Germany
|
| Posted: Mon Jan 12, 2004 10:55 am Post subject: |
|
|
I think that's a good time to get rid of Suse on my old K6-II box.  |
|
| Back to top |
|
|
Suicidal
l33t
Joined: 30 Jul 2003
Posts: 959
Location: /dev/null
|
| Posted: Mon Jan 12, 2004 11:08 am Post subject: |
|
|
| Anyone had issues installing gentoo on a Dell powervault 715 nas? If not I might try that next weekend. Now that I think of it they had redhat as an option on that box so I think it will be ok. |
|
| Back to top |
|
|
gerard27
Advocate
Joined: 04 Jan 2004
Posts: 2377
Location: Netherlands
|
| Posted: Mon Jan 12, 2004 8:14 pm Post subject: |
|
|
I would like to join the fray.
Installed Gentoo 1.4 20030911 about two weeks ago.
Did have some configuration problems,all solved by reading the fora!
I still have some 8Gb free partition,which should be sufficient.
Compared to other distro's this one is really what the doctor ordered.
Gerard van Vuuren
Netherlands |
|
| Back to top |
|
|
mukwuknuk
Tux's lil' helper
Joined: 23 Dec 2003
Posts: 80
Location: Colorado, USA
|
| Posted: Mon Jan 12, 2004 10:01 pm Post subject: |
|
|
Regarding the "make.conf" issue or difficulty --
Ques 1: Does this problem apply to all stages? If not, then which?
Ques 2: I don't have a make.conf.orig, which one vetran suggested using instead of make.conf. Can someone post a typical make.conf, or would it be too long? (Obviously a disclaimer would be appropriate that it won't work for everyone). I don't suppose there's a config utility to create a make.conf?
Ques 3: How serious is this? What's the "semi-official" definition of the problem anyway? All I see here in this testing thread are a few short, cryptic comments that the make.conf supplied is so bare-bones that it's insufficient... is that the sum total of the concern? Is everyone experiencing the same problem?
_________________
"If there are back-slashes in your path, you're heading down the wrong path ... backwards." |
|
| Back to top |
|
|
Hey!
n00b
Joined: 07 Dec 2003
Posts: 20
|
| Posted: Tue Jan 13, 2004 6:50 am Post subject: |
|
|
| mukwuknuk wrote: | Regarding the "make.conf" issue or difficulty --
Ques 2: I don't have a make.conf.orig, which one vetran suggested using instead of make.conf. Can someone post a typical make.conf, or would it be too long? (Obviously a disclaimer would be appropriate that it won't work for everyone). I don't suppose there's a config utility to create a make.conf?
Ques 3: How serious is this? What's the "semi-official" definition of the problem anyway? All I see here in this testing thread are a few short, cryptic comments that the make.conf supplied is so bare-bones that it's insufficient... is that the sum total of the concern? Is everyone experiencing the same problem? |
It's not a big deal. The make.conf script that comes with 2004.0 is very minimal, but with a bit of tweaking fully functional. My first emerge with 2004.0 was with only my USE variables and ACCEPT_KEYWORDS added and all worked fine.
Here is the sample make.conf
| Code: | # Copyright 2000-2003 Daniel Robbins, Gentoo Technologies, Inc.
# Contains local system settings for Portage system
# $Header: /home/cvsroot/gentoo-src/portage/cnf/make.conf,v 1.68 2003/09/29 18:13:42 carpaski Exp $
# Please review 'man make.conf' for more information.
# Build-time functionality
# ========================
#
# The USE variable is used to enable optional build-time functionality. For
# example, quite a few packages have optional X, gtk or GNOME functionality
# that can only be enabled or disabled at compile-time. Gentoo Linux has a
# very extensive set of USE variables described in our USE variable HOWTO at
# http://www.gentoo.org/doc/use-howto.html
#
# The available list of use flags with descriptions is in your portage tree.
# Use 'less' to view them: --> less /usr/portage/profiles/use.desc <--
#
# 'ufed' is an ncurses/dialog interface available in portage to make handling
# useflags for you. 'emerge app-admin/ufed'
#
# Example:
#USE="X gtk gnome -alsa"
# Host Setting
# ============
#
# If you are using a Pentium Pro or greater processor, leave this line as-is;
# otherwise, change to i586, i486 or i386 as appropriate. All modern systems
# (even Athlons) should use "i686-pc-linux-gnu". All K6's are i586.
#
CHOST="i686-pc-linux-gnu"
# Host and optimization settings
# ==============================
#
# For optimal performance, enable a CFLAGS setting appropriate for your CPU.
#
# Please note that if you experience strange issues with a package, it may be
# due to gcc's optimizations interacting in a strange way. Please test the
# package (and in some cases the libraries it uses) at default optimizations
# before reporting errors to developers.
#
# -mcpu=<cpu-type> means optimize code for the particular type of CPU without
# breaking compatibility with other CPUs.
#
# -march=<cpu-type> means to take full advantage of the ABI and instructions
# for the particular CPU; this will break compatibility with older CPUs (for
# example, -march=athlon-xp code will not run on a regular Athlon, and
# -march=i686 code will not run on a Pentium Classic.
#
# CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp,
# athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
# (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron), pentium3.
# Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
#
# CPU types supported in gcc-2.95*: k6, i386, i486, i586 (Pentium), i686
# (Pentium Pro), pentium, pentiumpro Gentoo Linux 1.2 and below use gcc-2.95*
#
# CRITICAL WARNINGS: ****************************************************** #
# ATHLON-4 will generate invalid SSE instructions; use 'athlon' instead. #
# PENTIUM4 will generate invalid SSE2 instructions; use 'pentium3' instead. #
# K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. #
# ************************************************************************* #
#
# Decent examples:
#
#CFLAGS="-mcpu=athlon-xp -O3 -pipe"
#CFLAGS="-march=pentium3 -O3 -pipe"
# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings.
#CXXFLAGS="${CFLAGS}"
# Advanced Masking
# ================
#
# Gentoo is using a new masking system to allow for easier stability testing
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
# on the platform they are set for. A special form has been added that
# indicates packages and revisions that are expected to work, but have not yet
# been approved for the stable set. '~arch' is a superset of 'arch' which
# includes the unstable, in testing, packages. Users of the 'x86' architecture
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
# '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms.
# DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
#
#ACCEPT_KEYWORDS="~arch"
# Portage Directories
# ===================
#
# Each of these settings controls an aspect of portage's storage and file
# system usage. If you change any of these, be sure it is available when
# you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
#
# PORTAGE_TMPDIR is the location portage will use for compilations and
# temporary storage of data. This can get VERY large depending upon
# the application being installed.
#PORTAGE_TMPDIR=/var/tmp
#
# PORTDIR is the location of the portage tree. This is the repository
# for all profile information as well as all ebuilds. This directory
# itself can reach 200M. WE DO NOT RECOMMEND that you change this.
#PORTDIR=/usr/portage
#
# DISTDIR is where all of the source code tarballs will be placed for
# emerges. The source code is maintained here unless you delete
# it. The entire repository of tarballs for gentoo is 9G. This is
# considerably more than any user will ever download. 2-3G is
# a large DISTDIR.
#DISTDIR=${PORTDIR}/distfiles
#
# PKGDIR is the location of binary packages that you can have created
# with '--buildpkg' or '-b' while emerging a package. This can get
# upto several hundred megs, or even a few gigs.
#PKGDIR=${PORTDIR}/packages
#
# PORT_LOGDIR is the location where portage will store all the logs it
# creates from each individual merge. They are stored as YYMMDD-$PF.log
# in the directory specified. This is disabled until you enable it by
# providing a directory. Permissions will be modified as needed IF the
# directory exists, otherwise logging will be disabled.
#PORT_LOGDIR=/var/log/portage
#
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
# concern that they will be deleted by rsync updates. Default is not
# defined.
#PORTDIR_OVERLAY=/usr/local/portage
# Fetching files
# ==============
#
# If you need to set a proxy for wget or lukemftp, add the appropriate "export
# ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
# all users on your system should use them.
#
# Portage uses wget by default. Here are some settings for some alternate
# downloaders -- note that you need to merge these programs first before they
# will be available.
#
# Default fetch command (5 tries, passive ftp for firewall compatibility)
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#
# Using wget, ratelimiting downloads
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#
# Lukemftp (BSD ftp):
#FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}"
#RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}"
#
# Prozilla (turbo downloader)
#FETCHCOMMAND='/usr/bin/proz --no-getch -s ${URI} -P ${DISTDIR}'
#
# Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
# The list is a space seperated list which is read left to right. If you use
# another mirror we highly recommend leaving the default mirror at the end of
# the list so that portage will fall back to it if the files cannot be found
# on your specified mirror. We _HIGHLY_ recommend that you change this setting
# to a nearby mirror by merging and using the 'mirrorselect' tool.
#GENTOO_MIRRORS="<your_mirror_here> http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo"
#
# Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
# The list is a single extry specifying the full address of the directory
# serving the tbz2's for your system. Running emerge with either '--getbinpkg'
# or '--getbinpkgonly' will cause portage to retrieve the metadata from all
# packages in the directory specified, and use that data to determine what will
# be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please
# consult the man pages and 'emerge --help' for more information.
#PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/"
#PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"
# Synchronizing Portage
# =====================
#
# Each of these settings effects how Gentoo synchronizes your Portage tree.
# Synchronization is handled by rsync and these settings allow some control
# over how it is done.
#
#
# SYNC is the server used by rsync to retrieve a localized rsync mirror
# rotation. This allows you to select servers that are geographically
# close to you, yet still distribute the load over a number of servers.
# Please do not single out specific rsync mirrors. Doing so places undue
# stress on particular mirrors. Instead you may use one of the following
# continent specific rotations:
#
# Default: "rsync://rsync.gentoo.org/gentoo-portage"
# North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage"
# South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage"
# Europe: "rsync://rsync.europe.gentoo.org/gentoo-portage"
# Asia: "rsync://rsync.asia.gentoo.org/gentoo-portage"
# Australia: "rsync://rsync.au.gentoo.org/gentoo-portage"
#SYNC="rsync://rsync.gentoo.org/gentoo-portage"
#
# RSYNC_RETRIES sets the number of times portage will attempt to retrieve
# a current portage tree before it exits with an error. This allows
# for a more successful retrieval without user intervention most times.
#RSYNC_RETRIES="3"
#
# RSYNC_TIMEOUT sets the length of time rsync will wait before it times out
# on a connection. Most users will benefit from this setting as it will
# reduce the amount of 'dead air' they experience when they run across
# the occasional, unreachable mirror. Dialup users might want to set this
# value up around the 300 second mark.
#RSYNC_TIMEOUT=180
# Advanced Features
# =================
#
# MAKEOPTS provides extra options that may be passed to 'make' when a
# program is compiled. Presently the only use is for specifying
# the number of parallel makes (-j) to perform. The suggested number
# for parallel makes is CPUs+1.
#MAKEOPTS="-j2"
#
# PORTAGE_NICENESS provides a default increment to emerge's niceness level.
# Note: This is an increment. Running emerge in a niced environment will
# reduce it further. Default is unset.
#PORTAGE_NICENESS=3
#
# AUTOCLEAN enables portage to automatically clean out older or overlapping
# packages from the system after every successful merge. This is the
# same as running 'emerge -c' after every merge. Set with: "yes" or "no".
# This does not affect the unpacked source. See 'noclean' below.
#AUTOCLEAN="yes"
#
# FEATURES are settings that affect the functionality of portage. Most of
# these settings are for developer use, but some are available to non-
# developers as well.
#
# 'autoaddcvs' causes portage to automatically try to add files to cvs
# that will have to be added later. Done at generation times
# and only has an effect when 'cvs' is also set.
# 'buildpkg' causes binary packages to be created of all packages that
# are merged.
# 'ccache' enables ccache support via CC.
# 'cvs' feature for developers that causes portage to enable all
# cvs features (commits, adds) and all USE flags in SRC_URI
# will be applied for digests.
# 'digest' autogenerate a digest for packages.
# 'distcc' enables distcc support via CC.
# 'fixpackages' allows portage to fix binary packages that are stored in
# PKGDIR. This can consume a lot of time. 'fixpackages' is
# also a script that can be run at any given time to force
# the same actions.
# 'keeptemp' prevents the clean phase from deleting the temp files ($T)
# from a merge.
# 'keepwork' prevents the clean phase from deleting the WORKDIR.
# 'noauto' causes ebuild to perform only the action requested and
# not any other required actions like clean or
# 'noclean' prevents portage from removing the source and temporary files
# after a merge -- for debugging purposes only.
# 'nostrip' prevents stripping of binaries.
# 'notitles' disables xterm titlebar updates (which contain status info).
# 'sandbox' enable sandbox-ing when running emerge and ebuild
# 'strict' causes portage to react strongly to conditions that
# have the potential to be dangerous -- like missing or
# incorrect Manifest files.
# 'userpriv' allows portage to drop root privleges while it is compiling
# as a security measure, and as a side effect this can remove
# sandbox access violations for users.
# 'usersandbox' enables sandboxing while portage is running under userpriv.
# unpack -- for debugging purposes only.
#FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork"
#
# CCACHE_SIZE sets the space use limitations for ccache. The default size is
# 2G, and will be set if not defined otherwise and ccache is in features.
# Portage will set the default ccache dir if it is not present in the
# user's environment, for userpriv it sets: ${PORTAGE_TMPDIR}/ccache
# (/var/tmp/ccache), and for regular use the default is /root/.ccache.
# Sizes are specified with 'G' 'M' or 'K'.
# '4G' for 4 gigabytes, '4096M' for 4 gigabytes, etc... Default is 2G
#CCACHE_SIZE="2G"
#
# DISTCC_DIR sets the temporary space used by distcc.
#DISTCC_DIR="${PORT_TMPDIR}/.distcc"
#
# RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates
# the portage tree. Specific chucks of the tree may be excluded from
# consideration. This may cause dependency failures if you are not careful.
# The file format is one pattern per line, blanks and ';' or '#' lines are
# comments. See 'man rsync' for more details on the exclude-from format.
#RSYNC_EXCLUDEFROM=/etc/portage/rsync_excludes
|
Have fun! |
|
| Back to top |
|
|
dalek
Veteran
Joined: 19 Sep 2003
Posts: 1353
Location: Mississippi USA
|
| Posted: Tue Jan 13, 2004 7:09 am Post subject: |
|
|
Is there like a make.conf how to somewhere. I would really like to know some of the tricks to a really good setup. I plan to install Gentoo on a old AMD 400MHz machine. I need something to "guide" me if you know what I mean. A link will be fine, or just point me in the direction.
Thanks
_________________
My rig: Gigabyte GA-970A-UD3P mobo, AMD FX-8350 Eight-Core CPU, ZALMAN CNPS10X Performa CPU cooler,
G.SKILL 32GB DDR3 PC3 12800 Memory Nvidia GTX-650 video card LG W2253 Monitor
60TBs of hard drive space using LVM
Cooler Master HAF-932 Case |
|
| Back to top |
|
|
Chaosite
Guru
Joined: 13 Dec 2003
Posts: 540
Location: Right over here.
|
| Posted: Tue Jan 13, 2004 12:28 pm Post subject: |
|
|
Hey, to all those who are have make.conf parsing problems,
First thing you do on the system, run:
| Code: | | cp /etc/make.conf.example /etc/make.conf |
To get the ultra explantory version of the file.
IMHO, this should be already done in the tarball...
P.S. It might be added by an `emerge sync`. Don't think so, but... |
|
| Back to top |
|
|
gerard27
Advocate
Joined: 04 Jan 2004
Posts: 2377
Location: Netherlands
|
| Posted: Tue Jan 13, 2004 3:39 pm Post subject: |
|
|
I started with stage 1-x86-20040105.tar.bz2.
All went ok until I did "emerge sync" to load the portage tree.
I got a message that my box couldn't connect.
What did I do wrong?
Gerard |
|
| Back to top |
|
|
ledskof
Apprentice
Joined: 22 Oct 2002
Posts: 209
|
|
| Back to top |
|
|
Chaosite
Guru
Joined: 13 Dec 2003
Posts: 540
Location: Right over here.
|
| Posted: Tue Jan 13, 2004 4:49 pm Post subject: |
|
|
| Gerard van Vuuren wrote: | I started with stage 1-x86-20040105.tar.bz2.
All went ok until I did "emerge sync" to load the portage tree.
I got a message that my box couldn't connect.
What did I do wrong?
Gerard |
In make.conf, try setting `SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"` so you'll be using a diffrent server which is still up.
Also, regarding my previous post, make.conf.example pops up when you emerge portage. |
|
| Back to top |
|
|
gerard27
Advocate
Joined: 04 Jan 2004
Posts: 2377
Location: Netherlands
|
| Posted: Wed Jan 14, 2004 10:59 am Post subject: |
|
|
I changed the SYNC = to what Chaosite suggested and portage was loaded and executed.
To my chagrin I noticed that gcc was compiling for i686 instead of
athlon xp.Then I did emerge system and saw the same thing.
My make.conf was gone and replaced by a 5 line file
[/quote]"#These settings were set by the catalyst build script that automatically built this stage"
CFLAGS = "-02 -mcpu=i686 -fomit -frame-pointer"
CHOST="-386-pc-linux-gnu"
USE=""
CXXFLAGS="$CFLAGS"
I guess I have to start all over again but I would lijke to know whether
this will happen again.
Gerard. |
|
| Back to top |
|
|
beejay
Retired Dev
Joined: 03 Oct 2002
Posts: 924
Location: Flensungen (das liegt neben Merlau)
|
| Posted: Wed Jan 14, 2004 1:01 pm Post subject: |
|
|
| Gerard van Vuuren wrote: | I changed the SYNC = to what Chaosite suggested and portage was loaded and executed.
To my chagrin I noticed that gcc was compiling for i686 instead of
athlon xp.Then I did emerge system and saw the same thing.
My make.conf was gone and replaced by a 5 line file
| Code: | #These settings were set by the catalyst build script that automatically built this stage"
CFLAGS = "-02 -mcpu=i686 -fomit -frame-pointer"
CHOST="-386-pc-linux-gnu"
USE=""
CXXFLAGS="$CFLAGS" |
I guess I have to start all over again but I would lijke to know whether
this will happen again.
Gerard. |
Don't set any optimizations (i.e. using ~x86) before bootstrap.sh is finished (This is also mentioned in the installation-guide).
All stages include a minimized make.conf. New (and more professional) make.conf's are now saved as make.conf.example when you upgrade portage (this is in fact what you do when bootstrapping or emerging system. This five-line-file you posted is in fact the original make.conf that was put into the stages.
_________________
Dort wo schwarzer Rauch aufsteigt, sich alsbald ein Fehler zeigt.
www.paludis-sucks.org | www.gentoo.de | www.gentoo-ev.org | www.gentoo.org
Last edited by beejay on Wed Jan 14, 2004 9:22 pm; edited 1 time in total |
|
| Back to top |
|
|
djh-world
Apprentice
Joined: 04 Jan 2004
Posts: 281
Location: Nottingham, UK
|
| Posted: Wed Jan 14, 2004 3:23 pm Post subject: |
|
|
| Out of interest, when will this 2004.o be fully released? Cause currently i'm having many problems with my hardware (via kt600) and people say waiting for the next release might be a good idea. |
|
| Back to top |
|
|
beejay
Retired Dev
Joined: 03 Oct 2002
Posts: 924
Location: Flensungen (das liegt neben Merlau)
|
| Posted: Wed Jan 14, 2004 5:56 pm Post subject: |
|
|
| gamezfreakuk wrote: | | Out of interest, when will this 2004.o be fully released? Cause currently i'm having many problems with my hardware (via kt600) and people say waiting for the next release might be a good idea. |
Near the end of January. But you won't get any benefit if you wait to reinstall, since you automatically will be up-to-date and automatically get a system like 2004 if you update regulary.
_________________
Dort wo schwarzer Rauch aufsteigt, sich alsbald ein Fehler zeigt.
www.paludis-sucks.org | www.gentoo.de | www.gentoo-ev.org | www.gentoo.org |
|
| Back to top |
|
|
Verbal
n00b
Joined: 17 Feb 2003
Posts: 11
Location: Your Post
|
| Posted: Wed Jan 14, 2004 9:16 pm Post subject: |
|
|
I may have to try this out on my 4u server with 4 SBC Celeron 500mhz and an openmosix/LTSP config. IPV6 will be tried as well as many servers.
I'll see what I can do this weekend. |
|
| Back to top |
|
|
langthang
Retired Dev
Joined: 27 Nov 2003
Posts: 620
|
| Posted: Wed Jan 14, 2004 10:20 pm Post subject: |
|
|
| /etc/make.conf in stage1-x86-200040105.tar.bz2 has an entry CXXFLAGS="$CFLAGS". Should it be CXXFLAGS="${CFLAGS}"? Because emerge info with CXXFLAGS="$CFLAGS" will set CXXFLAGS=" " |
|
| Back to top |
|
|
mukwuknuk
Tux's lil' helper
Joined: 23 Dec 2003
Posts: 80
Location: Colorado, USA
|
| Posted: Thu Jan 15, 2004 4:19 am Post subject: |
|
|
This is hopeless (for someone at my level I mean; I'm not critisizing Gentoo or this testing effort). I don't know why I thought I could accomplish anything helpful.
When I do "emerge -k gentoo-sources" it goes out to a mirror site and grabs a bunch of 2.4 stuff, even though I untarred a 2.6 tarball and emerged the system from that. I presume that invalidates my testing since the 2.4.22 kernel is now being built, as far as I can tell.
So what stupid mistake did I make? Was I supposed to set a lot of flags somewhere? I think you folks would be better off testing without me.
_________________
"If there are back-slashes in your path, you're heading down the wrong path ... backwards." |
|
| Back to top |
|
|
pixie
Guru
Joined: 29 Dec 2002
Posts: 305
|
| Posted: Thu Jan 15, 2004 4:21 am Post subject: |
|
|
gentoo-sources is 2.4
gentoo-dev-sources is 2.6 |
|
| Back to top |
|
|
SilverMast
n00b
Joined: 15 Jan 2004
Posts: 3
|
| Posted: Thu Jan 15, 2004 9:56 am Post subject: pentium4 |
|
|
Is there any way I can successfully build this system pentium4-specific? I read an earlier post recommending I use the p3 setting instead, but that's not the essence or purpose of Gentoo  |
|
| Back to top |
|
|
SPW
Guru
Joined: 22 Jul 2003
Posts: 318
Location: Lëtzebuerg
|
| Posted: Thu Jan 15, 2004 10:11 am Post subject: |
|
|
I still have not understood why we need new Gentoo versions. As we can keep our system up to date and all the components are updated I do not see the reason. The installation of Gentoo is supposed to be a one-time hassle, isn't it?
(I apologize if this question has been asked many times, but I have not found an answer to this in the usual FAQ and documentation.) |
|
| Back to top |
|
|
beejay
Retired Dev
Joined: 03 Oct 2002
Posts: 924
Location: Flensungen (das liegt neben Merlau)
|
| Posted: Thu Jan 15, 2004 12:05 pm Post subject: Re: pentium4 |
|
|
| SilverMast wrote: | | Is there any way I can successfully build this system pentium4-specific? I read an earlier post recommending I use the p3 setting instead, but that's not the essence or purpose of Gentoo |
The Problem is not Gentoo, the problem is gcc. Some versions create wrong code with something like -march=pentium4 that won't work. Consider compiling libc like that, no errors on compile, portage completes the installation but after the next reboot -- BANG!
| SPW wrote: | I still have not understood why we need new Gentoo versions. As we can keep our system up to date and all the components are updated I do not see the reason. The installation of Gentoo is supposed to be a one-time hassle, isn't it?
(I apologize if this question has been asked many times, but I have not found an answer to this in the usual FAQ and documentation.) |
It's nothing for the user that has already installed Gentoo. It's more for new users. You don't need to reinstall (except in some very difficult situations like the step from Gentoo 1.2 to 1.4 since some critical changes took effect at this point in Gentoo's history ). But think of the Live-CD as a Rescue-CD or an Installation-medium for new users -- makes sense to have the newest software and the best tools on it, doesn't it
_________________
Dort wo schwarzer Rauch aufsteigt, sich alsbald ein Fehler zeigt.
www.paludis-sucks.org | www.gentoo.de | www.gentoo-ev.org | www.gentoo.org |
|
| Back to top |
|
|
darkcoder
Apprentice
Joined: 09 May 2003
Posts: 253
Location: Lynchburg, VA
|
| Posted: Thu Jan 15, 2004 5:58 pm Post subject: |
|
|
I will test the new stages by the weekend, but even if you are not related to this problem, maybe you can spread the word. Current 1.4 Live CD's have a problem with the detection of some Adaptec SCSI controllers when using the doscsi boot option. It detects the controller fine with the "standard" driver, but also try to detect the adapter "again?" with the aic7xxx_old detection driver, and that cause a system hang up. While watching the Knoppix detection phase I see that they do not use the old detection driver (apparently they already know is problematic).
That problem affects many adaptec scsi controllers which can be found on many (and probably most) servers out there like the Dell's on my office.
You can see the problem in some of those links.
https://bugs.gentoo.org/show_bug.cgi?id=34550
https://bugs.gentoo.org/show_bug.cgi?id=31201
https://bugs.gentoo.org/show_bug.cgi?id=26503
Please, fix this.
_________________
Not bleeding edge.... No pain no game  |
|
| Back to top |
|
|
darkcoder
Apprentice
Joined: 09 May 2003
Posts: 253
Location: Lynchburg, VA
|
| Posted: Thu Jan 15, 2004 6:08 pm Post subject: |
|
|
I agree with a previous post about kernel 2.6.x unstability. Not only that, there are still some patches not available for it like grsecurity.
But for marketing reasons, why not switch to kernel 2.4.23 or 2.4.24? Both hava available grsecurity, ck-patches, supermount, acpi updates (pardon me if forget other patches here). And while security fixes have been backported, new kernels mean driver updates, or new drivers, etc, And do not have to work educating users (specially new ones) that those kernels already have the security fixes found lately).
_________________
Not bleeding edge.... No pain no game |
|
| Back to top |
|
|
dkaplowitz
Guru
Joined: 22 Nov 2003
Posts: 596
Location: Philadelphia, PA
|
| Posted: Thu Jan 15, 2004 6:22 pm Post subject: |
|
|
I'm having an issue with web-rsync when I try to install using the stage1-x86-pie-ssp-20040105.tar.bz2 image to do a stage1 install behind a firewall. I'm not sure it's related to the test image; in fact I doubt it is. I think it's probably just the rsync problems of late, but in case it is somehow related, here is the support thread I started:
https://forums.gentoo.org/viewtopic.php?p=780521#780521
_________________
http://dkap.info |
|
| Back to top |
|
|
|
Kernel & Hardware
