why removed gentoo-sources 2.6.11 frm portage !!!

toofastforyahuh · Apprentice Joined: 18 May 2004 Posts: 164

Seriously, after problems with Red Hat's kernel packaging years ago, and genkernel's brokenness/untrustworthiness I learned you should only get kernels from kernel.org. Don't rely on distros to do it. If a distro really needs patches, it should be contributing them to the main codebase in the first place.

It's also good to scan the kernel.org changelogs occasionally. I saw enough comments about insufficient testing and brokenness to stay away from 2.6.12 entirely. CD burning broke in 2.6.8 and 2.6.9 as well. And I can't say I've been happy with the CPU time allocation in 2.6.11.10 either--the much-vaunted 2.6.x "responsiveness" is gone when running transcode now. So, in general, now isn't the time to play musical kernels. Stick with what works and leave it alone.

Keffin · Posted: Mon Jul 25, 2005 10:21 pm Post subject:

tnt · Veteran Joined: 27 Feb 2004 Posts: 1222

andrewd18 · Posted: Tue Jul 26, 2005 3:22 am Post subject:

brankob · Apprentice Joined: 29 Apr 2004 Posts: 188

Keffin:

Sorry. Nothing personal. I was just steaming on "Gentoo issues" that have killed me many times.

Just quick recount:

-some time (6 months ?) ago, new and fresh version of STABLE portage have chosen to erase everything in my root directory when doing "emerge -up world" What is espacially ironic with this is that sandbox was responsible for this- the very mechanism that should protect me from s*it like this ! Not to mention that this was STABLE portage und that system URGED ME TO UPGRADE TO THIS (BROKEN) VERSION AS SOON AS POSSIBLE !

- samba was changed so that its password files were moved from /etc/password to /usr/share/samba. Even more, in first versions aftere the change they were moved,but samba has expected them on the old place, so it didn't work correctly. After that, this was corrected but it wasn't properly documented anywhere. After changing the files manually for thousandth time, I decided to compile the thing manually, and it worked ! I then examined configure options and ceme across relevant option and solved the problem.
Oh yeah, there might be yellow warning notice about this that flashed on the screen for the femtosecond while emerging the thing, but how was I suppose to see it ?

- a few versions of portage back, someone has decided to regroup some config files (again) without too much of documentation. Also, some things with network were rearanged and a few new options were added. Consequence of this is that after that, half of my services stopped working and I have to rearange their booting time and edit some of them to get them to work together. Even today, after several iterations of portage, proftpd start script doesn't work at the boot time.
It starts, but proftpd daemon dies. If I do "/etc/init.d/proftpd zap ; /etc/init.d/proftpd start", it starts working again normally.

- Transition from profile 2004.3 --->2005.0 absolutely sucks. I have 3 dual Opterons machines with very similar hardware and very similar software and portage policies. All machines are periodically updatedt and all are now on profile 2005.0. 32-bit environment works today only on one of them. Even if I forget the horrible update walk_through_the_minefield upgrade procedure for the moment, I can't overlook the fact that I have had workibng 32-bit environment on all of them and now it works only on one. Even this was not achieved without an effort- I had to repeat the procedure several times- after a while, multilib got borked on all of them.

- There is something VERY wrong with the textual terminal, at least in non-US locales and it affects the terminal as well as everything based on ncurses etc.
I was about to snap a picture of Midnight Commander and post it here, but I don't have an Apache at the moment on my DSL box , so it will have to wait.
It seems that whateverev is responsible for terminal emulation is not emulating all codes properly and that it gets the physical byte length of some caracters incorrectly. This means that for example, after typing in a few characters, I can backspace_erase my bash prompt and similar nonsense...
This happens on almost all of my machine2-32-bit and 64-bit alike. I have tried reemerging many things, from kernel sources , through glibc and various other libraries,ncuses etc etc etc without success.

-somebody has suggested using vanilla-sorces. I am using them at the moment (2.6.13-rc3) but this is not recommended, since vanilla-kernel team does not worry about stability of everything in every release. It si up to distribution personnel to patch and polish vanilla-kernel into their official kernel. So this means that gentoo-sources should be used for kernel.

These are just a few of all aches that pest me...

MAL · n00b Joined: 15 Jan 2003 Posts: 7