In all these responses, there has been no mention of the RHupdates folder - what I am trying to avoid is to modify the isos that are being mounted, I simply want to override them with my files, such that if I want to, I can just remove my files and things are back to normal. Is there a way to have this all work without having to create ext2 or other images? Nima On 13/10/06 11:14 AM, "David Cantrell" <dcantrell@xxxxxxxxxx> wrote: > John Summerfield wrote: >> David Cantrell wrote: >>> Daniel F de Araujo wrote: >>> >>>> >>>> Nima Talebi wrote: >>>> >>>>> Hi, >>>>> >>>>> Could someone please tell me what I am doing wrong that is resulting >>>>> in my >>>>> modified code not be seen/used in the Anaconda process. I can't find >>>>> a good >>>>> source for documentation so I am going by what I've picked up here and >>>>> there, so please correct me where you can. >>>>> >>>>> Once I figure this out, I will write a nice howto so the next person >>>>> settles >>>>> into the anaconda dev environment with less dust. >>>>> >>>>> Here are the details of my current setup: >>>>> >>>>> * Install method: HTTP >>>>> * Source tree root: /var/www/html/iso/RedHat/4.0/as/x86_64/. The >>>>> contents of >>>>> this directory are: >>>>> >>>>> drwxr-xr-x 6 root root 4096 Oct 12 13:06 disc1 >>>>> lrwxrwxrwx 1 root root 12 Mar 6 2006 disc2 -> mounts/disc2 >>>>> lrwxrwxrwx 1 root root 12 Mar 6 2006 disc3 -> mounts/disc3 >>>>> lrwxrwxrwx 1 root root 12 Mar 6 2006 disc4 -> mounts/disc4 >>>>> lrwxrwxrwx 1 root root 12 Mar 6 2006 disc5 -> mounts/disc5 >>>>> drwxr-xr-x 4 root root 4096 Oct 12 13:06 ISO >>>>> drwxr-xr-x 6 root root 0 Oct 12 14:03 mounts >>>>> drwxr-xr-x 2 root root 4096 Nov 3 2005 RPMS.det >>>>> drwxr-xr-x 2 root root 4096 Nov 3 2005 RPMS.os >>>>> drwxr-xr-x 2 root root 4096 Nov 3 2005 RPMS.updates >>>>> >>>>> ...as you can see the disc* are symbolic links. The reason is that >>>>> they are >>>>> forcing the mount/disc* directories to automount... This works fine, >>>>> however >>>>> for the sake of removing as many variables as possible, I've >>>>> replaced the >>>>> symbolic link for disc1 with the actual directory. >>>>> >>>>> * I have then created a directory called `Rhupdates' with my >>>>> replacement >>>>> python source inside it. I've placed this directory in.... >>>>> >>>>> /var/www/html/iso/RedHat/4.0/as/x86_64/ >>>>> /var/www/html/iso/RedHat/4.0/as/x86_64/disc1/ >>>>> /var/www/html/iso/RedHat/4.0/as/ISO/ >>>>> >>>>> ...I realise that this is silly, and I should only place it in the one >>>>> place, but given that all three make no difference, I can say with >>>>> confidence that I don't know what the correct place is. >>>>> >>>>> * My Rhupdates directory contains: >>>>> >>>>> -rw-r--r-- 1 root root 22854 Oct 12 11:56 installclass.py >>>>> -rw-r--r-- 1 root root 16715 Oct 12 11:42 network.py >>>>> >>>>> * If Rhupdates is to be `seen' by anaconda, I am expecting it to be >>>>> visible >>>>> under /mnt/source/Rhupdates one the machine being kickstarted, and >>>>> then have >>>>> sys.path.insert() this directory prior to anything else. >>>>> >>>>> >>>>> Could someone please tell me: >>>>> >>>>> If RTFM, where the FM is >>>>> Else, what I am doing wrong, and any misunderstandings I have based >>>>> on the >>>>> above. If additional information is required and I have carelessly >>>>> left it >>>>> out, please let me know and I will amend. >>>>> >>>>> Thankyou for your help, >>>>> >>>>> Nima >>>>> >>>>> FYI - Daniel <dan us ibm com> has already sent me his docs on how this >>>>> should be done... >>>>> >>>>> --snip-- >>>>> 1) NFS, FTP, HTTP: >>>>> Simply create a directory named "RHupdates" at the top level of the >>>>> source tree. Place your modified .py files in this folder and Anaconda >>>>> will use your changes during the next install. >>>>> --snip-- >>>> >>>> >>>> Actually, for FTP and HTTP, you can use the following options: >>>> - floppy. >>>> - 'updates.img' file in 'RedHat/base' directory. >>> >>> >>> And if you use updates.img, it needs to be and ext2 filesystem. >>> We might support iso9660, but I forget. ext2 works. >>> >>> Maybe we should also support vfat. Hrmm... >>> >> USb would be good (better than floppy for many), for production release >> and maybe for testing changes. > > USB jumpdrives are supported if you format it as ext2, no partition > table. Just format the raw device. ********************************************************************** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. **********************************************************************
