From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: INSTALL hint: create device btrfs-control
Date: 04 Aug 2011 20:35:00 +0200 [thread overview]
Message-ID: <BrDfNwli1uB@helmut.hullen.de> (raw)
In-Reply-To: <20110804173548.GA8970@carfax.org.uk>
Hallo, Hugo,
Du meintest am 04.08.11:
>> you should please add a hint in
>>
>> .../git/mason/btrfs-progs-unstable.git
>>
>> in the file "INSTALL" with at least the contents (please excuse my
>> gerlish)
>>
>> "btrfs" needs the device "btrfs-control". Perhaps you have to create
>> it:
>>
>> mknod /dev/btrfs-control c 10 234
> This should probably go in the problems FAQ [1] on the wiki
> instead, since (a) it's really a problem with your distribution, and
> (b) probably quite rare now that the majority of people are running
> distributions with udev.
Sorry - it's no problem of my distribution; slackware uses udev.
But I run/maintain a very special system, without udev, with most
modules integrated in the kernel etc. - it's for a special kind of
servers, not for end user workstations.
And I believe btrfs should run not only for "the majority of people"
without problems but also for systems which aren't "main stream".
> What are the symptoms of not having the device node? (i.e. how
> would I diagnose this particular problem?)
Please wait some hours (or days); I'll have to build a test system (I
won't change my running systems ...).
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-08-04 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 10:10 INSTALL hint: create device btrfs-control Helmut Hullen
2011-08-04 17:35 ` Hugo Mills
2011-08-04 18:35 ` Helmut Hullen [this message]
2011-08-04 20:13 ` Helmut Hullen
2011-08-04 20:42 ` Hugo Mills
2011-08-04 21:26 ` Helmut Hullen
2011-08-04 21:49 ` Hugo Mills
2011-08-05 5:43 ` Helmut Hullen
2011-08-05 10:19 ` 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=BrDfNwli1uB@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