Re: building 2.4.2 (with XFS) fails <- Is GLibC 2.2 required?
james rich wrote:
> I built a stock kernel 2.4.2 with no problems so the failure below is
> definately something related to the XFS patches. Unfortunately I don't
> know the cause of the build failure. Is everyone here building on RH7?
> I'm using Slackware 7.1. It seems that these patches would need to build
> on most distros before reaching release level. Let me know if I can do
> something (happy to test stuff).
<warning: newbie response, please _correct_ any false assumptions>
Totally coming at this from a different angle, I don't think its
going to be so much of a "distro" issue. I think it will be a GLibC
issue. Am I safe in assuming that XFS is not well supported (nor
will be well supported) on GLibC releases prior to 2.2? This is due
to GLibC 2.2 having a number of new capabilities like LFS (>2GB file
support on 32-bit architectures) in the VFS, among other details?
If so, then that doesn't make it a "RedHat 7.x"-only 'thang, it
makes it a GLibC 2.2 'thang. I've heard from many people (largely
because I am already running Ext3 on my kernel 2.2 systems and there
was a thread on this over on the SourceForge NFS list) that LFS is
not well supported (and utility support varies) unless binaries are
built against GLibC 2.2. So be it Slack, Mandrake or even RedHat
6.x users, if GLibC is the issue, your'all in the same boat.
Again, please correct me if I am wrong?
</warning>
DISCLAIMER: I just joined the XFS list about a week ago. I have
been running Ext3 for over 9 months (6 months in heavy production
use) and am admist integrating XFS into a test RedHat 7.0.90 (soon
to be 7.0.91) + kernel 2.4.2 installation. This move is largely due
to the fact that A) Ext3 is 2.2-only right now, B) ReiserFS has
kNFSd issues (let alone not quite as proven) C) XFS is one of the
most advanced JFS of the lot and D) the success rate seems to be
good with XFS (unless software RAID or IDE is used, although both
are due to the 2.4.x kernel itself).
-- TheBS
--
Bryan "TheBS" Smith chat:thebs413 @AOL/MSN/Yahoo
Engineer mailto:b.j.smith@xxxxxxxx,thebs@xxxxxxxxxxx
*********************************************************
"Never apply a Star Trek solution to a Babylon 5 problem"
-- Nicholas C. Weaver
|