From: Goffredo Baroncelli <kreijack@libero.it>
To: helmut@hullen.de
Cc: Helmut Hullen <Hullen@t-online.de>, linux-btrfs@vger.kernel.org
Subject: Re: [RFC][BTRFS-PROG] Avoid to scan cdrom and floppy
Date: Thu, 16 Jun 2011 22:07:53 +0200 [thread overview]
Message-ID: <4DFA6299.3040904@libero.it> (raw)
In-Reply-To: <Bn+os9hi1uB@helmut.hullen.de>
Hi Helmut
On 06/16/2011 05:09 PM, Helmut Hullen wrote:
> Hallo, Josef,
>
> Du meintest am 16.06.11:
>
>>>> 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".
>
>> You don't need udev to use btrfs, I've just not seen a distro that
>> allows you to not run with udev, so my question is more curiosity
>> than anything.
>
> But the developers seem to use only machines where "udev" runs.
>
> p.e. when testing the disks (I've told this bug about 1 year ago), p.e.
> with "/dev/btrfs-control".
>
> "btrfs-control" has to exist before btrfs is started, and there is
> neither a hint in the documentation nor a check.
>
Sorry Helmut, but I don't understand if you are blaming about lack of
documentation or about a problem.
The fact that the file /dev/btrfs-control doesn't exist, is not a
bug/problem of btrfs. This file should be created by the distribution:
or via the udev or via devtmpfs or statically. In this is not different
by any other device (like /dev/sdaX for example). They have to exists
before mounting the root-filesystem.
BR
G.Baroncelli
prev parent reply other threads:[~2011-06-16 20:07 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
2011-06-16 15:00 ` Josef Bacik
2011-06-16 15:09 ` Helmut Hullen
2011-06-16 20:07 ` Goffredo Baroncelli [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=4DFA6299.3040904@libero.it \
--to=kreijack@libero.it \
--cc=Hullen@t-online.de \
--cc=helmut@hullen.de \
--cc=kreijack@inwind.it \
--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).