Thanks - I'll give that a try, since the stock kernel seems to like to suck up a lot of CPU cycles at odd times. It's probably related to the ACPI hack that I used...
I really like this system, though -- all of the advantages of Debian, except that I get access to free-as-in-beer software and I get up to date packages without having to go to unstable. :-) -Luke On Sun, 2003-11-16 at 21:45, Brett I. Holcomb wrote: > Go into /usr/portage/sys-kernel and in some of the directories you will find > 2.6 kernel ebuilds. This directory contains subdirectories for all the > kernels available. However, only some kernels have 2.6 versions. Peruse the > subdirectories in sys-kernel and pick one you like. You'll have to use the > ACCEPT_KEYWORDS="~x86" emerge ./ebuildname technique while you are in the > subdirectory for the kernel. > > On Sunday 16 November 2003 21:28, you wrote: > > On Sun, 2003-11-16 at 21:08, Brett I. Holcomb wrote: > > > On Sunday 16 November 2003 20:51, you wrote: > > > > So far, it's a really good -- especially for something that appears at > > > > first glance to be bleeding edge. One of the reasons I'm running it on > > > > my personal machine is to find out how often the packages get broken. > > > > That way, I can decide if it makes sense to run it at work. > > > > > > If you do not use ~arch (i.e. ~x86) routinely you'll be installing stable > > > packages. If you use ~arch for everything you're experimenting <G>. I > > > do NOT have ~x86 in my /etc/make.conf but when I want to merge a package > > > that is masked I do > > > > > > ACCEPT_KEYWORDS="~x86" emerge packagename > > > > Cool. I prefer to stay with stable stuff by default. :-) > > > > So, if I wanted to experiment with the 2.5 or 2.6 kernel, what package > > would I emerge? I just checked and "emerge -s gentoo-sources" and it > > appears to only have the 2.4.20-r8 under that name. > > > > Thanks! > > -Luke > > -- > [EMAIL PROTECTED] mailing list > > -- [EMAIL PROTECTED] mailing list
