From: Dave Chinner <david@fromorbit.com>
To: Jay Ashworth <jra@baylink.com>
Cc: xfs@oss.sgi.com
Subject: Re: A short digression on FOSS (Re: understanding speculative preallocation)
Date: Mon, 29 Jul 2013 12:41:05 +1000 [thread overview]
Message-ID: <20130729024105.GC13468@dastard> (raw)
In-Reply-To: <32553786.2492.1375056392388.JavaMail.root@benjamin.baylink.com>
On Sun, Jul 28, 2013 at 08:06:32PM -0400, Jay Ashworth wrote:
> ----- Original Message -----
> > From: "Dave Chinner" <david@fromorbit.com>
>
> > Sure, they have diverged signficant;y as we've backported various
> > bits of XFs fetaures and bug fixes back into RHEL6. As have every
> > other distro that doesn't track mainline directly. That's why you
> > need to look at the kernel source package to know what code the
> > distro is running.
>
> And... all the way back to Jason's original question:
>
> The way that you get the information out of a kernel/kernel RPM to
> determine which XFS version it's running... is? Cause it's clearly
> not obvious to either him or me.
The "version" of XFS that you are running is that of the
kernel you are running. i.e. 2.6.32-279.x.y or 2.6.32-358.x.y.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-07-29 2:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 7:23 understanding speculative preallocation jbr
2013-07-26 11:50 ` Dave Chinner
2013-07-26 17:40 ` Jason Rosenberg
2013-07-26 19:27 ` Stan Hoeppner
2013-07-26 19:43 ` A short digression on FOSS (Re: understanding speculative preallocation) Jay Ashworth
2013-07-27 3:52 ` Stan Hoeppner
2013-07-27 21:00 ` Jay Ashworth
2013-07-28 1:38 ` aurfalien
2013-07-28 1:50 ` Jay Ashworth
2013-07-28 2:08 ` aurfalien
2013-07-28 2:21 ` Jay Ashworth
2013-07-28 5:09 ` Purpose of the XFS list -- was: " Stan Hoeppner
2013-07-28 15:45 ` Jay Ashworth
2013-08-14 17:01 ` Emmanuel Florac
2013-07-28 7:18 ` Stefan Ring
2013-07-28 15:48 ` Jay Ashworth
2013-07-29 0:02 ` Dave Chinner
2013-07-29 0:06 ` Jay Ashworth
2013-07-29 2:41 ` Dave Chinner [this message]
2013-07-29 3:12 ` Eric Sandeen
2013-07-29 4:11 ` Stan Hoeppner
2013-07-29 14:33 ` Jay Ashworth
2013-07-29 15:25 ` Dave Howorth
2013-07-29 3:38 ` Keith Keller
2013-07-29 4:32 ` Eric Sandeen
2013-07-29 4:57 ` Keith Keller
2013-07-29 13:38 ` Eric Sandeen
2013-07-29 18:15 ` Keith Keller
2013-07-29 14:24 ` Jay Ashworth
2013-07-29 14:36 ` Jay Ashworth
2013-07-29 14:57 ` Eric Sandeen
2013-07-29 15:30 ` Jay Ashworth
2013-07-29 17:05 ` Eric Sandeen
2013-07-29 0:00 ` Dave Chinner
2013-07-28 5:15 ` Michael L. Semon
2013-07-26 20:38 ` understanding speculative preallocation Jason Rosenberg
2013-07-26 20:50 ` Ben Myers
2013-07-26 21:04 ` Jason Rosenberg
2013-07-26 21:11 ` Jason Rosenberg
2013-07-26 21:42 ` Ben Myers
2013-07-27 1:30 ` Dave Chinner
2013-07-28 2:19 ` Jason Rosenberg
2013-07-29 0:04 ` Dave Chinner
2013-07-26 21:45 ` Eric Sandeen
2013-07-27 4:26 ` Keith Keller
2013-07-27 1:26 ` Dave Chinner
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=20130729024105.GC13468@dastard \
--to=david@fromorbit.com \
--cc=jra@baylink.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox