diff options
Diffstat (limited to 'docs/README')
| -rw-r--r-- | docs/README | 361 |
1 files changed, 96 insertions, 265 deletions
diff --git a/docs/README b/docs/README index d35508e66..02bc5d351 100644 --- a/docs/README +++ b/docs/README @@ -1,37 +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 as a lot of things are binary files. - -For the boot kernel, see https://kenobi.mandrakesoft.com/~chmou/kernel/BOOT/ -or build your own: -- install the kernel-*.src.rpm from -- go to the /usr/src/RPM/SPECS/ (or any others topdir you have configured). -- type rpm -ba --with BOOT kernel-2.4.spec. -Then see function install_kernel() at the end of gi/update_kernel. - -For the other things, take SRPMS/DrakX-*.src.rpm - -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 *************************************************** @@ -39,27 +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 : - -(1) network or 1-cdrom installs - DIRS == the root directory of the Distribution +% gendistrib --noclean --distrib <DIR> -(2) multi-cdrom install - DIRS == the root directories of all the media that the install will see +Where <DIR> is the root of all the distribution. -``gendistrib'' will scan the file Mandrake/base/hdlists in the main root -directory (the first one in DIRS) to search for all media used. Typically you -use Mandrake/RPMS* for RPM packages repository. -For multi-cd, please use Mandrake/RPMS or Mandrake/RPMS1, Mandrake/RPMS2, etc. -For one CD or a network/hd volume, please use Mandrake/RPMS. +``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 ``Mandrake/base/rpmsrate''; this file manages +Optionnally, you can modify ``media/media_info/rpmsrate''; this file manages the relative importance of the files, and thus their installation or not. -Also, mdkinst_stage2.gz must be remade if you modify files in Mandrake/mdkinst. +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. ******************************************************************************** @@ -67,84 +40,59 @@ See below for information about these files. ******************************************************************************** First here are the different things needed : -Mandrake/base/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 - -Mandrake/base/hdlist*.cz - table of rpm's headers, referred by ``hdlists'' + 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 Mandrake/RPMS* changes (with ``gendistrib'') ! - -Mandrake/base/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 Mandrake/RPMS* changes ! - (with ``gendistrib --noclean --distrib .'') + ! Need to be remade when media/main changes (with ``gendistrib'') ! -Mandrake/base/compss - obsoletes comps. It store packages in different categories, generated - from the %{GROUP} field - ! Need to be remade when Mandrake/RPMS* changes ! - (with ``gendistrib --noclean --distrib .'') +media/media_info/compssUsers.pl -Mandrake/base/rpmsrate +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 Mandrake/base/compssUsers* files, + 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. - -Mandrake/mdkinst - 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. -Mandrake/base/mdkinst_stage2.bz2 - for the ramdisk. live sytem in ext2 filesystem bzipped2. - generated from Mandrake/mdkinst tree using misc/make_mdkinst_stage2 - See ``Ramdisk or not'' below for more. +install/stage2/mdkinst.sqfs + for the compressed loopback of install. + generated from install/stage2/live tree using misc/mdkinst_stage2_tool -Mandrake/base/rescue_stage2.bz2 - rescue ramdisk. live sytem in ext2 filesystem bzipped2. +install/stage2/rescue.sqfs + rescue ramdisk. create_compressed_fs iso file this is the ramdisk loaded when typing rescue on boot prompt. - there is no live system available, only the ramdisk is used. -images/*.img - boot images to use with DrakX. Use: - - cdrom for cdrom install - - network for ftp/nfs install (non-pcmcia devices) - - hd for hard-disk install - - pcmcia for pcmcia install (see ``PCMCIA install'' below for more) +install/images/all.img + fat16 image to dd on a partition (hint: sda1) - the following modules have been removed from: - network.img: acenic sk98lin de4x5 - cdrom.img and hd.img: BusLogic seagate fdomain g_NCR5380 dc395x_trm tmscsim - hd.img: dpt_i2o eata eata_pio eata_dma - cdrom.img: aztcd gscd isp16 mcd mcdx optcd cm206 sjcd - pcmcia.img: apa1480_cb - they are now in "other.img", +install/images/boot.iso + iso image to burn enabling any install (cdrom/hd/nfs/ftp) - blank.img is a blank boot image without a kernel nor initrd. this image - can be used to generate custom boot disk. - - if you think one of those modules is used a lot, tell me, i may find some room - to put it back on the main floppies. + 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 ************************************************************************* @@ -162,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 @@ -179,92 +127,58 @@ 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. -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) - -******************************************************************************** -* PCMCIA install *************************************************************** +* modules ********************************************************************** ******************************************************************************** -If the media you use to install is a pcmcia device, use the pcmcia boot disk. +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. ******************************************************************************** -* Ramdisk or not *************************************************************** +* Making screenshots *********************************************************** ******************************************************************************** -The DrakX 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) -(update! now size is 21MB - 24/01/01) -(update! now size is 19MB - 26/04/01) - -| | newt | DrakX -|-------+---------+---------------------------------------------------------- -| nfs | live | live -| ftp | ramdisk | ramdisk -| http | ramdisk | ramdisk -| hd | ramdisk | live if Mandrake/mdkinst/usr/bin/runinstall2 is a link, -| | | ramdisk otherwise -| cdrom | ramdisk | live if memory < 52MB, ramdisk otherwise - -Where ramdisk is needed, if detected memory is below the limit allowed for -ramdisk (maintained in file gi/mdk-stage1/config-stage1.h; currently 52 Mb), -a failure dialog will be printed explaining that there is not enough memory -to perform the installation. - -When i say live, it means that the stage1 will *mount* the -Mandrake/mdkinst and use it that way. - -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) - -For pcmcia, it depends on the type of install. +1. easy solution: press "F2"! +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 ******************************************************************************** -* modules ********************************************************************** +* Auto install ***************************************************************** ******************************************************************************** -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. +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. -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 -/modules/modules.dep (stage1). +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: -/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_. +http://members.shaw.ca/Mandrake2/drakx/9.2/AutoInstall-9.2.2.html -/usr/bin/insmod_ is the real prog (which you usually find in /sbin/). You need -to give it the complete path. - -******************************************************************************** -* Making screenshots *********************************************************** -******************************************************************************** -1. easy solution: press "F2"! +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 -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 +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. ******************************************************************************** * Miscellaneous **************************************************************** @@ -274,104 +188,21 @@ then, on another computer: > - What exactly each stage does init loads stage1 -stage1 loads stage2, on 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 -doesn't contain scsi modules nor ide. +stage1 loads stage2, from various medium type > - How one stage terminates and another begins. i.e., How does > stage1 find, mount, and launch stage2? -/sbin/init just starts /sbin/stage1 -/sbin/stage1 takes care of mounting stage2 (in ramdisk if necessary) - then it runs /usr/bin/runinstall2 + /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) > 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 -******************************************************************************** -* OEM ************************************************************************** -******************************************************************************** -> I am a system OEM in Bangalore,India selling systems bundled with -> Mandrake Linux. The problem is that with every system I sell, I need to -> install & configure the system which takes HOURS!. Can I do a diskcopy -> instead? -> -> Please Help. This is a major bottleneck for me. - -many solutions: - -- make an install on drive hdb, then : - dd if=/dev/hdb of=/dev/hdc - but you should make sure the hardware is *REALLY* identical. - -- try the oem feature - 3. - burn a cd out of *latest* cooker or 8.0 and above. - - boot on it telling "oem" to syslinux - !! it will destroy every data on the harddrive or - resize (or use free space) if *ONLY* one fat partition is defined !! - - you now have a very automated install matrix - (duplicate it with "dd if=/dev/hdb of=/dev/hdc bs=1M count=730") - - put the harddrive in the oem box, the user will now have an *very* automated - install, just asking the root password and user password, and some other - question according its hardware. - - 4. just like 3. but you may have to mount /cdrom after typing rescue on - syslinux prompt (oem script do it automatically if a automatic boot nfs - network has been done as server is known). under /cdrom may be anything - as long as it provides an installation tree of Mandrake Linux. - after that run oem script by typing "/etc/oem -f" for normal installation - or "/etc/oem -f server" for server installation (normal with server installed). - - 5. (just like 3. without burning a cd, doing the first part by hand) - have a look at the /etc/oem script on the rescue and do it by hand... - - -cu Pixel, fpons. - - -comments: -1. maybe copy unnecessary things -> take too long - solution -> use bs=8k count=xxxx -2. kernel_reread can be found on the new rescue, source is also at end of this -mail. This solution works with one partition. Can be easily enhanced to many -primary partitions... For extended partitions, more complicated, but not much :) -3. has just been added in latest cooker. It may still have some pb. The main -current limitation is IDE only, though it can be fixed easily for special cases. - --------------------------------------------------------------------------------- -#include <stdio.h> -#include <sys/mount.h> -#include <fcntl.h> - -void die(char *msg) -{ - perror(msg); - exit(1); -} - -void kernel_read(char *dev) -{ - int fd; - if ((fd = open(dev, O_RDONLY)) == -1) die("can't open device"); - ioctl(fd, BLKRRPART, 0); - close(fd); -} - -int main(int argc, char **argv) -{ - if (argc != 2) { - fprintf(stderr, "usage: kernel_read_part <hard drive device>\n"); - exit(1); - } - kernel_read(argv[1]); -} |