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: 16 Jun 2011 16:45:00 +0200 [thread overview]
Message-ID: <Bn+ojsGi1uB@helmut.hullen.de> (raw)
In-Reply-To: <4DFA0FD7.8010908@redhat.com>
Hallo, Josef,
Du meintest am 16.06.11:
>> Thank you - it's nice for all who don't use udev.
> Who the hell doesn't use udev?
Me - p.e.
"udev" may be interesting for desktop users, for multimedia computers.
It's not necessary for a simple server, for a machine where the
administrator wants to rule instead of "udev".
If the developers of "btrfs" really do mean that "udev" has to run on
the machine which uses "btrfs" then they have to say so, and they have
to check wether this (possible) condition is redeemed.
Not only in the "devices" environment.
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-06-16 14:45 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
2011-06-16 14:14 ` Josef Bacik
2011-06-16 14:45 ` Helmut Hullen [this message]
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=Bn+ojsGi1uB@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.