From: Hendrik Boom <hendrik@pooq.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Do Debian's 2.6.18 problems exist in gentoo?
Date: Sat, 20 Jan 2007 17:27:28 -0500 [thread overview]
Message-ID: <pan.2007.01.20.22.27.27.259560@pooq.com> (raw)
I'm in the process of installing gentoo now, in the hope of getting it to
work more reliably (and more up-to-date) than Debian. Debian's 2.6.18-3
kernel includes backported msync-optimising patches from 2.19 that don't
work properly and have the effect of sometimes causing serious file-system
damage. (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401006 if
you're curious about gory details).
What I was wondering was whether a similar misfortune has befallen
gentoo's 2.6.18 kernel, or whether gentoo's kernel developers have just
left the 2.6.19 patches in 2.6.19.
Maybe I'm being silly asking about this, but I have become paranoid about
severe file system damage.
-- hendrik
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2007-01-21 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 22:27 Hendrik Boom [this message]
2007-01-21 2:09 ` [gentoo-user] Do Debian's 2.6.18 problems exist in gentoo? Nick Rout
2007-01-21 10:41 ` [gentoo-user] " Mick
2007-01-21 23:46 ` [gentoo-user] " Iain Buchanan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2007.01.20.22.27.27.259560@pooq.com \
--to=hendrik@pooq.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox