[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: 7.3 installer with XFS



On Tue, 21 May 2002, Raju Mathur wrote:

> >>>>> "Florin" == Florin Andrei <florin sgi com> writes:
> 
>     Florin> Guys, I might start to modify the 7.3 installer to make it
>     Florin> use XFS out of the box. Michael Best did some research on
>     Florin> it, and below are his thoughts.  Do you think his plan is
>     Florin> ok? What are the obvious things missing?  I'm planning to
>     Florin> use the 2.4.18 XFS-enabled kernel from oss.sgi.com, and
>     Florin> also start with Michael's work here:
> 
>     Florin> http://www.pendragon.org/projects/valhalla-xfs/index_html
> 
>     Florin> -----Forwarded Message-----
> 
>     Florin> From: Michael Best <mbest emergence com>
>     Florin> To: linux-xfs oss sgi com
>     Florin> Cc: Christophe Zwecker <doc zwecker de>
>     Florin> Subject: Re: Status on RH7.3 installer ?
>     Florin> Date: 14 May 2002 16:10:07 -0600
> 
>     Florin> Perhaps someone knows how to do the step that I stopped
>     Florin> on, which was to generate a disk/disc image for booting
>     Florin> from the cdrom.  The default Redhat installer uses a 2.8M
>     Florin> installer image in the dosutils/autoboot directory of the
>     Florin> cd:
> 
>     Florin>   2.8M cdboot.img
>     Florin>   1.9M initrd.img
> 
>     Florin> Which appears to be a 2.8M boot image which contains:
> 
>     Florin>   784k of vmlinuz (kernel) and
>     Florin>   1.9M of initrd.img plus
>     Florin>   various bootup files.
> 
>     Florin> I need to make one of these and then I can probably make a
>     Florin> cd that boots with a different kernel.  By simply using
>     Florin> mkinitrd it makes a minimalist initrd image.
> 
> [Warning -- RH 7.2 experience]
> 
> The initrd can't be made using standard mkinitrd as far as I know.  I
> contains a non-standard init which calls /sbin/loader.  /sbin/loader
> itself is a sort of swiss knife of lots of apps rolled into one:
> language selection, modprobe, hardware probes, etc.  In the end,
> loader runs anaconda from the stage2.img.
> 
> The easiest way I found of making a custom initrd is to gunzip the
> original one, mount -oloop it, make whatever changes are required and
> then umount and gzip it again.  Maybe there're some tools available in
> anaconda-source or anaconda-runtime-source, but was too lazy to check
> :-)

I'd be too lazy to do that manually :) The 'buildinstall' script in 
anaconda-runtime package rebuilds the whole installer(images) from 
scratch, you just need to point the script to your RH install-tree.

	- Panu -





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]