diff options
Diffstat (limited to 'docs/README')
| -rw-r--r-- | docs/README | 154 |
1 files changed, 42 insertions, 112 deletions
diff --git a/docs/README b/docs/README index 6c8307707..02bc5d351 100644 --- a/docs/README +++ b/docs/README @@ -1,29 +1,18 @@ -Well here is a little description of what DrakX needs to work in comparison -to the RH newt install. +Well here is a little description of what DrakX needs to work ******************************************************************************** -* CVS ************************************************************************** +* VCS ************************************************************************** ******************************************************************************** -Like all good free software, DrakX is in CVS :) +Like all good free software, DrakX is in SVN :) -You can access it at http://www.mandrakelinux.com/cgi-bin/cvsweb.cgi/gi +You can access it at http://svnweb.mageia.org/soft/drakx/trunk/ or via -export CVS_RSH=ssh -export CVSROOT=:ext:anoncvs@cvs.mandrakesoft.com:/cooker -cvs checkout gi - (enter password 'cvs') +svn co svn+ssh://svn.mageia.org/svn/soft/drakx/trunk -This is only read-only access. If you want more, tell me (pixel@mandrakesoft.com) - -Alas, all is not in CVS, a lot of things come from rpm packages which you must -install. - -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) ******************************************************************************** * Making your custom install *************************************************** @@ -31,28 +20,19 @@ Instead, changing some .pm files is quite easy (nice interpreted language) If you have your own rpms you want to add, or make your own updated cdrom, you just have to issue: -% gendistrib --noclean --distrib <DIRS> - -Where <DIRS> is the root of all the media that the install will see, this first -one is the main one : +% gendistrib --noclean --distrib <DIR> -(1) network or 1-cdrom installs - DIRS == the root directory of the Distribution +Where <DIR> is the root of all the distribution. -(2) multi-cdrom install - DIRS == the root directories of all the media that the install will see - -``gendistrib'' will scan the file media/media_info/hdlists in the main root -directory (the first one in DIRS) to search for all media used. Typically you -use media/main for RPM packages repository. -For multi-cd, please use media/main or media/foo, etc. -For one CD or a network/hd volume, please use media/main. +``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. Optionnally, you can modify ``media/media_info/rpmsrate''; this file manages the relative importance of the files, and thus their installation or not. -To modify the code of stage2, use "misc/mdkinst_stage2_tool install/stage2" to generate "install/stage2/live". -When you are done use "misc/mdkinst_stage2_tool install/stage2" again, the "rm -rf install/stage/live". +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. ******************************************************************************** @@ -60,28 +40,17 @@ See below for information about these files. ******************************************************************************** First here are the different things needed : -media/media_info/hdlists +media/media_info/media.cfg description of the available install media. - format is one line for one medium as - <hdlist_name> <rpms_directory> <description> - <hdlist_name> should be match regexp /hdlist\S*.cz2?/ - for example (two cd install) you get - hdlist1.cz Mandrake/RPMS1 Boot CD - hdlist2.cz Mandrake/RPMS2 Extension CD + cf MDV::Distribconf(3) media/media_info/hdlist*.cz - table of rpm's headers, referred by ``hdlists'' + 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/depslist.ordered - for each packages, tell which package it depends on. Also contains the - size for some (obscure) bloody reasons. - ! Need to be remade when media/main changes ! - (with ``gendistrib --noclean --distrib .'') - -media/media_info/compssUsers +media/media_info/compssUsers.pl media/media_info/rpmsrate ranks and classify packages, so that the installer will know which @@ -90,37 +59,41 @@ media/media_info/rpmsrate <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 must have + 5 mandatory 4 important - 3 very nice + 3 interesting 2 nice 1 maybe - by default (for non expert), group selects packages for level 4 (important) - and 5 (must have). export mode add 3 (very nice) level. other level (below 2) - can only be selected using individual package selection. - -install/stage2/live - live system used on certain installs. See ``Ramdisk or not'' below for - more. + 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.clp +install/stage2/mdkinst.sqfs for the compressed loopback of install. generated from install/stage2/live tree using misc/mdkinst_stage2_tool -install/stage2/rescue.clp +install/stage2/rescue.sqfs rescue ramdisk. create_compressed_fs iso file this is the ramdisk loaded when typing rescue on boot prompt. -install/images/*.img - floppy boot images to use with DrakX. Use: - - cdrom.img for cdrom install - - network.img + network_drivers.img for ftp/nfs install (non-pcmcia devices) - - hd_grub.img for hard-disk install (see http://qa.mandrakesoft.com/hd_grub.cgi) - - pcmcia.img for pcmcia install (see ``PCMCIA install'' below for more) +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) + ******************************************************************************** * logs ************************************************************************* ******************************************************************************** @@ -137,7 +110,7 @@ not interesting. - alt-F4: kernel's place. aka the output of dmesg. - alt-F7: the graphical install lives there -- command "bug" puts on floppy lots of interesting stuff. +- 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 @@ -154,45 +127,11 @@ the auto-partitionning partitions can be changed, the default user class can be set to developer (!)... ******************************************************************************** -* po translation files ********************************************************* -******************************************************************************** -DrakX uses .po files for its translation. A script takes the different -strings out of the .pm files. It generates the DrakX.pot file which contains -all the english strings to translate. - -******************************************************************************** -* PCMCIA install *************************************************************** -******************************************************************************** -If the media you use to install is a pcmcia device, use the pcmcia boot disk. - -******************************************************************************** * modules ********************************************************************** ******************************************************************************** -Modules can be found in at least 2 places: -- in /modules/modules.mar -- in /lib/modules.cz<KERNEL_VERSION_RELEASE> - -/modules/modules.mar is used in mdk-stage1. It contains only modules -interesting for one kind of install. For example in an hd install, it -contains scsi modules. For a network install, it contains network card -modules. (To create, extract or view files in a ``mar'' archive, please -use gi/mdk-stage1/mar/mar; this is basically an archive format meant to -be minimalistic) - -/lib/modules.cz<KERNEL_VERSION_RELEASE> contains all modules, it is used -in stage2. - - 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. It uses the dependencies found in -/modules/modules.dep (stage1). - -/usr/bin/insmod is a wrapper around /usr/bin/insmod_. It just extracts the -module out of /lib/modules.cz in /tmp. Then it calls insmod_. - -/usr/bin/insmod_ is the real prog (which you usually find in /sbin/). You need -to give it the complete path. +wrapper around /usr/bin/insmod. ******************************************************************************** * Making screenshots *********************************************************** @@ -220,7 +159,7 @@ About the stage2 part (the actual installer, at the time you're documentation written by David Eastcott. Either install the package "drakx-autoinstall-doc" from contrib, or browse: -http://members.shaw.ca/mandrake/drakx/9.0/HTML/ +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 @@ -251,15 +190,6 @@ your auto installs from your server. init loads stage1 stage1 loads stage2, from various medium type -stage2 is too big to fit on a floppy, that's why stage1 exists - -> - How each stage relates to the various media access methods - -stage1 knows only how to access to the media is compiled for. It -contains only the kernel modules needed for that media. For eg, -the nfs/ftp/http stage1 (network.img floppy) doesn't contain scsi -modules nor ide. - > - How one stage terminates and another begins. i.e., How does > stage1 find, mount, and launch stage2? @@ -274,5 +204,5 @@ replaces stage1, and init then monitors stage2) > o Text and Graphic mode installers > - Architectural overview of each -have a look at gi/docs/object_class.fig +have a look at drakx/docs/object_class.fig |