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 17:00:21 -0400 (EDT) [thread overview]
Message-ID: <6869770.2390.1374958821773.JavaMail.root@benjamin.baylink.com> (raw)
In-Reply-To: <51F343F5.5080709@hardwarefreak.com>
----- Original Message -----
> From: "Stan Hoeppner" <stan@hardwarefreak.com>
> On 7/26/2013 2:43 PM, Jay Ashworth wrote:
>
> > But to address your specific point, I don't believe that RH is going
> > to
> > base its opinion on what time its employees spend supporting the
> > remainder
> > of the FOSS ecosystem on whether the relevant distro was copied from
> > theirs,
> > or not -- and I will be disappointed, publicly, and vocally, if they
> > do.
>
> On 7/26/2013 8:26 PM, Dave Chinner wrote:
In a message which, for some reason, I do not see here in my list folder;
(it wasn't in my inbox either; this seems a running thing)
> > Disclaimer: I'm the primary RHEL XFS developer, employed by Red Hat.
> >
> > CentOS is a rebadged RHEL product that is released for free. If you
> > want bugs fixed in CentOS, then generally you are on your own. If
> > you want paid support where people will fix problems you have, you
> > need to pay for RHEL.
> >
> > You get what you pay for.
>
> Jay, I'm awaiting your public and vocal disappointment. BTW, Dave has
> stated this position regarding CentOS many times. I'm guessing you're
> new to the XFS list (July 13 maybe) or simply missed such prior posts
> if you've been lurking much longer.
I am new to the list, yes. But -- and I can only reply to what you
quoted here; apologies to DC if it's less than what he wrote -- I am
in fact disappointed: in Dave for the strawman reply. No one, that I
saw, *reported bugs or asked for support* with CentOS.
The question -- and it was coming from someone who sounded like
they had read their Raymond, Moen, and Tatham, was "how do I
determine *which version of the XFS drivers* is in the kernel
I'm running, so that I can helpfully report my problems to the list".
If Dave thinks *that* question is out of bounds, then when I do my
rotating reformat to recover from my recent power supply induced
crash, XFS will not be the file system I pick off the pulldown menu
to reformat with.
As I've just had to explain to the openSUSE release configuration
people over sysVinit and packaging, the policies of the developers
underneath the code are *much* more important to me than the code
is, or what the code does.
If the implication of Dave's comment above is that he's not interested
in bug reports from people who aren't paid customers of RH, I'm fine
with that as well; his call. Clearly, I won't be one of those,
either; my sister isn't interested in paying $1200/yr for the OS on
her DVR.
Perhaps I'm misinterpreting one of you.
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
next prev parent reply other threads:[~2013-07-27 21:00 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 [this message]
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
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=6869770.2390.1374958821773.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