From: Richard Weinberger <richard@nod.at>
To: Kyle Moffett <kyle@moffetthome.net>
Cc: Valdis.Kletnieks@vt.edu, mfasheh@suse.com, jlbec@evilplan.org,
ocfs2-devel@oss.oracle.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
license-violation@gpl-violations.org
Subject: Re: OCFS2 1.6.0 for mainline?
Date: Sat, 15 Oct 2011 23:12:44 +0200 [thread overview]
Message-ID: <4E99F74C.80900@nod.at> (raw)
In-Reply-To: <CAGZ=bqJb5FGJe264TOtfuzm8dyvWO883NFBnzkyA4M6Fe7Nq_g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
Am 15.10.2011 23:03, schrieb Kyle Moffett:
> On Sat, Oct 15, 2011 at 15:26, <Valdis.Kletnieks@vt.edu> wrote:
>> On Sat, 15 Oct 2011 19:49:43 +0200, Richard Weinberger said:
>>> Am 15.10.2011 19:45, schrieb Valdis.Kletnieks@vt.edu:
>>>> Put differently, why do you think 1.6.0 is available?
>>
>>> OCFS2 1.6.3-1 and OCFS2 Tools 1.6.3-1 are the latest versions. The new
>>> features available in this release include Extended Attributes, POSIX
>>> ACLs, REFLINKs, Indexed Directories, Allocation Reservation, Metadata
>>> Checksums and User/Group Quotas."
>>
>> Nice feature list, I can see why you want it. ;)
>>
>>> Looks like it's only available for "Unbreakable Linux" subscribers.
>>> The development seems to be detached from mainline. :-(
>>
>> Well, you have to admit it *is* an interesting business model - giving release
>> N to your customers and N-1 to the world. I just got totally mislead by the
>> quote from the Oracle site that said the development happens in mainline. ;)
>
> If someone who has a copy of Oracle's "Unbreakable Linux" can get
> ahold of the sources, please put them in GIT somewhere for the rest of
> us to access; it *is* GPLed software after all. Otherwise, please
> distribute the binaries to the rest of us and we will obtain the
> sources on our own. I can't find any published information on their
> website about how to obtain the sources, so someone will have to
> contact them directly.
I found this src.rpm:
http://public-yum.oracle.com/repo/OracleLinux/OL6/1/base/x86_64/kernel-uek-2.6.32-100.34.1.el6uek.src.rpm
linux-2.6.32/fs/ocfs2 contains OCFS2 1.6.3.
Mark, Joel, can you please port this "release" to mainline?
Thanks,
//richard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-10-15 21:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 15:38 OCFS2 1.6.0 for mainline? Richard Weinberger
2011-10-15 17:45 ` Valdis.Kletnieks
2011-10-15 17:49 ` Richard Weinberger
2011-10-15 19:26 ` Valdis.Kletnieks
2011-10-15 21:03 ` Kyle Moffett
2011-10-15 21:12 ` Richard Weinberger [this message]
2011-10-15 21:25 ` Valdis.Kletnieks
2011-10-17 17:16 ` Mark Fasheh
2011-11-09 7:55 ` [Ocfs2-devel] " Joel Becker
2011-11-09 7:55 ` Joel Becker
2011-11-09 9:47 ` Richard Weinberger
2011-10-15 17:50 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2011-10-16 14:20 Xose Vazquez Perez
2011-10-16 14:55 Xose Vazquez Perez
2011-10-16 17:40 ` Sasha Levin
2011-10-16 22:07 ` Xose Vazquez Perez
2011-10-16 22:44 ` richard -rw- weinberger
2011-10-16 23:24 ` Sasha Levin
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=4E99F74C.80900@nod.at \
--to=richard@nod.at \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jlbec@evilplan.org \
--cc=kyle@moffetthome.net \
--cc=license-violation@gpl-violations.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.