xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

New RPMs based on XFS CVS (Feb24) WORK! Anyone got 146MB free somewhere

from [Bryan J. Smith] [Permanent Link][Original]
To: linux-xfs@xxxxxxxxxxx
Subject: New RPMs based on XFS CVS (Feb24) WORK! Anyone got 146MB free somewhere on the 'Net?
From: "Bryan J. Smith" <b.j.smith@xxxxxxxx>
Date: Sun, 25 Feb 2001 19:56:54 -0500
Organization: SmithConcepts/Personal
Reply-to: b.j.smith@xxxxxxxx, thebs@xxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx 
New RPMs based on XFS CVS (Feb24) WORK!  Anyone got 146MB free
somewhere on the 'Net?

All --

My new RPMs based around XFS from CVS (late Feb 24) seem to work
great!
I just tried them out, and even made an initrd disk so I could make
a root (/) XFS partition.

The list of all files in the archive is below (146MB total).  I also
am attaching my HTML "HOWTO" (which needs some refinement -- please
review).

I was going to put them on my personal server, with a 256Kbps
connection (shared with other co-locaters), but I think that's not
going to cut it if more than 2 people download (plus I've got
bandwidth limitations).  Is there somewhere at SGI or SourceForge
where these could go?  I'd be interested in cutting them on a weekly
basis.

Thanx in advance ... (and I hope the HTML attachment doesn't screw
up the archives)

-- TheBS

[ kernel-2.4.2-xfscvs_feb24]$ tree
.
|-- RCS
|   `-- SCXFS-HOWTO.lyx,v
|-- SCXFS-HOWTO.html
|-- SCXFS-HOWTO.lyx
|-- SPECS
|   `-- kernel-2.4.spec
|-- SRPMS
|   |-- acl-1.0.1-0.src.rpm
|   |-- attr-1.0.1-0.src.rpm
|   |-- dmapi-0.1.1-0.src.rpm
|   |-- kernel-2.4.2-xfscvs_feb24.src.rpm
|   |-- mkinitrd-2.8-1XFS.src.rpm
|   |-- modutils-2.4.2-3.src.rpm
|   |-- nfs-utils-0.3.1-1.src.rpm
|   |-- xfsdump-1.0.2-0.src.rpm
|   `-- xfsprogs-1.1.2-0.src.rpm
|-- athlon
|   |-- kernel-2.4.2-xfscvs_feb24.athlon.rpm
|   `-- kernel-smp-2.4.2-xfscvs_feb24.athlon.rpm
|-- i386
|   |-- acl-1.0.1-0.i386.rpm
|   |-- acl-devel-1.0.1-0.i386.rpm
|   |-- attr-1.0.1-0.i386.rpm
|   |-- attr-devel-1.0.1-0.i386.rpm
|   |-- devfsd-2.4.2-xfscvs_feb24.i386.rpm
|   |-- dmapi-0.1.1-0.i386.rpm
|   |-- dmapi-devel-0.1.1-0.i386.rpm
|   |-- kernel-2.4.2-xfscvs_feb24.i386.rpm
|   |-- kernel-BOOT-2.4.2-xfscvs_feb24.i386.rpm
|   |-- kernel-doc-2.4.2-xfscvs_feb24.i386.rpm
|   |-- kernel-headers-2.4.2-xfscvs_feb24.i386.rpm
|   |-- kernel-pcmcia-cs-2.4.2-xfscvs_feb24.i386.rpm
|   |-- kernel-smp-2.4.2-xfscvs_feb24.i386.rpm
|   |-- kernel-source-2.4.2-xfscvs_feb24.i386.rpm
|   |-- mkinitrd-2.8-1XFS.i386.rpm
|   |-- modutils-2.4.2-3.i386.rpm
|   |-- nfs-utils-0.3.1-1.i386.rpm
|   |-- xfsdump-1.0.2-0.i386.rpm
|   |-- xfsprogs-1.1.2-0.i386.rpm
|   `-- xfsprogs-devel-1.1.2-0.i386.rpm
|-- i586
|   |-- kernel-2.4.2-xfscvs_feb24.i586.rpm
|   `-- kernel-smp-2.4.2-xfscvs_feb24.i586.rpm
`-- i686
    |-- kernel-2.4.2-xfscvs_feb24.i686.rpm
    |-- kernel-enterprise-2.4.2-xfscvs_feb24.i686.rpm
    `-- kernel-smp-2.4.2-xfscvs_feb24.i686.rpm


-- 
Bryan "TheBS" Smith, Engineer                  CONTACT INFO
***********************************************************
 Chat: thebs413 @ AOL/MSN/Yahoo (see http://Everybuddy.com)
Email: mailto:thebs@xxxxxxxxxxxxxxxxx,thebs@xxxxxxxxxxx
0pt \textit{SmithConcepts}{\small \( ^{TM} \)} XFS Release\\ for RedHat Linux 7.0\\ HOWTO

SmithConcepts TM XFS Release
for RedHat Linux 7.0
HOWTO

Bryan J. Smith
(mailto:b.j.smith@xxxxxxxx)

$Id: SCXFS-HOWTO.lyx,v 1.2 2001/02/25 22:59:29 bjsmith Exp $

Contents

1  General XFS Information
2  SGI XFS for Linux Release(s)
    2.1  Beta releases
    2.2  Pre-Release version 0.9
    2.3  SGI CVS repository
3  SmithConcepts XFS Release(s)
    3.1  Before you being
    3.2  Release 2.4.2-xfscvs_feb24
    3.3  RPM List
        3.3.1  Binary Kernels Packages
        3.3.2  Kernel Source and Utilities Packages
        3.3.3  XFS Commands and Utilities
        3.3.4  Kernel Support Packages
        3.3.5  Other RPMs
        3.3.6  Source RPMs (SRPMs)
    3.4  Differences from Pre-Release 0.9
4  Installation / Maintenance Issues
    4.1  Installing more than one kernel RPM
        4.1.1  Multiple binaries
        4.1.2  Single source / utilities
        4.1.3  Installing older kernels
    4.2  XFS / (root) Partitions
    4.3  Building your own RPMs
5  Future Roadmap
    5.1  RedHat Linux 7.1
    5.2  Donations
6  Legal
    6.1  SmithConcepts
    6.2  Trademark
    6.3  Copyright and License
    6.4  Warranty
7  Log

1  General XFS Information

XFS is an advanced, enterprise-tested, journaling filesystem (JFS) for Irix and, most recently, Linux. The best source of information on XFS for Linux is SGI's official Open Source Software (OSS) XFS site.

With that said, here are some quick URLs for the XFS ``unfamiliar'':

2  SGI XFS for Linux Release(s)

At this time ($Date: 2001/02/25 22:59:29 $), there has been no ``official, feature complete'' XFS release for Linux. There has been, however, several ``Beta'' releases, one ``Pre-Release'' as well as continued, open, read-only access to the developer CVS (Concurrent Versions System) server where XFS is under constant development.

2.1  Beta releases

SGI has released several Beta XFS releases. At this time ($Date: 2001/02/25 22:59:29 $), all Beta releases have been against either 2.4.0-test or the completed 2.4.0 kernel (which is quite dated in Linux kernel time ;-). Beta XFS releases are available in SGI's ``ProPack'' format, RPMs for RedHat and in source form.

For more information on Beta XFS releases, see:

2.2  Pre-Release version 0.9

In mid-January 2001, SGI released its first XFS for Linux Pre-Release. This Pre-Release version 0.9 targetted the RedHat 7.0 release and an XFS kernel build against the recently completed Linux 2.4.0 kernel release. It included RPMs, Source RPMs (SRPMs) as well as a modified, replacement Anaconda installer with full XFS awareness for CD/Network installs. Unfortunately, like the Beta, releases, several revisions of the 2.4 kernel have followed without an update to Pre-Release version 0.9 (as of $Date: $), and many users have discovered issues with the 2.4.0 release (like IDE and software RAID - attributed to the stock 2.4.0 Linux kernel release itself).

For more information on the Beta XFS release, see:

2.3  SGI CVS repository

So, currently ($Date: 2001/02/25 22:59:29 $), the only means of getting an ``up-to-date'', ``XFS patched'' (among other patches) 2.4 kernel release is via CVS access to SGI's OSS server. SGI has kept its CVS tree very in-sync with offical Linux 2.4 kernel releases as they occur. Using CVS, you can retrieve the entire, patched Linux kernel tree (currently 2.4.2) and XFS command utilities from SGI's OSS server. Unfortunately this requires you to configure, build and install your own kernel (as well as the XFS utilities), which can be daunting for newer administrators.

For more information on SGI CVS Repository access, see:

3  SmithConcepts XFS Release(s)

The purpose of the SmithConcepts XFS Release is to bridge the gap between the dated Pre-Release (currently 0.9, based on Linux kernel 2.4.0 as of $Date: $) and the ``up-to-date'' CVS kernel/utilities (currently based on the lastest Linux kernel 2.4.2 release).

3.1  Before you being

I HIGHLY RECOMMEND that you consider yourself to be an EXPERIENCED KERNEL/LILO SYSADMIN before evem attempting to upgrade your system's kernel to this this EXPERIMENTAL XFS RELEASE. If this is your first time using the XFS kernel, you should only commit TEST SYSTEMS to the trial of this release.

3.2  Release 2.4.2-xfscvs_feb24

The current ($Date: 2001/02/25 22:59:29 $) SmithConcepts XFS release is 2.4.2-xfscvs_feb24. It is based on the XFS patched kernel and command code as of 2001 Feb 24. It builds, it installs, but it may not work for you on your system. I do not even pretend to understand how all the new components and capabilities of kernel 2.4 (let alone XFS) work. Use and install at your discretion.

3.3  RPM List

Below is a list of RPMs (by downloadable URL) and their descriptions for this release.

3.3.1  Binary Kernels Packages

It should be noted that, just like the SGI XFS Pre-Release, XFS itself is configured as a loadable module (and NOT compiled in) in all pre-configured binary kernels. See the following additional sections for more details and issues.

3.3.2  Kernel Source and Utilities Packages

The following RPMs should be upgraded when any of the above binary kernels are installed:

3.3.3  XFS Commands and Utilities

These RPMs are support commands for XFS filesytems. In the Pre-Release, they were a single RPM (xfs-cmds-1.0.5-1.i386.rpm). For now, the CVS tree builds them individually (there will be a single, unified SPEC file in the future):

3.3.4  Kernel Support Packages

The following RPMs are *KEY* in getting the XFS kernel booting in many configurations:

  • ./i386/devfsd-2.4.2-xfscvs_feb24.i386.rpm
    devfs daemon for systems that use the new /dev filesystem (devfs) interface
  • ./i386/mkinitrd-2.8-1XFS.i386.rpm
    A patched mkinitrd package that allows for the creation of root disks with the XFS loadable module (for systems that have a XFS formatted root filesystem)
    [ NOTE: While this mkinitrd is a perfect upgrade for RedHat 7.0 (which has an older version), *IF* you upgrade to newer RedHat betas/releases with mkinitrd-3.0.x, you will *NEED* to patch and rebuild their mkinitrd package to work with XFS! ]
  • ./i386/modutils-2.4.2-3.i386.rpm
    Kernel 2.4-compatible loadable kernel module utility suite (ripped from the RedHat 7.0.91/wolverine beta)

3.3.5  Other RPMs

3.3.6  Source RPMs (SRPMs)

As above for the binary of the same name:

3.4  Differences from Pre-Release 0.9

The pre-built binary kernels are closely based on the existing .config files from the SGI XFS Pre-Release. As such, they're configuration and contents are similiar with the following key differences:

  • The obvious: SmithConcepts releases are based on the Linux 2.4.2 kernel release
  • ATA/IDE is now compiled-in by default. Early stock 2.4.0/2.4.1 kernel releases had issues with these devices (which affected XFS) and the SGI Beta/Pre-Release compiled ATA/IDE only as a loadable module.
  • The ``ksymoops'' package is not included in the current release (2.4.2-xfscvs_feb24). As such, the ``SysReq'' configuration option does not work and there is no ``kernel-utils'' RPM for the current release.
    (NOTE: Please no comments on this. I ran into an issue in the builds which I did not want to address. I will, in all likelihood, put ksymoops/SysReq/kernel-utils back in as standard in a future release. If you don't know what I am talking about then don't worry about it as many RPM kernel binaries have it disabled by default anyway ;-)
  • The kernel tree is a heavily patched/modified kernel tree from SGI's XFS CVS repository
    (NOTE: Do *NOT* assume from the short SRPM file listing that the SmithConcepts/SGI CVS XFS kernel is lacking all the patches of the SGI Pre-Release or RedHat RPM kernels. Instead of using the stock ``linux-2.4.x.tar.bz2'' kernel as a ``base'', the completely modified ``linux-2.4.x-xfscvs_date.tar.bz2'' is used as a base and already has many of these patches integrated)
  • The Athlon processor has its own, specific kernel target RPM
    (Newer RedHat betas now includes the Athlon as a standard kernel target RPM, so it is only natural. Plus, being an engineer, I have several Athlons due to their superior 64-bit/double-precision performance)
  • The IA-64 processor target RPM has been dropped
    (NOTE: I do not have an Itanium to use, nor do I wish to bother with the simulator on x86 given my personal time constraints. Thus, I have also removed the IA-64 target, among all other non-x86 targets, from the SPEC file below (which means the SPEC file is x86-only). This is the same SPEC file in the SRPM as well)

4  Installation / Maintenance Issues

There are several details to installing and maintaining the SmithConcepts XFS Release(s). Please familiarize yourself with them below before installing. E.g., a good time to do this would be while you are downloading the RPM(s). ;->

4.1  Installing more than one kernel RPM

Newer versions of RPM (3.0.4+?) allow more than one RPM to be installed. As such, it is fairly easy to install multiple kernels from RPM, and boot any one of them. Of course, there are limits to this configuration (e.g., only one kernel-source RPM can be installed). And RPM itself cannot address boot/LILO details (i.e., /boot/* and /etc/lilo.conf files).

You should consider keeping your existing 2.2 and/or 2.4 kernel RPM(s) installed when installing (not upgrading) to the SmithConcepts XFS releases. I summarize the details below (sysadmin-level knowledge of RPM highly recommended):

4.1.1  Multiple binaries

You can have multiple kernel binaries installed as their files will not conflict with each other. You should be able to install multiple versions of the following kernel binary RPMs (replace ``ver'' with the kernel version, e.g., 2.2.17.14, 2.4.2-1, and ``arch'' with the processor target, e.g., i686, athlon):

  • kernel-ver.arch.rpm
  • kernel-smp-ver.arch.rpm
  • kernel-enterprise-ver.i686.rpm
  • kernel-BOOT-ver.i386.rpm

In each case, you should install with the ``rpm -i'' command (and NOT ``rpm -U'' which will replace existing kernels). You may additionally need to use the ``-replacefiles'' option on some systems. It is recommended that you do not blindly use the ``-force'' option.

Of course you still need to modify the files in /boot and edit /etc/lilo.conf and install before attempting to reboot after a new kernel version installation.

4.1.2  Single source / utilities

As far as the source code and/or utilities (at least in regards to RedHat 7+ releases) are concerned, you should only have one RPM set. Install only one version of the following RPMs (again, replace "ver" with the kernel version, e.g., 2.2.17.14, 2.4.2-1, and "arch" with the processor target, although it will almost always be i386 RPM for x86 systems):

  • kernel-doc-ver.i386.rpm
  • kernel-headers-ver.i386.rpm
  • kernel-ibcs-ver.i386.rpm
  • kernel-pcmcia-ver.i386.rpm
  • kernel-source-ver.i386.rpm
  • kernel-utils-ver.i386.rpm

Normally, that set should be the latest for maximum compatibility with components (e.g., kernel-headers can affect other, non-kernel elements like GLibC on RedHat systems). So when ``upgrading'' (NOT installing) these components, use the ``rpm -U'' command (and NOT ``rpm -i'' which can lead to multiple copies and dependency frustrations).

4.1.3  Installing older kernels

Numerous issues can arise if you have a newer kernel and source/utility set installed, yet are re-installing or building a custom kernel of an older version. It may require numerous RPM uninstalls (``rpm -e'') and/or re-installs to accomplish. Note that RedHat 7 releases have other components that are based on the kernel-headers-2.4.*.i386.rpm releases and they should not be uninstalled or replaced (except with newer versions).

4.2  XFS / (root) Partitions

As previously mentioned, XFS is compiled as a module in all pre-configured binary kernel RPMs. This is due to sheer size issues with the XFS code. If you are going to make your root (/) filesystem XFS, you must due one of following. Either:

  1. Build and install a custom kernel from source with XFS compiled-in, OR
  2. Use the modified mkinitrd utility suite to make a XFS initial root disk, e.g.:

mkinitrd --with=xfs --with=xfs_support /boot/initrd-2.4.2-xfscvs_feb24.img 2.4.2-xfscvs_feb24

In the case of #2, do NOT forget to add the proper ``initrd'' option to your ``image'' section in /etc/lilo.conf.

[ FYI, the default ramdisk size in the pre-configured binary kernel RPMs is the standard 4096 ]

4.3  Building your own RPMs

If you are maintaining your own working CVS directory of the XFS kernel, doing your own updates, etc..., you can find my reference (i.e. you'll need to modify for yourself) RPM SPEC file below for creating your own RPMs/SRPMs (so you don't have to download my 20GB+ SRPMS just to get that one file ;-). If you don't know what a RPM ``SPEC'' file is, or you don't understand how to use it, then you probably should NOT be building your own RPMs.

RPM SPEC file:

[ NOTE: For reasons of maintaining sanity, I will *NOT* answer questions on how to use SPEC files (unless you are making a suggestion regarding or commenting on a bug in the file itself). Asking my questions directly will put you on my very personal /dev/null E-mail filter. ;-). ]

5  Future Roadmap

I cannot tell or predict the future. I definately cannot tell what direction SGI will take with future RedHat and/or Linux kernel releases.

5.1  RedHat Linux 7.1

If the SGI Pre-Release version 0.9 is any indicator, I expect SGI to release a new Pre-Release (possibly Release version 1?) shortly after (i.e. withing a week or two) the official release of RedHat Linux 7.1. It will most likely be based on the latest stock Linux kernel release (be it the current 2.4.2 release, or future 2.4.3+ releases) with various patches and a modified Anaconda installer in-line with the stock RedHat 7.1 release.

5.2  Donations

It currently takes in excess of 10 hours to build binary kernel RPMs from the RPM .spec file and additional time to reorganize, build and upload the releases themselves (to my sub-standard server and connection). Please be patient with me on updates and fixes. Heck, if my boss (of my normal 60-er, 40 hour/week job) knew I was donating my personal time to something like this, he'd probably find work-related stuff for me to do at home instead. ;-PPP

So, for the impatient ;->, if you would be interested in donating any hardware or capabilities (such as server space on a fast connection) to ``expidite'' the release process, please contact me directly (I've had my eye on an approximately $1K total ServerWorks chipset-based mainboard + 2xCPU and 1GB memory upgrade ;-). Note, at this time ($Date: 2001/02/25 22:59:29 $), I canNOT offer any tax deductions or avenue of legal gift expenditure incentives in any donation.

6  Legal

I am not a lawyer and do not pretend to offer legally accurate statements, although I offer them in the ``goodwill'' of protecting myself and the intellectual property of myself and others. Please do not abuse this ``goodwill.''

6.1  SmithConcepts

SmithConcepts is currently not an incorporate or registered fictious entity (as of $Date: 2001/02/25 22:59:29 $).

6.2  Trademark

SmithConcepts(TM), SmithConcepts.COM and the SmithConcepts(TM) logo are trademarks of Bryan J. Smith. (C) 1992-1995, 1998-2001, all rights reserved.

6.3  Copyright and License

All orginal content contained within this document and directory heirarchy (./kernel-2.4*) is property of Bryan J. Smith, (C) 2001. All rights reserved to the Free Software Foundation (FSF) unless otherwise noted.

Content and other intellectual property of other entities and persons are recognized as property of their respective entities and persons, all rights reserved unless otherwise noted.

This document is licensed under the GNU Free Documentation License, version 1.1 (http://www.gnu.org/copyleft/fdl.html), (C) 2001.

All content and/or code at this directory heirachy (./kernel-2.4*) and below is licensed under the GNU Public License, version 2 (http://www.gnu.org/copyleft/gpl.html), (as of $Date: 2001/02/25 22:59:29 $), or other FSF recognized and applicable GNU license(s) unless otherwise noted and/or reserved by copyright.All rights served to the FSF unless otherwise noted and/or reserved by copyright.

6.4  Warranty

[ Re: Terms and Conditions 11 and 12 from the GPL ]

BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7  Log

$Log: SCXFS-HOWTO.lyx,v $Revision 1.2  2001/02/25 22:59:29  bjsmithIncorrect mkinitrd syntax in section 4.2 (fixed)Revision 1.1  2001/02/25 22:36:00  bjsmithInitial revision

File translated from TEX by TTH, version 2.51.
On 25 Feb 2001, 17:59.
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: building 2.4.2 (with XFS) fails, Keith Owens
Next by Date:  Re: New RPMs based on XFS CVS (Feb24) WORK! <- Hmmm, whole else besides SourceForge.NET?, Bryan J. Smith
Previous by Thread:  NFS 0 sizes bug, high nfsd load, Robin Humble
Next by Thread:  Re: New RPMs based on XFS CVS (Feb24) WORK! <- Hmmm, whole else besides SourceForge.NET?, Bryan J. Smith
Indexes:  [Date] [Thread] [Top] [All Lists]