From: Goffredo Baroncelli <kreijack@libero.it>
To: helmut@hullen.de
Cc: Helmut Hullen <Hullen@t-online.de>, linux-btrfs@vger.kernel.org
Subject: Re: minor ID for btrfs-control
Date: Sun, 03 Apr 2011 12:24:05 +0200 [thread overview]
Message-ID: <4D984AC5.3040207@libero.it> (raw)
In-Reply-To: <Bj8lm4ND1uB@helmut.hullen.de>
Hello Helmut,
On 04/03/2011 05:11 AM, Helmut Hullen wrote:
> Hallo, Goffredo,
[..]
>> As wrote by Tomasz the minor number of the btrfs-control is allocated
>> dynamically.
>
> At which place?
I replied you too fast. Btrfs register a "misc" device, but its number
is not dynamically allocated (see [1] for further information), but it
is static.
$ grep BTRFS_MINOR -r include/
include/linux/miscdevice.h:#define BTRFS_MINOR 234
I can conclude that _now_ the minor is 234 and not 55. But I don't know
if it is a _stable_ interface.
I think that during the boot you should check the minor with
grep btrfs-control /proc/misc | awk '{ print $1 }'
Regards
G.Baroncelli
[1] http://www.linuxjournal.com/article/2920
>
> Viele Gruesse!
> Helmut
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> .
>
next prev parent reply other threads:[~2011-04-03 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 16:45 minor ID for btrfs-control Helmut Hullen
2011-04-02 17:29 ` Tomasz Torcz
2011-04-02 18:06 ` Helmut Hullen
2011-04-03 9:42 ` Helmut Hullen
2011-04-03 12:28 ` Peter Stuge
2011-04-03 13:33 ` Helmut Hullen
2011-04-03 14:00 ` Peter Stuge
2011-04-03 14:33 ` Helmut Hullen
2011-04-02 22:35 ` Goffredo Baroncelli
2011-04-02 23:30 ` Peter Stuge
2011-04-03 4:12 ` Helmut Hullen
2011-04-03 3:11 ` Helmut Hullen
2011-04-03 10:24 ` Goffredo Baroncelli [this message]
2011-04-03 10:52 ` Helmut Hullen
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=4D984AC5.3040207@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).