linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Torcz <tomek@pipebreaker.pl>
To: linux-btrfs@vger.kernel.org
Subject: Re: minor ID for btrfs-control
Date: Sat, 2 Apr 2011 19:29:36 +0200	[thread overview]
Message-ID: <20110402172936.GA24370@mother.jarsat.pl> (raw)
In-Reply-To: <Bj4lB4gT1uB@helmut.hullen.de>

On Sat, Apr 02, 2011 at 06:45:00PM +0200, Helmut Hullen wrote:
> if I've understood some mails in this list correct, then btrfs needs a  
> character device "btrfs-control"  with the ID 10:55
> 
> When I look for this device in
> 
>         /sys/class/misc/btrfs-control/dev
> 
> I see 10:234
> Kernel 2.6.38.1 (self made), no udev, no initrd, no tempfs. btrfs from  
> nov. 2010
> What goes wrong?


  No udev is wrong.  Modern Linux kernels allocate minor devices dynamically.
If you do not use udev, you need to synchronise /dev/ node with /sys/class/misc/btrfs-control/dev
manually on each boot.

-- 
Tomasz Torcz       ,,(...) today's high-end is tomorrow's embedded processor.''
xmpp: zdzichubg@chrome.pl                      -- Mitchell Blank on LKML


  reply	other threads:[~2011-04-02 17:29 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 [this message]
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
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=20110402172936.GA24370@mother.jarsat.pl \
    --to=tomek@pipebreaker.pl \
    --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).