Slashdot Mirror
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."
If the open source/Linux development holds up on this one, with any luck, there will only be 220 more notices before we see 2.6.0. Yay!
The whole premise of slashdot is to post news articles (and I use the term news lightly), and then people discuss the article (and troll).
Just what do the slashdot janitors expect us to say after the 10th or 20th kernel announcement? There's not much to say, that hasn't been said 10 or 20 times before.
If there is an excess of trolling, it's because The Janitors aren't thinking clearly, when deciding news articles. They're so worried about their precious little Linux, that they'd rather post crap about it, then find something that with a little more substance.
That is why none of them will ever be serious journalists. That and because, collectively, they have about 1/20th of a brain - and 1/40th of a penis.
The BitKeeper works, and this release is here to show us.
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.
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.
Best Slashdot Co
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...
I have actually been using this one for months on a 2.4.16 kernel tree.
The pre-empt kernel patch is actually the most interesting feature in Linux as it suddenly turns a server OS with a sluggish UI into a really responsive workstation with still impressive network performance.
So it is quite good news to hear that it will be possible to determine whether we want our kernel user or services oriented by just checking a box in the Linux-compilation-tcl box.
Trolling using another account since 2005.
I'm glad to see a change Log that I can understand!.
I's detailed and clear.
I'm from Argentina: Tango, Asado, Mate, Gaucho, Maradona, YPF
8:40 - start compiling, so far so good
/* Copy and release all segment info associated with a VM */
/*
...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
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);
1 Earth is warming, 2 It's us, 3 it's royally bad, 4 we need to take action NOW
Although most people use the term 'Linux' for the operating System as a whole it really only the name of the Kernel. Would we call it 'Hurd' if we ran it with a hurd-Kernel? No, we probably talk about 'Linux with a Hurd-kernel' or somesuch, which is funny enough (maybe it should be 'GNU/Hurd' or just 'GNU' then). In that light (Linux being really just the name of the kernel) news about new kernelversions are very appropriate under this topic, what more interesting could there be under the 'Linux' topic, than something about a new Version of 'Linux'?
...). The term 'Linux-kernel' is redundant, and thus really not a good topic.
So if we want to keep the terms right (and those who always complain about the use of the term hacker in a wrong context know we should) maybe there should be another topic 'GNU/Linux' or 'LinuxOS' (and also 'LinuxAPPS'?) to comfort those who want to read about Linux, but not about the kernel (so actually not about 'Linux'
I also wonder, how one can be interested in Operating systems based on the Linux kernel, without being interested in the development of the kernel itself (especially the unstable versions, since there is much more happening), and for a lot of readers the 'new kernel' news is the place to discuss these developments. So if you want to vent your complaints, that hardware x isn't supported, why patch y didn't make it in, express your happiness that z works now (z preferably being the VM), or just have a question these stories are the place to go. The kernel is the thing that all those LinuxOSes, LinuxDevices and whatnot have in common, and if you're interested in Linux on your Palm, or maybe in your coffee-machine, then you should be interested in the kerneldevelopment, since without a kernel allowing to be shrinked down to that size it's just not possible. If you're interested in 'Linux' running on big iron, like n-Processor machines, well, it's really the kernel and its development that makes it possible.
And finally, if you're really not interested in kernel development, it's not that hard to spot, that a story is about the new kernel, just ignore it, and be happy, these storys are there, because if they weren't people would just post things about new kernel developments in other Linux-stories (even if slightly offtopic).
--
"By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks