<div dir="ltr">Hi Stan,<div><br></div><div>Thanks for the info (most of it was, in fact, news to me). I'm an application developer trying to debug a disk space problem, that's all. So far, I've tracked it down to being an XFS issue.</div>
<div><br></div><div>So you are saying there's no public information that can correlate XFS versioning to CentOS (or RHEL) versioning?</div><div><br></div><div>Sad state of affairs.</div><div><br></div><div>If anyone can volunteer this info (if available to you) I'd be much appreciative.</div>
<div><br></div><div>Regardless, is there a version history for XFS vis-a-via mainline Linux?</div><div><br></div><div>Thanks,</div><div><br></div><div>Jason</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Jul 26, 2013 at 3:27 PM, Stan Hoeppner <span dir="ltr"><<a href="mailto:stan@hardwarefreak.com" target="_blank">stan@hardwarefreak.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 7/26/2013 12:40 PM, Jason Rosenberg wrote:<br>
<br>
</div><div class="im">> Anyway, I'm surprised that you don't have some list or other way to<br>
> correlate version history of XFS, with os release versions. I'm guessing<br>
> the version I have is not using the latest/greatest. We actually have<br>
> another system that uses an older version of the kernel (2.6.32-279), and<br>
<br>
</div>2.6.32-279 - this is not a mainline kernel version. This is a Red Hat<br>
specific string describing their internal kernel release. It has zero<br>
correlation to any version number of anything else in the world of<br>
mainline Linux.<br>
<div class="im"><br>
> If, say you tell me, the mainline xfs code has improved behavior, it would<br>
> be nice to have a way to know which version of CentOS might include that?<br>
<br>
</div>IMNSHO, CentOS is a free proprietary chrome plated dog turd. It's<br>
flashy on the outside and claims it's "ENTERPRISE", "just like RHEL!".<br>
Then you crack it open and find nothing but crap inside. So you take it<br>
back to the store that gave it away for free and the doors are barred,<br>
the place out of business. The chrome has peeled off and you're stuck<br>
with crap that difficult to use. Every time you touch it you get dirty<br>
in some fashion.<br>
<br>
RHEL is a proprietary solid chrome turd you pay for. You can't get to<br>
the inside, but if you find a scratch and 'return' it Red Hat will say<br>
"we can help you fix that".<br>
<br>
If you avoid the flashy turds altogether while still plunking down no<br>
cash, and use a distro based entirely on mainline Linux and GNU user<br>
space source, you can get help directly from the folks who wrote the<br>
code you're running because they know what is where. Whether it be<br>
Linux proper, the XFS subsystem, NFS, Samba, Postix, etc. Such<br>
distributions are too numerous to mention. None of them are chrome<br>
plated, none claim to be "just like ENTERPRISE distro X". I tell all<br>
users of RHEL knock offs every time I see a situation like this:<br>
<br>
Either pay for and receive the support that's required for the<br>
proprietary distribution you're running, or use a completely open source<br>
distro based on mainline kernel source and GNU user space. By using a<br>
RHEL knock off, you're simply locking yourself into an outdated<br>
proprietary code base for which there is no viable support option,<br>
because so few people in the community understand the packaging of the<br>
constituent parts of the RHEL kernels. This is entirely intentional on<br>
the part of Red Hat, specifically to make the life of CentOS users<br>
painful, and rightfully so.<br>
<br>
FYI, many of the folks on the XFS list are Red Hat employees, including<br>
Dave. They'll gladly assist RHEL customers here if needed. However, to<br>
support CentOS users, especially in your situation, they'd have to use<br>
Red Hat Inc resources to hunt down the information related to the CentOS<br>
kernel you have that correlates to the RHEL kernel it is copied from.<br>
So they've just consumed Red Hat Inc resources to directly assist a free<br>
competitor who copied their distro.<br>
<br>
Thus there's not much incentive to assist CentOS users as they'd in<br>
essence be taking money out of their employer's pocket. Taken to the<br>
extreme this results in pay cuts, possibly furloughs or pink slips, etc.<br>
<br>
Surely this can't be the first time you've run into a free community<br>
support issue with the CentOS kernel. Surely what I've written isn't<br>
news to you. Pay Red Hat for RHEL, or switch to Debian, Ubuntu, Open<br>
Suse, etc. Either way you'll be able to get much better support.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Stan<br>
<br>
</font></span></blockquote></div><br></div>