[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Creating an ext 2 image update
- From: Arthur Rodrigo Sawazachi Valadares <arthursv linux vnet ibm com>
- To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list redhat com>
- Subject: Re: Creating an ext 2 image update
- Date: Thu, 07 Aug 2008 10:41:26 -0300
Hi Joel, I was doing something just like that. But this is what I'm
still getting, after using your method as well:
I created the image with $./mkimage /tmp yuminstall.py
and I copied the /tmp/ud.img to the http server.
Then I booted RHEL with updates=HTTPPATH/ud.img.
Got this after setting the NFS path on installer:
Traceback (most recent call last):
File "/usr/bin/anaconda", line 895, in ?
from yuminstall import YumBackend
File "/tmp/updates/yuminstall.py", line 21, in ?
from errors import *
On Thu, 2008-08-07 at 11:12 +0200, Joel Andres Granados wrote:
> The best way to test stuff with anaconda is to pass the updates image on the command line.
>
> 1. create an updates image. Go to (http://jgranado.fedorapeople.org/anaconda/scripts/createUpdates). There has been lots of scripts to do this but this is what I use.
> 2. Put the image on the network somewhere (http server)
> 3. start install and pass "updates=http://server/path/to/updates.img"
>
> this should work for all anaconda py files and should also work for the libraries that anaconda uses.
>
> Hope it helps.
>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]