public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jay Ashworth <jra@baylink.com>
To: xfs@oss.sgi.com
Subject: Re: A short digression on FOSS (Re: understanding speculative preallocation)
Date: Sat, 27 Jul 2013 22:21:34 -0400 (EDT)	[thread overview]
Message-ID: <31450470.2412.1374978094689.JavaMail.root@benjamin.baylink.com> (raw)
In-Reply-To: <52C3E9E6-61DD-4537-9A64-C8CBFC86F6E3@gmail.com>

----- Original Message -----
> From: "aurfalien" <aurfalien@gmail.com>

> If it RHEL/CentOS really is the only option, then perhaps get one box
> on RHEL and submit bugs for it.

Sure, but "submit bugs" was a straw man the entire time  The OP wasn't talking
about how and where to submit bugs, and neither was I.

The OP was trying to determine how he got from Distro/Kernel Version to
XFS checkout ID, so that he could *talk to the XFS devs* about his problem.

And no one had a straight answer for him, which straight answer *is*:

"You have to talk to whomever builds the kernel packages for the distro 
you're working on; they should be able to tell you which XFS {version|
release|checkout} is built into that particular kernel RPM."

>From there, we veered *very* close to "we don't talk to people unless 
they're paying Red Had customers", and I'm relatively certain that was
*not* the takeaway Dave was aiming for with us.

Those kernel packagers *should* (be able to) tell the XFS people those answers
off hand.  If I were a developer on a major kernel subsystem project where
that actually mattered, I think I'd probably get with the kernel builders
at at least the major distros and kernel.org, and get them to tell me...

but that is a pretty far cry from my even *suggesting* that the XFS devs do
so, much less -- as it feels like Stan believes I already have -- saying that
I *expect* they should do so.

To any event that I "expect" that -- I expect it as a professional system
administrator with 30 years experience and lots of practice dealing with
systems at both the micro and macro level.  

Not as any kind of "customer".

*I* *have* read my Raymond and Moen, for all the good it's doing me. :-}

But I still do have those professional SA reflexes, and they still inform
the way that I make strategic decisions and choices about distros and 
their various components.  And not all of those decisions are strictly
technological.

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra@baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA               #natog                      +1 727 647 1274

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-07-28  2:21 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 [this message]
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
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=31450470.2412.1374978094689.JavaMail.root@benjamin.baylink.com \
    --to=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