From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Hugo Mills <hugo@carfax.org.uk>,
Calvin Walton <calvin.walton@kepstin.ca>,
"BTRFS, Linux" <linux-btrfs@vger.kernel.org>
Subject: Re: Another defrag question
Date: Thu, 21 Feb 2013 18:03:17 +0100 [thread overview]
Message-ID: <51265355.1020409@petaramesh.org> (raw)
In-Reply-To: <20130221163844.GD14283@carfax.org.uk>
Le 21/02/2013 17:38, Hugo Mills a écrit :
> Plus, if something does go wrong with your FS, and you're running an
> older kernel, you'll get limited amounts of sympathy, because quite a
> lot of the problems people encounter with older kernels have already
> been fixed in newer ones.
The matter, as usual, is that what may be a "new" kernel from a user's
standpoint, may be an "old" kernel from a developer's standpoint.
Should this exclude all standard users from developer's "sympathy", or
reduce it to very limited amounts ?
Users are supposed to use released material, not bleeding-edge
compile-it-yourself devs toys...
> Finally, Ubuntu publish the latest kernels in a PPA[1], so there's not
> really much excuse for not keeping up with them.
Yep. AFAIK the MAINLINE PPA is a Ubuntu-packaged STANDARD kernel without
any of the specific Ubuntu kernel patches.
That makes it very inappropriate for daily use, and the Ubuntu devs ask
for trying it ONLY when reporting kernel bugs, to check if said bug may
have been fixed upstream in latest kernel, or not.
Last time I tried this standard kernel, on one of my machines, it just
wouldn't boot ; on another one, it couldn't manage power (battery etc)
correctly, and on the machine on which I write this email, it couldn't
see my SD card reader anymore - for this one is managed by a driver
which still didn't make it into the standard kernel.
I use Ubuntu on several -dekstop- machines that benefit and need the
Ubuntu patches on their Ubuntus. I'm not (currently) running a headless
generic server for which my main and only concern would be BTRFS...
So I try to stick to the very old - albeit maximum 6 months old ! -
stock Ubuntu kernel...
Well... Sometimes I upgrade to next Beta :-]
Kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
Ne cherchez pas : Je ne suis pas sur Facebook.
next prev parent reply other threads:[~2013-02-21 17:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 15:46 Another defrag question Swâmi Petaramesh
2013-02-21 15:50 ` Liu Bo
2013-02-21 15:55 ` Swâmi Petaramesh
2013-02-21 15:54 ` Calvin Walton
2013-02-21 16:01 ` Swâmi Petaramesh
2013-02-21 16:09 ` Blair Zajac
2013-02-21 16:38 ` Hugo Mills
2013-02-21 17:03 ` Swâmi Petaramesh [this message]
2013-02-21 17:25 ` Hugo Mills
2013-02-21 17:47 ` Swâmi Petaramesh
2013-02-21 20:46 ` Hugo Mills
2013-02-21 20:58 ` Bardur Arantsson
2013-02-21 21:56 ` David Sterba
2013-02-22 5:55 ` Bardur Arantsson
2013-02-21 21:31 ` Johannes Hirte
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=51265355.1020409@petaramesh.org \
--to=swami@petaramesh.org \
--cc=calvin.walton@kepstin.ca \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.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