From: Jay Ashworth <jra@baylink.com>
To: xfs@oss.sgi.com
Subject: Re: Purpose of the XFS list -- was: A short digression on FOSS (Re: understanding speculative preallocation)
Date: Sun, 28 Jul 2013 11:45:54 -0400 (EDT) [thread overview]
Message-ID: <22300590.2458.1375026354258.JavaMail.root@benjamin.baylink.com> (raw)
In-Reply-To: <51F4A77A.30502@hardwarefreak.com>
----- Original Message -----
> From: "Stan Hoeppner" <stan@hardwarefreak.com>
> CentOS is a direct clone of RHEL. It uses the RHEL kernel. Thus XFS in
> the CentOS kernel is not generally supported on this mailing list.
> CentOS (and RHEL) userland XFS tools yes, kernel no. If there were some
> other custom distro kernel out there that was non mainline, it wouldn't
> get support here either.
Like, um, SuSE. Which hasn't used "mainline kernels" in years, if ever.
What, exactly, Stan, *is* a mainline kernel? kernel.org kernels?
No distribution worth its oats is using those; it isn't just CentOS.
> The reason "we" (and I'm not a Red Hat employee, nor a RHEL user)
> suggest to CentOS users that they become paying RHEL customers is
> obvious: they already use the software and are familiar and presumably
> comfortable with it and prefer it. If they pay they get Red Hat support
> for XFS in the kernel, along with anything else kernel related. If they
> want to continue to use a "no cost" OS and get support on this mailing
> list, they must have a distro with a mainline kernel. So the other
> obvious option is move to a distro that uses a mainline kernel. They
> may also be able to install a mainline kernel on CentOS, as someone
> suggested previously.
Or, they could use any other distro that isn't RHEL.
Or, well, SuSE, if your assertion is actually accurate, which I think it's
not, clearly.
> Nobody here is aiming guns at CentOS users heads. They have plenty of
> support options. It just so happens that using the stock CentOS (RHEL)
> kernel isn't one of them.
Ok. Got it. Then, since CentOS is the only realistic non-$1200/server/yr
distro available, I won't be using XFS anymore.
Note that you are pretty wildly violating the spirit of FOSS here.
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-28 15:46 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 [this message]
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=22300590.2458.1375026354258.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 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.