2.5.4 Kernel Out

Saint Aardvark writes: "Just in time for my 30th birthday, the new kernel is out...how did he know? Thanks, Linus! Change log here. I usually stick to stable stuff, but I think I'll try this for fun." Reader Scooby Snacks writes: "Be sure to use the patches and pick from the fine list of mirrors."

Comments

New Topic Please

[Dredd13]

Can we have a topic "Linux-Kernel-Release", so that those of us who care about "Linux news" (and so don't want to check-to-exclude the "Linux" topic) can still send these Freshmeat-intended stories to /dev/null where they belong?

Re:New Topic Please

[Dredd13]

I don't think I was trolling at all, I'm actually really sick of having to wade through kernel announcements.

.0's are newsworthy

.FINAL_VERSION's are newsworthy

.PATCH_OF_THE_WEEK's are not "Stuff that matters" for the majority of folks out there. If you ARE one of the folks that it matters for, chances are you're monitoring the kernel.org site already.

Just my $0.02 worth anyhow....

Re:New Topic Please

[hal200]

I'm not trying to troll here, but I don't get it. Maybe it's just me, but is it really so onerous to read a headline and move on if you're not interested? (Just to go on the record though, I happen to like the Kernel X.Y.Z is out! news items.)

Are you paying for your desktop real estate by the pixel or something?

I rather effectively screen out JonKatz by reading the headline, and seeing the big green JonKatz underneath. Then I know it's drivel and I move on.

I just don't understand the motivation behind, "I should be able to filter this out!"...It's not like they're forcing you to read the article and all the comments. Just move along if it doesn't pique your interest. Considering how many stories flit past the front page in a day (and more with judicious use of Slashboxes), it's not hard to find something more personally interesting.

Then again, maybe I'm just being obtuse. Anyone care to enlighten me?

[OT] Re:New Topic Please

[Psiren]

Moderators, this isn't a troll. Enough complaints have been made about this over time for it to be a justified request.

There are those of use who do want to read Linux stories, but don't want to know about every release of the kernel. It's not as if theres a shortage of sites that have that information.

Yeah, but

[wiredog]

Some of us use slashdot as a central news source. Why go around to a zillion other places, when we can just catch the announce here? Saves time.

Re:Yeah, but

[Dredd13]

And if there was a separate "LinuxKernelReleases" topic, both of us would be happy. you could get your "news" (which I don't consider news, but that's here nor there), and myself (and others) could simply check that box to say "Don't show me these stories".

And life would be happy all around. See how nice that'd work if TPTB @ /. would just use the Slash engine the way it's designed to work? :-)

D

I'm sick of it...

[__aahlyu4518]

Sick of these minor release announcements on development branch kernels... Not because of the announcement itself, but because of all the people yelling and screaming that they don't want to know about it... Stop bitching and skip the article and move on and leave the thread clean for those that DO like to read about it and read INTERESTING comments...

Re:Collective scream...

[Kynde]

8:40 - start compiling, so far so good

...and that's as far as you'd get on an x86. Although those _actually_ interested in developement kernels would have no trouble locating a suitable patch posted to kernel mailing list by Andrew Morton.

Also vesa frame buffers users will have difficulties linking it together, because of few bus_to_virt instead of phys_to_virt

(Patches for the x86 headers below...)

--- linux-2.5.4/include/asm-i386/processor.h Sun Feb 10 22:00:29 2002
+++ 25/include/asm-i386/processor.h Sun Feb 10 22:21:53 2002
@@ -435,14 +435,7 @@ extern int kernel_thread(int (*fn)(void
/* Copy and release all segment info associated with a VM */
extern void copy_segments(struct task_struct *p, struct mm_struct * mm);
extern void release_segments(struct mm_struct * mm);
-
-/*
- * Return saved PC of a blocked thread.
- */
-static inline unsigned long thread_saved_pc(struct task_struct *tsk)
-{
- return ((unsigned long *)tsk->thread->esp)[3];
-}
+extern unsigned long thread_saved_pc(struct task_struct *tsk);

unsigned long get_wchan(struct task_struct *p);
#define KSTK_EIP(tsk) (((unsigned long *)(4096+(unsigned long)(tsk)->thread_info))[1019])
--- linux-2.5.4/arch/i386/kernel/process.c Sun Feb 10 22:00:28 2002
+++ 25/arch/i386/kernel/process.c Sun Feb 10 22:26:35 2002
@@ -55,6 +55,14 @@ asmlinkage void ret_from_fork(void) __as
int hlt_counter;

/*
+ * Return saved PC of a blocked thread.
+ */
+unsigned long thread_saved_pc(struct task_struct *tsk)
+{
+ return ((unsigned long *)tsk->thread.esp)[3];
+}
+
+/*
* Powermanagement idle function, if any..
*/
void (*pm_idle)(void);