I've tried the following:
Upgrade 7.3/xfs 1.1 to 8.0/xfs 1.2 with the v.2 ISO image. Except for the
question of whether I was building a new system or upgraded I chose all the
default settings. This scenario worked just fine with only one exception -
lilo did not run as part of the installation so the machine rebooted
however it was using the prior 7.3/xfs 1.1 kernel and none of the modules
loaded. Easy enough to fix, however something that might be frustrating.
I have one cosmetic note - the installer I know on the v.1 disk, not sure
about the v.2 disk - prompts for Disk 6 - I was tired and grumpy by this
point so it took some time for it to sink in that this means the SGI XFS
1.2 for RH disk.
Thanks so much for putting the effort into this. LOVE xfs.
--On Wednesday, February 19, 2003 2:37 PM -0600 Russell Cattelan
Ok the installer iso has been respun the iso the athlon kernels.
The acl-devel and attr-devel packages have also been updated
to libacl-devel and libattr-devel.
I have not tested this iso but hopefully nothing in the
build process has gone a muck so it should work no worse than
the old one.
The Makefile that I use to do all the setup and building of the various
pieces has been included on the iso.
No howto at this time but is anybody is feeling really brave they
can give play with it.
On Tue, 2003-02-18 at 19:27, Eric Sandeen wrote:
On Tue, 18 Feb 2003, Bernhard Erdmann wrote:
> Is it that complicated? Do you have a Howto or a script how to "roll
> your own installer"?
It's not that hard, once you've taken the time to figure things out.
There were two bits of it, Anaconda modifications to support xfs,
and creating the right build environment for the installer. You can look
at the patch in the Anaconda SRPM to see what we did to the installer
itself (actually lots of xfs support is there already from Red Hat,
thanks to Martin!). To see how we set up the build environment, it would
probably be best to post a Makefile that Russell wrote to do most of the
We essentially have every RPM from 8.0 + our RPMs in a tree, and symlink
them around. One set of symlinks is for all the RPMs needed to build
the anaconda environment, the other set of symlinks "teaches" the
installer which RPMs are on which CD. Scripts that come with Anaconda
do the rest (build the hdlist and build the installer).
I'll talk to Russell about publishing the Makefile - I think we'd both
be ecstatic if someone else wanted to pick up this work. :)
Russell Cattelan <cattelan@xxxxxxxxxxx>