Andrej Podzimek wrote:
1) Btrfs does not have mature and user-friendly command-line
tools. AFAIK, you can only list your snapshots and subvolumes by
grep'ing the tree dump. ;-)
I haven't looked closely at the btrfs commands recently, but from what I've
seen, they're really amazingly
On Sat, Jul 17, 2010 at 12:57:40AM +0200, Richard Elling wrote:
Because of BTRFS for Linux, Linux's popularity itself and also thanks
to the Oracle's help.
BTRFS does not matter until it is a primary file system for a dominant
distribution.
From what I can tell, the dominant Linux
On Mon, Jul 19, 2010 at 3:31 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
Upcoming Ubuntu 10.10 will use BTRFS as a default.
Though there was some discussion around this, I don't think the above
is a given. The ubuntu devs would look at the status of the project,
and decide closer to the release.
Ubuntu always likes to be on the edge even if btrfs is far from being
'stable' I would not want to run a release that does this. Servers need
stability and reliability. Btrfs is far from this.
Well, it seems to me that this is a well-known and very popular „circle in
proving“:
A: XYZ is far
On 07/19/10 07:26, Andrej Podzimek wrote:
I run ArchLinux with Btrfs and OpenSolaris with ZFS. I haven't had a
serious issue with any of them so far.
Moblin/Meego ships with btrfs by default. COW file system on a
cell phone :-). Unsurprisingly for a read-mostly file system it
seems pretty
On 16/07/2010 23:57, Richard Elling wrote:
On Jul 15, 2010, at 4:48 AM, BM wrote:
2. No community = stale outdated code.
But there is a community. What is lacking is that Oracle, in their infinite
wisdom, has stopped producing OpenSolaris developer binary releases.
Not to be
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Pasi Kärkkäinen
Redhat Fedora 13 includes BTRFS, but it's not used as a default (yet).
RHEL6 beta also includes BTRFS support (tech preview), but again,
Upcoming Ubuntu 10.10 will use
On Jul 15, 2010, at 4:48 AM, BM wrote:
On Thu, Jul 15, 2010 at 10:53 AM, Garrett D'Amore garr...@nexenta.com wrote:
The *code* is probably not going away (even updates to the kernel).
Even if the community dies, is killed, or commits OGB induced suicide.
1. You used correct word: probably.
