* btrfs development git tree
@ 2010-01-08 12:41 Simon Schubert
2010-01-08 16:37 ` /dev/btrfs-control Michael Niederle
2010-01-09 0:57 ` btrfs development git tree Liuwenyi
0 siblings, 2 replies; 4+ messages in thread
From: Simon Schubert @ 2010-01-08 12:41 UTC (permalink / raw)
To: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
Hey,
I apologize for this ignorant question upfront, but:
Where can I find a current btrfs git repo? The one linked from the wiki
(I think cmason's unstable tree) did not update in the last 3 weeks, and
I don't think nothing happened since then. Maybe the wiki could list
also alternative repos from other developers?
thanks
simon
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* /dev/btrfs-control
2010-01-08 12:41 btrfs development git tree Simon Schubert
@ 2010-01-08 16:37 ` Michael Niederle
2010-01-08 18:54 ` /dev/btrfs-control Kay Sievers
2010-01-09 0:57 ` btrfs development git tree Liuwenyi
1 sibling, 1 reply; 4+ messages in thread
From: Michael Niederle @ 2010-01-08 16:37 UTC (permalink / raw)
To: linux-btrfs
Some btrfs-tools make use of "/dev/btrfs-control".
How should I create this node? Is this a block or a character device (I suppose
it should be a character device), which major and minor numbers should be
assigned?
I do not use udev, so I have to create all device nodes "by hand" or "by
script".
I started using btrfs with the arrival of kernel 2.6.32 - no problems until
now! :-) I'm very interested in using its snapshot feature. Currently I'm not
able to mount a snapshot (subvolume), but this might be connected to the
missing device-node.
Thanks in advance for any help,
Michael
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: /dev/btrfs-control
2010-01-08 16:37 ` /dev/btrfs-control Michael Niederle
@ 2010-01-08 18:54 ` Kay Sievers
0 siblings, 0 replies; 4+ messages in thread
From: Kay Sievers @ 2010-01-08 18:54 UTC (permalink / raw)
To: Michael Niederle; +Cc: linux-btrfs
On Fri, Jan 8, 2010 at 17:37, Michael Niederle <mniederle@gmx.at> wrote:
> Some btrfs-tools make use of "/dev/btrfs-control".
>
> How should I create this node? Is this a block or a character device (I suppose
> it should be a character device), which major and minor numbers should be
> assigned?
It's a char device node:
$ cat /sys/class/misc/btrfs-control/dev
10:62
Kay
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: btrfs development git tree
2010-01-08 12:41 btrfs development git tree Simon Schubert
2010-01-08 16:37 ` /dev/btrfs-control Michael Niederle
@ 2010-01-09 0:57 ` Liuwenyi
1 sibling, 0 replies; 4+ messages in thread
From: Liuwenyi @ 2010-01-09 0:57 UTC (permalink / raw)
To: Simon Schubert; +Cc: linux-btrfs
=E4=BA=8E 2010-1-8 20:41, Simon Schubert =E5=86=99=E9=81=93:
> Hey,
>
> I apologize for this ignorant question upfront, but:
>
> Where can I find a current btrfs git repo? The one linked from the w=
iki
> (I think cmason's unstable tree) did not update in the last 3 weeks, =
and
> I don't think nothing happened since then. Maybe the wiki could list
> also alternative repos from other developers?
>
> thanks
> simon
>
> =20
Maybe there is no suitable patch accepted by community.
You can search the maillist in past 3 weeks or more and find it out.
--=20
Best Regards,
Liuwenyi
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-01-09 0:57 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-08 12:41 btrfs development git tree Simon Schubert
2010-01-08 16:37 ` /dev/btrfs-control Michael Niederle
2010-01-08 18:54 ` /dev/btrfs-control Kay Sievers
2010-01-09 0:57 ` btrfs development git tree Liuwenyi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox