User Tools
packages:anaconda
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
packages:anaconda [2007-12-18 21:43] patrys |
packages:anaconda [2008-08-29 14:40] patrys |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| <file># poldek -r /path/to/root -U anaconda | <file># poldek -r /path/to/root -U anaconda | ||
| </file> | </file> | ||
| - | Tou will need to load all the necessary file system modules, so put the following into ''/path/to/root/etc/modules'': | + | You will need to load all the necessary file system modules, so put the following into ''/path/to/root/etc/modules'': |
| - | <file>ext2 | + | <file>dm-mod |
| + | ext2 | ||
| ext3 | ext3 | ||
| jfs | jfs | ||
| Line 45: | Line 46: | ||
| createrepo -g comps.xml -c /tmp/cache1 -v PLD/RPMS/ | createrepo -g comps.xml -c /tmp/cache1 -v PLD/RPMS/ | ||
| </file> | </file> | ||
| - | NOTE: Currently PLD Linux AC and TH already have repodata on ftp. | + | th/ac ftp admin could generate repodata with: |
| + | |||
| + | <file>$ gen-indexes ready | ||
| + | </file> | ||
| + | the comps.xml that is used for generation is at: | ||
| + | |||
| + | <file>$ l ~/ftp/.stat/repodata/comps.xml | ||
| + | -rw-r--r-- 1 pldth pldth 114K 2008-01-06 19:09 /home/pld/admins/th/ftp/.stat/repodata/comps.xml | ||
| + | </file> | ||
| + | and in CVS: [[http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/pld-ftp-admin/repodata/|http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/pld-ftp-admin/repodata/]] | ||
| + | |||
| + | **NOTE** Currently PLD Linux AC and TH already have repodata on ftp. | ||
| Line 54: | Line 66: | ||
| - | <file># cat /root/anaconda-install | + | <file>anaconda -T -m ftp://ftp.pld-linux.org/dists/th/ |
| - | export LC_ALL=en_US.utf-8 | + | </file> |
| - | mirror=http://your-mirror/pld | + | This will anaconda install from the selected url. |
| - | arch=`arch` | + | |
| - | url=$mirror/dists/ac/PLD/$arch/ | + | |
| - | anaconda --method=$url | + | |
| + | ===== Testing changes ===== | ||
| + | In order to test your changes without building a whole new CD, you can test Anaconda on your local system. To do so, go to the folder where your local build is and type: | ||
| + | |||
| + | |||
| + | |||
| + | <file>sudo ./anaconda --test -T -m ftp://ftp.pld-linux.org/dists/th/ | ||
| + | </file> | ||
| + | You can also test the graphic mode using: | ||
| + | |||
| + | |||
| + | |||
| + | <file>sudo ./anaconda --test -G -m ftp://ftp.pld-linux.org/dists/th/ | ||
| + | </file> | ||
| + | |||
| + | |||
| + | ===== Installing a chroot ===== | ||
| + | To install into a chroot, pass the ''-r'' command line switch: | ||
| + | |||
| + | |||
| + | |||
| + | <file>anaconda -G -m ftp://ftp.pld-linux.org/dists/th/ -r /path/to/chroot | ||
| </file> | </file> | ||
| - | This will just autodetect your archidecture and invoke anaconda install from url. | + | This will skip the partitioning steps and proceed with software selection and package installation. |
packages/anaconda.txt · Last modified: 2016-01-16 09:34 by glen
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
