Re:why is this news?
by
jfmiller
·
· Score: 5, Insightful
Normally I just lurk but I feel the need to disagree with Mr. Grimes.
I like many who read Slashdot am a linux enthusiast. I appriciate having a place where my OS of choice is reported on with the zeal and timeliness that Microsoft gets in the main stream press. Slashdot is one of the few sights I read on a daily basis, and I for one appriciate hearing about the new kernels. along with the rest of the pertinante Tech news.
My local paper still lists The High School football team's results on the front page every Saturday during the fall, even though most of it's readers dont have kids on the HS football team. It builds a sence of community pride wich is greater than the information that is contained or it's relevance to peoples lives.
Kernel anouncements on slashdot are appriciated by me and I hope a great many other readers. And even if there are only a few of us Linux is one of the things that form Slashdot's Community, and therefore in the interest of Community pride I encourage CT to continue to post all the kernel updates.
JFMILLER
-- Strive to make your client happy, not necessarly give them what they ask for
Re:Changes/Improvements
by
brer_rabbit
·
· Score: 5, Insightful
The ChangeLog definitely needs some verbosity. The word to the wise is "only update if you need to", yet viewing the changelog leaves one wondering if they need the newer software.
What exactly do entries like "shrink dcache/icache more aggressively" or "random bugfix" mean? The former I'd guess has to do with data and instruction caches, but what aggressively shrinking does to them I have no clue without a more context. And the latter, "random bugfix", I hit my coworkers over the head when I see that in our CVS logs.
So is my current kernel effected? Am I missing out by not having my dcache/icache shrunk more aggressively? Or maybe those random bufixes effect me? A little more verbosity in the ChangeLog would go a long way. Having to follow the hacker's mailing list is not an option, this should be included in the release notes.
Re:call it what it is
by
Arandir
·
· Score: 5, Insightful
Linus really, really, REALLY needs to start the 2.5.x branch.
Stable branches need to be stable. Do all of the new feature experimentation in unstable. It's gotten to the point now that "stable" has become a meaningless word in linuxland.
Next time around, let's fork off 2.7.0 at the same time 2.6.2 is released. Or maybe Linux needs to split into three branches: "flimsy" for experimentation and VM wars, "unstable" for up-to-date hardware support but no new features, and "stable" which only gets bug and security fixes.
-- A Government Is a Body of People, Usually Notably Ungoverned
New ./ feature idea
by
Atilla
·
· Score: 5, Insightful
Ok, how about this -
maybe major kernel release posts should go in their own category, so whiners could set their user prefs to not display them.
Slashdot Mirror
Normally I just lurk but I feel the need to disagree with Mr. Grimes.
I like many who read Slashdot am a linux enthusiast. I appriciate having a place where my OS of choice is reported on with the zeal and timeliness that Microsoft gets in the main stream press. Slashdot is one of the few sights I read on a daily basis, and I for one appriciate hearing about the new kernels. along with the rest of the pertinante Tech news.
My local paper still lists The High School football team's results on the front page every Saturday during the fall, even though most of it's readers dont have kids on the HS football team. It builds a sence of community pride wich is greater than the information that is contained or it's relevance to peoples lives.
Kernel anouncements on slashdot are appriciated by me and I hope a great many other readers. And even if there are only a few of us Linux is one of the things that form Slashdot's Community, and therefore in the interest of Community pride I encourage CT to continue to post all the kernel updates.
JFMILLER
Strive to make your client happy, not necessarly give them what they ask for
The ChangeLog definitely needs some verbosity. The word to the wise is "only update if you need to", yet viewing the changelog leaves one wondering if they need the newer software.
What exactly do entries like "shrink dcache/icache more aggressively" or "random bugfix" mean? The former I'd guess has to do with data and instruction caches, but what aggressively shrinking does to them I have no clue without a more context. And the latter, "random bugfix", I hit my coworkers over the head when I see that in our CVS logs.
So is my current kernel effected? Am I missing out by not having my dcache/icache shrunk more aggressively? Or maybe those random bufixes effect me? A little more verbosity in the ChangeLog would go a long way. Having to follow the hacker's mailing list is not an option, this should be included in the release notes.
Linus really, really, REALLY needs to start the 2.5.x branch.
Stable branches need to be stable. Do all of the new feature experimentation in unstable. It's gotten to the point now that "stable" has become a meaningless word in linuxland.
Next time around, let's fork off 2.7.0 at the same time 2.6.2 is released. Or maybe Linux needs to split into three branches: "flimsy" for experimentation and VM wars, "unstable" for up-to-date hardware support but no new features, and "stable" which only gets bug and security fixes.
A Government Is a Body of People, Usually Notably Ungoverned
Ok, how about this -
maybe major kernel release posts should go in their own category, so whiners could set their user prefs to not display them.
--- sig moved for great justice.