diff options
Diffstat (limited to 'docs/README')
| -rw-r--r-- | docs/README | 277 |
1 files changed, 171 insertions, 106 deletions
diff --git a/docs/README b/docs/README index d3432e34c..02bc5d351 100644 --- a/docs/README +++ b/docs/README @@ -1,143 +1,208 @@ -Well here is a little description of what panoramix needs to work in comparison -to the standard newt install. +Well here is a little description of what DrakX needs to work ******************************************************************************** -* CVS ************************************************************************** +* VCS ************************************************************************** ******************************************************************************** -Like all good free software, panoramix is in CVS :) +Like all good free software, DrakX is in SVN :) -You can access it using: -% export CVSROOT=:pserver:anoncvs@linux-mandrake.com:/home/cvs/cooker -% cvs login -% Passwd: cvs -% cvs checkout gi +You can access it at http://svnweb.mageia.org/soft/drakx/trunk/ -This is only read-only access. If you want more, tell me (pixel@mandrakesoft.com) +or via -Alas, all is not in CVS as a lot of things are binary files. -For the other things, take cooker-contrib others/src/gi.tar.bz2 +svn co svn+ssh://svn.mageia.org/svn/soft/drakx/trunk -Please note that redoing *all* the stuff is not for the faint of heart. I myself -sometimes wonder what the whole make does :-% -Instead, changing some .pm files is quite easy (nice interpreted language) + +This is only read-only access. If you want more, tell me (pixel) ******************************************************************************** -* FILES ************************************************************************ +* Making your custom install *************************************************** ******************************************************************************** -First he are the different things needed : - -Mandrake/base/hdlist - table of rpm's headers. - ! Need to be remade when Mandrake/RPMS changes ! - -Mandrake/base/depslist - for each packages, tell which package it depends on. Also contains the - size for some (obscure) bloody reasons. - ! Need to be remade when Mandrake/RPMS changes ! - -Mandrake/base/compss - obsoletes comps. It store packages in different categories, a bit like - the %{GROUP} field +If you have your own rpms you want to add, or make your own updated cdrom, you +just have to issue: -Mandrake/base/compssList - for each packages, it gives the appreciation for each type of user. - used to preselect packages - used to decide to show or hide packages. +% gendistrib --noclean --distrib <DIR> -Mandrake/mdkinst - live system used on certain installs. See ``Ramdisk or not'' below for - more. +Where <DIR> is the root of all the distribution. -Mandrake/base/mdkinst_stage2.gz - for the ramdisk. - live sytem in ext2 filesystem gzipped. See ``Ramdisk or not'' below for - more. +``gendistrib'' will scan the file media/media_info/media.cfg to search for all +media used. Typically you use media/main for RPM packages repository. -images/gi_*.img - boot images to use with panoramix. Use: - - gi_hd for hard-disk install - - gi_cdrom for cdrom install - - gi_network for ftp/nfs install - - gi_pcmcia for pcmcia install (see ``PCMCIA install'' below for more) +Optionnally, you can modify ``media/media_info/rpmsrate''; this file manages +the relative importance of the files, and thus their installation or not. - -Some optional files : - -Mandrake/base/depslist.html - html formatted depslist +To modify the code of stage2, use "misc/mdkinst_stage2_tool --uncompress +install/stage2" to generate "install/stage2/live". When you are done, use +"misc/mdkinst_stage2_tool --clean --compress install/stage2". +See below for information about these files. ******************************************************************************** -* po translation files ********************************************************* +* FILES ************************************************************************ ******************************************************************************** -Panoramix uses .po files for its translation. A script takes the different -strings out of the .pm files. It generates the panoramix.pot file which contains -all the english strings to translate. -To add a new language, you just have to add it to lang.pm (if it's not there -already) and put the .po in the perl-install/po directory (see ``Ramdisk or -not'' to know if you have to regenerate the mdkinst_stage2.gz) +First here are the different things needed : + +media/media_info/media.cfg + description of the available install media. + cf MDV::Distribconf(3) + +media/media_info/hdlist*.cz + table of rpm's headers, referred by ``media.cfg'' + their contents can be listed using ``packdrake -l <hdlist_file>'' or + or ``parsehdlist <hdlist_file>''. + ! Need to be remade when media/main changes (with ``gendistrib'') ! + +media/media_info/compssUsers.pl + +media/media_info/rpmsrate + ranks and classify packages, so that the installer will know which + ones to install. format is : + <intern_group> + <level> <packages> + where <intern_group> is a symbolic name used in media/media_info/compssUsers* files, + and <level> defines importance level as described below : + 5 mandatory + 4 important + 3 interesting + 2 nice + 1 maybe + installer selects packages for level 4 (important) and 5 (mandatory). + packages in other level (3, 2, 1) can only be selected using + individual package selection. + +install/stage2/mdkinst.sqfs + for the compressed loopback of install. + generated from install/stage2/live tree using misc/mdkinst_stage2_tool + +install/stage2/rescue.sqfs + rescue ramdisk. create_compressed_fs iso file + this is the ramdisk loaded when typing rescue on boot prompt. + +install/images/all.img + fat16 image to dd on a partition (hint: sda1) + +install/images/boot.iso + iso image to burn enabling any install (cdrom/hd/nfs/ftp) + + To boot from cdrom, use boot.iso + To boot from network, use isolinux/alt0/all.rdz + vmlinuz via pxe + To boot from hd (esp. usb key), use all.img. + + NB for usb boot: + - it seems some bioses don't use the code on MBR (sda), + or at least skip it when it's blanked + (eg: "dd if=/dev/zero of=/dev/sda bs=1 count=446") + - some bioses need it. I had some luck using + dd if=/usr/lib/extipl/aldebaran.bin of=/dev/sda + (install package extipl first) ******************************************************************************** -* PCMCIA install *************************************************************** +* logs ************************************************************************* ******************************************************************************** -If the media you use to install is a pcmcia device, you have two choices: -- use the gi_pcmcia boot disk -- use another boot disk and it will ask you a supplementary disk. Give it the -gi_pcmcia disk. - +During install, a lot of interesting stuff can be found in different places: +in consoles and in files. To switch to console 2 for example, do Ctrl-Alt-F2 +from the X install. +- alt-F1: the stdout of the install. Not very interesting stuff +- alt-F2: simple shell. Quite a lot of commands are available but as they are +written in perl (for space), they do not handle the very same options as normal. +After install, you can do ``chroot /mnt'' to see your system just like after +rebooting. ``rpm -qa'' works for example. +- alt-F3: a lot of interesting things. Be carefull, some ``ERROR'' messages are +not interesting. +- alt-F4: kernel's place. aka the output of dmesg. +- alt-F7: the graphical install lives there + +- command "bug" puts on floppy/usb-key lots of interesting stuff. +- /tmp/stage1.log: same as alt-F3 part when stage1 run (e.g. actions + before graphical install really begins) +- /tmp/ddebug.log: (nearly the) same as latter alt-F3 part +- /tmp/syslog: same as alt-F4 +- /mnt/root/drakx/ddebug.log: at the end of each step, DrakX tries to backup + /tmp/ddebug.log to /mnt/root/drakx. Available only after mounting of /. +- /mnt/root/drakx/install.log: the log of the installation (or upgrade) of the rpms +(just like rpm's /mnt/tmp/(install|upgrade).log) +- /mnt/root/drakx/auto_inst.cfg.pl: a kickstart file generated at the end of each +step. Can be used in 2 ways: kickstart install or ``defcfg'' install. Hopefully +you know about kickstart. ``defcfg'' is a way to customize the default values in +install. For example, French can be the default language with a qwerty keyboard, +the auto-partitionning partitions can be changed, the default user class can be +set to developer (!)... ******************************************************************************** -* Ramdisk or not *************************************************************** +* modules ********************************************************************** ******************************************************************************** -The panoramix install is much bigger than the newt one. So the ramdisk which was -used is getting big, and costs a lot in memory -(eg: the mdkinst_stage2 is 14MB - 23/09/99) - -| | newt | panoramix -|-------+---------+---------------------------------------------------------- -| nfs | live | live -| ftp | ramdisk | ramdisk -| http | ramdisk | not yet :( -| hd | ramdisk | live if Mandrake/mdkinst/usr/bin/runinstall2 is a link, -| | | ramdisk otherwise -| cdrom | ramdisk | live if memory < 40MB, ramdisk otherwise - -When i say live, it means that the install1 stage will *mount* the -Mandrake/mdkinst and use it that way. +To manually install a module during install, switch to console #2 +and type "modprobe <modulename>". The modprobe program is a perl +wrapper around /usr/bin/insmod. -The ramdisk is used in place of the live in some cases. This ramdisk is filled -with mdkinst_stage2.gz - -For cdrom install, the ramdisk is used to speed up things (access time is quite -high on cdrom drives) +******************************************************************************** +* Making screenshots *********************************************************** +******************************************************************************** +1. easy solution: press "F2"! -For pcmcia, it depends on the type of install. +2. On a test machine, make a network install, switch to console (ctrl-alt-F2), enter: +% xhost+ +then, on another computer: +% DISPLAY=test_machine:0 xwd -root | convert - screenshot.png +******************************************************************************** +* Auto install ***************************************************************** +******************************************************************************** +A powerful auto-install system is available. It allows performing +an install without any human interaction. + +To feed automatic parameters to the stage1 part (the textmode +part - might not be necessary for you if you plan to do +cdrom-based auto-installs, but mostly highly needed when doing +network installs), please refer to ../mdk-stage1/doc/TECH-INFOS. + +About the stage2 part (the actual installer, at the time you're +(usually) running in graphical mode), please refer to the nice +documentation written by David Eastcott. Either install the +package "drakx-autoinstall-doc" from contrib, or browse: + +http://members.shaw.ca/Mandrake2/drakx/9.2/AutoInstall-9.2.2.html + +The previous document will explain you how to setup the contents +of the auto_inst.cfg file. Note that you have 3 alternatives for +providing this file: +- from a floppy disk; use "kickstart=floppy" as kernel parameter, + as explained in the document +- from the installation volume itself; put the file in the + "install" directory of the installation volume; use + "kickstart" only, or "kickstart=filename" to specify another + filename than auto_inst.cfg +- specified by the network; setup your DHCP server to provide the + "bootfile" parameter, this file will be used as the + "auto_inst.cfg" file; in this case you also need to provide the + "netauto" boot parameter + +In any case, if the specified file ends with -IP or -IP.pl, IP +will be substituted by the IP address of the machine, when doing +a network install. Might be useful so that you can control all +your auto installs from your server. ******************************************************************************** -* modules ********************************************************************** +* Miscellaneous **************************************************************** ******************************************************************************** -Modules can be found in at least 3 places: -- in /modules/modules.cgz -- in /lib/modules/ -- in /lib/modules/modules.cpio.bz2 +> o Media access methods: nfs, ftp, http, hd, cdrom +> o Stages: init, stage1, stage2 +> - What exactly each stage does -/modules/modules.cgz is used in stage1. It contains only modules interesting for -one kind of install. For example in an gi_hd install, it contains scsi modules. -For an gi_network install, it contains network card modules. +init loads stage1 +stage1 loads stage2, from various medium type -/lib/modules/ contains modules that should be in /lib/modules/modules.cpio.bz2 -but are not for speed up. The serial.o module is there to speed up mouseconfig. +> - How one stage terminates and another begins. i.e., How does +> stage1 find, mount, and launch stage2? -/lib/modules/modules.cpio.bz2 contains every module except those of -/lib/modules/ + /sbin/init just starts /sbin/stage1, and monitors its +execution; it's here to cleanly umount the partitions when stage1 +or stage2 dies/finished + /sbin/stage1 takes care of mounting stage2 (in ramdisk if +necessary) then it execs /usr/bin/runinstall2 (thus, stage2 +replaces stage1, and init then monitors stage2) -To install a module, use modprobe which is in /usr/bin. It's a perl wrapper -around /usr/bin/insmod. It uses the dependencies found in -/lib/modules/modules.dep (stage1). +> o Text and Graphic mode installers +> - Architectural overview of each -/usr/bin/insmod is a wrapper around /usr/bin/insmod_. It just extracts the -module out of /lib/modules/modules.cpio.bz2 in /tmp. Then it calls insmod_. +have a look at drakx/docs/object_class.fig -/usr/bin/insmod_ is the real prog (which you usually find in /sbin/). You need -to give it the complete path. |