On Wed, 20 Feb 2008 09:44:52 -0500 Jeremy Katz <katzj@xxxxxxxxxx> wrote: > On Wed, 2008-02-20 at 09:33 +0100, Joel Andres Granados wrote: > > isys.c and the likes go into the stage2.img (squashfs) To get a new > > isys.c into the installation you would have to rebuild anaconda, put > > isys.so into new stage2.img, put stage2.img image in tree, install. > > FYI, updates.img is for .py file, you can also put stuff there that > > you want to have at install time (a text file or whatever). > > This is partially true. You can also build isys.c into the _isys.so > shared module that's used by python and also stick it into an > updates.img. PYTHONPATH impacts loading of "native" modules as well as > byte-compiled ones. > > Other things that you can stick into updates.img are updated shared > libraries as we set LD_LIBRARY_PATH appropriately also. And rhpl updates, pykickstart...and tools that we might want for debugging. You might find this page useful: http://fedoraproject.org/wiki/Anaconda/Stage2DevelopmentGuide -- David Cantrell <dcantrell@xxxxxxxxxx> Red Hat / Honolulu, HI
Attachment:
pgp3qQKujPx2w.pgp
Description: PGP signature
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
