Re: [SuSE Linux] 2.2.5 ->2.2.9
lunaslide <lunaslide@pacbell.net> writes:
Remember to comment out the lines in /sbin/init.d/boot that start "update (bdflush)" Since 2.2.8(?), this daemon is no longer necessary.
NO!! do NOT do that for kernel 2.2.9! It was because the code in 2.2.8 which did this had serious bugs, which could cause filesytem corruption, that 2.2.9 came out so quickly after 2.2.8. 2.2.9 no longer has this "feature", so you should still be running the update daemon. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Graham Murray wrote:
lunaslide <lunaslide@pacbell.net> writes:
Remember to comment out the lines in /sbin/init.d/boot that start "update (bdflush)" Since 2.2.8(?), this daemon is no longer necessary.
NO!! do NOT do that for kernel 2.2.9!
It was because the code in 2.2.8 which did this had serious bugs, which could cause filesytem corruption, that 2.2.9 came out so quickly after 2.2.8. 2.2.9 no longer has this "feature", so you should still be running the update daemon.
Why then does it mention this as a note in the 2.2.9 patch notes? Perhaps you could elaborate, as I do not fully understand the change and was going by the suggestion in the kernel notes. Should I be running this daemon or not? -- lunaslide * PGP key->pgpkeys.mit.edu port 11371 * * * * * * My advice to you is just be lucky. Go out there and buy low and sell high, and everything will be fine.* -Ken Thompson * * * * * -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
lunaslide wrote:
Graham Murray wrote:
lunaslide <lunaslide@pacbell.net> writes:
Remember to comment out the lines in /sbin/init.d/boot that start "update (bdflush)" Since 2.2.8(?), this daemon is no longer necessary.
NO!! do NOT do that for kernel 2.2.9!
It was because the code in 2.2.8 which did this had serious bugs, which could cause filesytem corruption, that 2.2.9 came out so quickly after 2.2.8. 2.2.9 no longer has this "feature", so you should still be running the update daemon.
Why then does it mention this as a note in the 2.2.9 patch notes? Perhaps you could elaborate, as I do not fully understand the change and was going by the suggestion in the kernel notes. Should I be running this daemon or not?
The best solution for these problem is to update the updated (bdflush) package to version 2.11 (24.05.99).
Henning wrote:
lunaslide wrote:
Graham Murray wrote:
lunaslide <lunaslide@pacbell.net> writes:
Remember to comment out the lines in /sbin/init.d/boot that start "update (bdflush)" Since 2.2.8(?), this daemon is no longer necessary.
NO!! do NOT do that for kernel 2.2.9!
It was because the code in 2.2.8 which did this had serious bugs, which could cause filesytem corruption, that 2.2.9 came out so quickly after 2.2.8. 2.2.9 no longer has this "feature", so you should still be running the update daemon.
Why then does it mention this as a note in the 2.2.9 patch notes? Perhaps you could elaborate, as I do not fully understand the change and was going by the suggestion in the kernel notes. Should I be running this daemon or not?
The best solution for these problem is to update the updated (bdflush) package to version 2.11 (24.05.99).
From the lsm:
This version does not spawn a bdflush daemon, as this is now done by the kernel (kflushd). It will exit silently on newer kernels that do not need its services.
Sources at <A HREF="http://metalab.unc.edu/pub/Linux/system/daemons"><A HREF="http://metalab.unc.edu/pub/Linux/system/daemons</A">http://metalab.unc.edu/pub/Linux/system/daemons</A</A>> No rpm. But it compiles within seconds.
Henning
It's "back-and-forth", "no-yes-no" controversies like this one that make me glad that I am waiting for SuSE's next release.... ;-) -- JLK Linux, because it's STABLE, the source code is included, the price is right. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Henning <hhv@hhv.de> writes:
The best solution for these problem is to update the updated (bdflush) package to version 2.11 (24.05.99).
From the lsm:
This version does not spawn a bdflush daemon, as this is now done by the kernel (kflushd). It will exit silently on newer kernels that do not need its services.
And it is interesting to read the source file which states that the new behaviour was in 2.2.8 but was backed out in 2.2.9, which seems to support my original caution. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Graham Murray wrote:
And it is interesting to read the source file which states that the new behaviour was in 2.2.8 but was backed out in 2.2.9, which seems to support my original caution.
Yep. That's correct. Henning -- H. Henning Vossieck - hhv@hhv.de - <A HREF="http://hhv.de/"><A HREF="http://hhv.de/</A">http://hhv.de/</A</A>> SuSE Linux 6.0+ Kernel 2.3.4-109 glibc 2.1.1 egcs 1.1.2 -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (4)
-
graham＠barnowl.demon.co.uk -
hhv＠hhv.de -
jlkreps＠navix.net -
lunaslide＠pacbell.net