Author Topic: [Solved] Why 2.6.32 kernel as default, not 2.6.33  (Read 819 times)

Offline fishfillet

  • Full Member
  • ***
  • Posts: 221
[Solved] Why 2.6.32 kernel as default, not 2.6.33
« on: April 16, 2010, 04:56:02 AM »
Pardon me if this was already answered somewhere...

I am just curious why did Texstar choosed 2.6.32 as the default kernel instead of 2.6.33.

Any reasons?

At any rate, I love the bfs versions. :)
« Last Edit: April 18, 2010, 02:52:07 PM by Texstar »

Offline Texstar

  • Administrator
  • Super Villain
  • *****
  • Posts: 12490
Re: Why 2.6.32 kernel as default, not 2.6.33
« Reply #1 on: April 16, 2010, 05:02:55 AM »
Feedback from the beta testers said it had more issues than with 2.6.32.11.  It doesn't work with VMWare, speakers don't mute when headset plugged in...etc. You can always update to the 2.6.33.2 kernel from the repository.


Thanks to everyone who donates. You keep the servers running.

Offline fishfillet

  • Full Member
  • ***
  • Posts: 221
Re: Why 2.6.32 kernel as default, not 2.6.33
« Reply #2 on: April 16, 2010, 05:41:43 AM »
Feedback from the beta testers said it had more issues than with 2.6.32.11.  It doesn't work with VMWare, speakers don't mute when headset plugged in...etc. You can always update to the 2.6.33.2 kernel from the repository.


Thank you sir, for the prompt reply.

Offline fishfillet

  • Full Member
  • ***
  • Posts: 221
Re: Why 2.6.32 kernel as default, not 2.6.33
« Reply #3 on: April 16, 2010, 05:44:10 AM »
I hope this is allowed....

Does the .pae and .a64 kernels also use BFS?   Or just the .bfs?

alexjamestodd

  • Guest
Re: Why 2.6.32 kernel as default, not 2.6.33
« Reply #4 on: April 16, 2010, 08:19:57 AM »
downloaded new mini me and the difference with the new kernel is astonashingly good.

Offline MaddogF16

  • Hero Member
  • *****
  • Posts: 2711
Re: Why 2.6.32 kernel as default, not 2.6.33
« Reply #5 on: April 16, 2010, 10:24:14 AM »
The .32 series kernel is going to be kept up with updates for longer than the .33 series.
Why?