Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: kreijack@libero.it
Cc: linux-btrfs@vger.kernel.org, stewart@flamingspork.com
Subject: Re: [RFC] aptitude & BTRFS slowness
Date: Thu, 20 Oct 2011 09:51:48 +0600	[thread overview]
Message-ID: <20111020095148.0886b181@natsu> (raw)
In-Reply-To: <3728579.PMSEXudObp@venice>

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]

On Wed, 19 Oct 2011 23:24:59 +0200
Goffredo Baroncelli <kreijack@libero.it> wrote:

>         export LD_PRELOAD=/usr/lib/libeatmydata/libeatmydata.so
>         aptitude

Why not simply run

>         eatmydata aptitude


-- 
With respect,
Roman

~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2011-10-20  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 21:24 [RFC] aptitude & BTRFS slowness Goffredo Baroncelli
2011-10-20  3:51 ` Roman Mamedov [this message]

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=20111020095148.0886b181@natsu \
    --to=rm@romanrm.ru \
    --cc=kreijack@libero.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stewart@flamingspork.com \
    /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