From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: [RFC][BTRFS-PROG] Avoid to scan cdrom and floppy
Date: 15 Jun 2011 22:35:00 +0200 [thread overview]
Message-ID: <Bnwmy4zD1uB@helmut.hullen.de> (raw)
In-Reply-To: <4DF9160A.4020102@libero.it>
Hallo, Goffredo,
Du meintest am 15.06.11:
> thanks to the last Hugo's email, I restart to work on the patch which
> avoid to scan cdrom and floppy during a "btrfs filesystem show" and a
> "btrfs device scan". Comparing to my previous patch I modified the
> strategy, and now the scan of the devices is based on the content of
> the file /proc/partitions. The old behavior may be set passing the
> "--all-devices" options.
Thank you - it's nice for all who don't use udev.
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-06-15 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 20:28 [RFC][BTRFS-PROG] Avoid to scan cdrom and floppy Goffredo Baroncelli
2011-06-15 20:35 ` Helmut Hullen [this message]
2011-06-16 14:14 ` Josef Bacik
2011-06-16 14:45 ` Helmut Hullen
2011-06-16 15:00 ` Josef Bacik
2011-06-16 15:09 ` Helmut Hullen
2011-06-16 20:07 ` Goffredo Baroncelli
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=Bnwmy4zD1uB@helmut.hullen.de \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--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;
as well as URLs for NNTP newsgroup(s).